Journeys

Replay a single visitor's day as a timeline: the pages they read, what they clicked, the events they fired and any errors they hit.

Flow shows the routes a thousand people took. Journeys shows one of them. Each card is a single visitor's day: where they landed, what they read, what they clicked, which events they fired, anything that broke, and where they left.

It is the view to open when a number looks wrong and you want to see the raw behavior behind it. Filter to a goal and read three journeys that converted; filter to a campaign and watch what those visitors actually did with the page you sent them to.

What a journey is

One visitor per site-local day. If someone visits in the morning and again in the evening, that is one journey containing two visits, not two journeys. Journeys never join across days, and never across sites, because the identity behind them cannot.

The visitor id is the same cookieless, one-way hash the rest of Numative counts with: it is derived from the day, the site and a server secret, so it identifies a day's activity and not a person. It cannot be reversed to an IP, it is different tomorrow, and it is different on every site. See Privacy & data.

Reading the list

Journeys are listed newest first, up to 500 at a time. Each card summarizes the day before you open it:

Where they were: city, region and country, with the device and browser. A map above the list plots the same visitors.
The route: landing page, the pages between, and the page they left from.
How long the day lasted, and how many visits it took.
Click and error counts, so a session that hit a bug is visible without expanding it.
A bot badge naming the crawler, on the journeys that are not people.

The timeline

Expanding a card replays the day in order, one row per thing that happened:

Pageviews, with the referrer that brought them and how long they stayed on each page.
Clicks, described by the element they landed on ("button.subscribe", the link's destination), captured with no event code at all. See Click autocapture.
Custom events you send, with their properties and any revenue.
Errors, exactly where they happened, so you can watch a visitor click a button, hit a TypeError and leave. See Error tracking.

Values a visitor typed are never captured, so a form field appears by its label or placeholder and never by its contents.

Filtering

Journeys honor the same filters and segments as the rest of the dashboard, plus one of their own: clicking a visitor's id filters to that visitor, which is how a page row or a goal drills into "show me the people this describes". Because the id rotates daily, that filter is scoped to the day it belongs to.

The list caps at 500 journeys; when it is full, narrow the window or add a filter rather than scrolling.

Journeys are built from the per-visitor event stream the Numative tracker collects, which the Google Analytics API does not expose, so the section is available on sites with Numative tracking. A site running both sources still gets it: journeys are read from the collector whichever source the dashboard is showing.

Over the API

GET /api/v1/journeys returns the same list, and ?visitor=<id> returns one visitor's full event stream. See the Stats API.