Sessions

A session is one contiguous visit from a single person. A new session starts after 30 minutes of inactivity, so the same person coming back later shows up as a separate, later visit. The feed is newest first.

Reading a session card

Each card is one visit. Left to right it tells you who came, how, and what they did.

• Visit number and acquisition source. VISIT 25 is this person's 25th visit to your site. The Acquisition source line shows the source and medium that first brought them in (for example ig · social). Direct visits have no acquisition line.
• Who. An avatar plus a name. If you have identified the user (by sending a user ID from your site), you see their real identifier and an Identified badge; otherwise you get a stable anonymous name like "Orange Trout" that stays the same across all of their visits.
• Browser, OS, device. The three small icons. Traffic from an in-app browser (Instagram, for example) shows that app's icon, which is why social visits look the way they do.
• Pageviews and events. The eye pill counts pageviews. Any named event that fired in the visit gets its own pill next to it (for example InitiateCheckout 1), so you can spot the sessions that actually did something.
• Channel. The marketing channel TrueMetriks resolved for the visit (Organic Social, Direct, Paid Search, and so on).
• Entry and exit page. The first page they landed on, an arrow, and the last page they saw. A single path means they only viewed one page.
• When and how long. The start time and the session duration (first event to last event).

Narrowing the feed

The bar above the list filters which sessions you see:

• Identified only hides anonymous visitors so you only see people you have a user ID for.
• Min pageviews, Min events, and Min duration (s) drop the shallow visits. Set Min duration to a few seconds to clear out the 0-second bounces, or Min events to 1 to see only sessions where something fired.
• The Filter button and date range at the top scope the feed by any property (country, channel, UTM, page, event name, and more), exactly like the rest of the dashboard.

Use the page arrows on the right to move through the feed; it loads 100 sessions per page.

Opening a session

Click any card to expand it in place. You get two tabs and a shortcut to the person's full history.

Timeline

The Timeline is the play-by-play: every event in the visit, in order, numbered down the page. Each pageview shows the URL (the query string, including UTMs and click IDs, is greyed after it) and the time spent on that page before the next pageview. Custom events, outbound clicks, button clicks, copies, form submits, input changes, and errors all appear inline where they happened.

The pills at the top filter the timeline by event type. Each one carries a count, so Pageview 3 means three pageviews in this visit; click a type to show or hide it. Long sessions load in batches with a Load More button, and the footer keeps a running Showing X of Y events.

The per-page duration is measured to the next pageview, not the next event, so a custom event firing a split second after the page loads never makes a page look like it lasted zero seconds.

Session Info

The Session Info tab is the reference card for the visit, in three columns:

• User Information - user ID, language, and resolved country, region, and city.
• Device Information - device type, browser and version, OS and version, screen size, and IP.
• Source Information - channel, referrer, and entry page.

View User

View User jumps from this single visit to that person's complete cross-session profile: every visit they have ever made, stitched together. It is the bridge from "what happened in this session" to "who is this person and what is their whole journey." See Users for that view.