How to track website visitors—and understand their interest

What does website visitor tracking show?

A useful visitor view groups activity by browser and session. In WhoVisited, you can examine page views, the pages visited in order, returning sessions, and custom events that you explicitly send. This gives more context than a total page-view count alone.

For a B2B team, this view can answer practical questions: Did a browser return after reading the product page? Which content did it explore before pricing? Did a configured event, such as a demo button click, occur? Use those signals to improve your website and decide which journeys deserve closer attention.

How does the tracking work?

1. Create a site and allow its domain. WhoVisited only accepts activity from configured website origins.
2. Install the tracker. Add the public script with your site ID. It records page views and can receive custom events you choose to send.
3. Review journeys. The dashboard groups activity into anonymous visitors and sessions so you can inspect the sequence of pages and events.

The script uses a random browser identifier and a session identifier. A session expires after inactivity. Your website must decide when it is appropriate to start collection, including any consent requirements that apply to your visitors. The tracker can wait for consent and respects Do Not Track and Global Privacy Control signals.

Can you identify every anonymous visitor?

No. An anonymous browser record is a record of activity, not a person's identity. The same person can use multiple browsers or devices, and multiple people can share a device. A visit to a pricing page also does not prove that someone is ready to buy.

WhoVisited currently focuses on activity, sessions, and visitor journeys. Company and person resolution are planned integrations, not a feature you should assume is available today. Even when a company can be inferred later, that alone will not establish which person visited. Keep these distinctions clear when interpreting your data or sharing it with a sales team.

How to get started with WhoVisited

Start with one website and a few questions you actually need to answer. Configure its allowed origin, install the script, and check that page views arrive. Then add only the custom events that represent meaningful actions. Review a handful of real journeys before deciding whether the data helps your team.

Collection depends on an active workspace subscription and site settings. You can pause a site, and the server checks access again when events arrive. Read the privacy policy for details about collected data and controls.