Journeys

A journey is one session opened as a timeline: every page in order, how long each was engaged and how far it was scrolled, and every custom event where it fired, with its properties. It answers the question the counts cannot: what did this person actually do.

Opening one

Four doors, all leading to the same drawer over the screen you are on:

• Realtime: the Session link on any row of the activity feed.
• Events: a selected event’s Recent occurrences.
• Goals: a selected goal’s Converting sessions, the newest sessions that completed it, so the funnel’s last number has faces.
• Pages: a selected page’s Recent sessions on this page, so “what did they do next” is one click.

The lists respect the range and the filters of the screen. A list shows when the session started, country and device, the entry page and the exit page, the page count and the engaged time.

The drawer is in the address bar (session=…), so a link to it opens the same session for a colleague. Escape closes it and puts focus back where you were.

Also today

Under the timeline, Also today lists the same visitor’s other sessions on that day, newest first; Open swaps the drawer to one of them. The day is the limit on purpose: an anonymous visitor’s number is computed from the request and a salt that changes every day, so the same person is a different number tomorrow and their days cannot be joined. How Lynq counts says why.

What a journey is not

It is not a recording. There is no mouse movement, no keystrokes, no form contents, no screenshots; a journey is the pageviews and events the tracker already sends, in order. There is no list of all sessions either: the drawer opens from a row that answers a question, never from a search over everyone.