Connect your website to the questions behind each visit.

See which sources bring visitors to your website. Compare landing pages, campaigns, and the goals those visits complete. The tracker records navigation through the same integration as custom events.

For a SaaS website, start with the pricing page and a completed signup. Use a goal to compare the quality of traffic from different sources.

The browser integration supports page views, outbound links, downloads, tagged custom events, and engagement. Optional click and form capture need explicit configuration.

Choose a few useful events before adding more detail. Avoid passwords, form answers, and other sensitive values in event properties.

Create a project and an ingest key. Add the supplied snippet to your website. Set the allowed origins and choose the privacy settings before sending events.

Visit a page and check the project's first-event status. Then verify one goal before using it in a report. The tracker guide explains the connection settings.

The browser tracker observes supported history changes in single-page applications. Do not also send a server page view for the same visit.

If your server knows about activity the browser cannot see — a subscription renewal, a background job, a purchase confirmed after the visitor left — send it to the HTTP API instead, with the same visitor identity.