Skip to main content
The Visitors view (Analytics → Visitors) is the people-shaped side of your analytics. Instead of aggregate pageview counts, it lists the actual humans who’ve been on your site, what stage of recognition they’re at, and what they did — so you can move someone from anonymous traffic to a named contact in one click.

​
The visitor list

Each row is one visitor (a stable first-party _sapt_vid), tagged with where they sit in the identity lifecycle: At the top of the view is your identification rate — the share of recent visitors who are identified or better. It’s the single number that tells you how well your site is converting anonymous traffic into people you can actually follow up with.

​
The lifecycle

A visitor moves through three stages, and Sapt keeps everything they did before each transition:
  1. Anonymous → identified. The moment a visitor submits a tracked form, or your code calls window.sapt.identify({ email }) (see First-party analytics), Sapt attaches that email/phone to their visitor ID. Everything they browsed before identifying is retroactively theirs.
  2. Identified → contact. Linking the visitor to a CRM Person promotes them to a contact. Do it from the dashboard with Add to CRM, or over the Attribution MCP with linkVisitorToContact.
Identification is sticky and cross-device. When the same email or phone shows up on a phone and a laptop, Sapt stitches those visitor IDs together so the timeline shows one person across every device — not two anonymous strangers.

​
Visitor timeline

Click any visitor to open their full event timeline: every pageview, click, form submit, and custom event in order, with the source and campaign that brought each session. For a contact, the same timeline also folds in CRM activity, so you get one continuous story from first anonymous visit to latest interaction.

​
Add to CRM

When a visitor is identified, the Add to CRM button turns them into a contact:
  • A CRM Person is created (or matched, if one already exists for that email/phone).
  • The visitor’s entire prior browsing history is attached retroactively — including sessions from before they identified, and from other devices that have been stitched to them.
  • From then on, new web activity keeps flowing onto that contact’s journey automatically.
This is how a cold, anonymous pageview from three weeks ago ends up as the first touch on a brand-new contact’s record the instant they fill out a form.

​
Do it from an agent

Everything here is also available to AI agents through the Attribution MCP:
  • getVisitors — the visitor list with identity status and stats
  • getLiveVisitors — who’s on the site right now
  • getVisitorTimeline — one visitor’s full event history
  • linkVisitorToContact — the programmatic Add to CRM
  • getContactJourney — the unified journey once a visitor is a contact

​
Keep going

Attribution analytics

Attribution MCP

First-party analytics