DocsOpen Henkan Vision
Insights

Visitors

Follow one visitor across their visits to see how many it took to buy and what stopped them before.

Up to date with v1.21.1Updated 29 October 20262 min read

Visitors groups sessions by visitor, so you can follow one visitor's path across several visits. Vision never knows who that visitor is.

A visitor is one browser on one device. After consent, the Vision script keeps an anonymous identifier in that browser, which links its next visits to the same visitor.

Each visitor gets a generated name, such as Calm Falcon 42, so you can recognise them and talk about them with your team. The name comes from the anonymous identifier only and never changes.

Human visitors of the site over the last 30 days, newest visit first.
Human visitors of the site over the last 30 days, newest visit first.
1
Figures. Visitors and visits in the period, the share who came back, the share who bought, and how many visits buyers needed.
2
Segments. All, Returning (two visits or more), Bought, Came back, did not buy, and With friction, each with its count.
3
Date range. A preset (the last 24 hours, 7, 30 or 90 days, this or last week, this or last month) or any range picked on the two-month calendar.
4
Visits. One dot per visit, oldest first: grey, orange when it had a friction, green when it ended in a purchase.
5
Journey. Where the visitor stands.

Read the list#

ColumnMeaning
VisitorThe generated name, the device and country of the latest visit, and since when the visitor comes (or new).
VisitsOne dot per visit in the period, up to the last 8, then the number of visits.
Last visitWhen their latest visit started. Times are in UTC.
FrictionFriction tags found across their visits.
JourneyBought on visit 3, Stuck at checkout (came back and left at the checkout again), Left at checkout (one visit), Returning or First visit. The cart counts the same way.

Visits before buying counts, for each visitor who bought in the period, the visits up to and including the first purchase. Segment counts cover the whole period, whichever segment is selected.

Only human visitors are listed. AI agents browsing the site have their own view under AI agents.

Follow one visitor#

Select a visitor to open their journey.

One visitor's journey, from first visit to purchase.
One visitor's journey, from first visit to purchase.
1
Story. How many visits over how many days, the first friction and the visit they bought on.
2
Tags. Device, country, total time, pages and the data layer values pushed across visits; select a value to see sessions that share it.
3
The journey at a glance. One marker per visit (up to 12), placed by date: orange for a friction, green for a purchase.
4
Friction step. The page where the visit's first friction happened, with its type and time.
5
Replay. Starts a few seconds before the friction when the visit had one.

Each visit lists the pages viewed in order (up to 12, with repeated reloads merged), how long it lasted, its device and how it ended: Bought, or No purchase with when the visitor came back.

Use the journey to answer questions such as:

  • How many visits does it take to buy?
  • What stopped this visitor the time before they bought?
  • Do visitors who hit a friction come back?

The session page links back to its visitor with All visits of followed by the visitor's name.

Limits#

  • A visitor is one browser. The same person on a phone and a laptop counts as two visitors, and clearing cookies and site data starts a new visitor.
  • The identifier is kept only after recording consent. See Recording consent.
  • Visitors follow the same retention as sessions: when all of a visitor's sessions are deleted, the visitor is too.

Your AI agents can read visitors through the MCP server and the REST API with list_visitors and get_visitor_journey.

PreviousSessionsNextFunnels