Capture activity
Use the Outlit Browser SDK for pageviews, form submissions, engagement, and custom events on your site. Use the Outlit Node.js SDK or Outlit Rust SDK for backend or native actions such as a completed export or API operation. These Outlit server SDKs can record identified or fingerprint-linked product events, but cannot observe a visitor’s browser landing page or link an unknown browser visit by themselves. Identify the browser visitor with their email when it becomes available; an email-only server identify does not link an otherwise anonymous browser visitor. PostHog and Mixpanel integrations import product activity into Outlit. The Outlit Browser SDK gives Outlit its own record of the anonymous website journey and links it to the contact when the browser identifies them. Billing status comes from a verified integration such as Stripe. CRM, conversations, and support integrations add account records and evidence. Start with Connect your data to see which sources your workspace needs.Link activity to people and customers
The Outlit Browser SDK gives an anonymous visitor an ID once tracking is enabled. When someone submits an email, signs up, or logs in, browseridentify() or setUser() links that visitor’s earlier activity to a known person. Outlit can then associate that person with a customer through a company email domain, explicit customerId, or connected source data. Personal-email addresses remain separate unless another source links them. See Identity resolution for the matching rules and review steps.
With the default autoTrack: "auto" mode, the browser SDK keeps tracking off—and stores nothing—in regions that require opt-in consent (EEA, UK, Switzerland, or unknown) until your site calls enableTracking(); autoTrack: false makes tracking wait for an explicit consent signal unless a previous opt-in is stored. The script and npm guides show the consent pattern. A persisted opt-out continues across visits until tracking is enabled again.
Read the customer timeline
Customer profiles show activity from connected sources in chronological order. Product events, billing changes, support tickets, messages, and meetings appear with their source context where available. Facts and assessments build on that evidence; check the source and timestamp before treating a finding as current. Customers explains profile sections and source coverage. Each person’s journey stage and the customer’s billing status are separate. Outlit derives engagement and inactivity from product activity. If you choose an ordinary event as the activation event, its first match records activation once for each eligible resolved person and company, independently. SDK events do not change billing status. See Customer journey for all stages, including Past due.Use the context
Your team reviews churn and renewal situations in Attention. Developers and agents can also read authorized customer context through the CLI, MCP, or public tool gateway. Use the Ingest API for custom event ingestion.Privacy and delivery
The Outlit Browser SDK strips recognized sensitive form fields before sending them. Configure enabled domains under Settings → Website Visitors; the public tracking key is visible in browser code by design. If your site needs consent, use the consent controls before collecting activity. For retention or deletion requests, ask your Outlit contact about your workspace policy.Next steps
Track your first event
Install the Outlit Browser SDK and check a customer timeline.
Customer context graph
See how tracking and integrations feed customer profiles.