Sessions, visitors, journeys
The three units of data you'll work with. Knowing how they relate makes the filters and dashboards make sense.
Session
One continuous recording on a single page-load. Starts when the tracker boots, ends when the tab closes, the page unloads, or recording is stopped by idle suppression (5-min pause, 30-min hard stop). Navigating to a new URL inside the same site begins a new session, same visitor, new recording.
Visitor
A randomly-generated anonymous identifier stored in the browser's localStorageunder a key the tracker owns. The same visitor can have many sessions over time. Clearing local storage (or using a fresh incognito window) creates a new visitor — there's no fingerprinting to stitch them back together.
Journey
When a visitor has multiple sessions (because they navigated across pages), the player offers a Journey toggle that stitches those sessions into one continuous playback. The Journey button shows up automatically on the replay page when the visitor has 2+ sessions inside a tight time window.
Journeys are useful for funnel work, instead of opening session 1, then session 2, then session 3, you scrub one timeline that spans the whole visit.
Grouping in the sessions list
The sessions toolbar has a Group selector:
- None, flat list of every session, most recent first (or by event count if you switch the sort).
- URL, group sessions by their canonical page (no query string), so all visits to
/orykl-sessionsbucket together. - Visitor, group all sessions by the same visitor. This is the default and what unlocks the Play Journey button on multi-session buckets.