Sessions and realtime

Follow a single visit step by step, and see who is on the site right now.

Sessions

Sessions lists the latest 50 visits, or only the visits that paid. Each row shows when the visit started, where it landed, its source, how many pages it saw, how long it lasted and what it paid.

Open a visit to see its journey in order: every page, event, goal, identify and payment, up to 500 steps.

Session replay

Turn on session replay per site in Site settings → Install and proxy, then update the tag on your site: it gains data-replay="true", which loads a separate recorder script (about 3 kB gzipped). The main script stays the same size.

Open a recorded visit and press play. The page is rebuilt from the recording in a sandboxed frame, with the pointer, clicks and scrolling on top. The timeline marks page views, goals and payments; select a mark to jump to it. Play at 1× or 2×, and leave Skip idle on to jump over gaps longer than 3 seconds. Visits without a recording say so.

• Every input, textarea and select value is masked as ***. Password fields are never recorded. Checkbox and option choices aren't kept.
• Text inside an element with data-atrby-mask is masked. An element with data-atrby-block is replaced by a grey box of the same size.
• No network requests, console output, scripts, or the contents of iframes, canvas and video are recorded. URLs keep the path only, never the query string.
• You choose the share of visits recorded (1–100%). A visit is in or out for its whole tab session.
• Starter includes 2,000 recordings a month and Growth 20,000 (trials get Growth's). When the month's recordings are used up, new visits aren't recorded; visits already recording carry on.
• Recordings are kept for 30 days, then deleted. One recording is capped at about two hours.
• Bots, other hostnames and your excluded IPs, countries and paths are not recorded, the same as events.
• Viewers can't watch recordings unless you turn Sessions on for them in Team, and any member can have replays hidden.

Journey to payment

When a visit belongs to a known person, its journey also lists every visit by that person in the last 90 days, oldest first, with the payment: for example “3 visits over 9 days · identity-attributed”. Visits are linked by the user id you pass to identify(), and on cookie-mode sites also by the visitor cookie. Anonymous cookieless visits can't be linked across days, by design.

Realtime

• Visitors in the last 5 minutes, and visitors and pageviews in the last 30.
• A per-minute chart for the last 30 minutes, and revenue so far today.
• Top pages, sources and countries right now, and a feed of the latest events.

The screen updates every 5 seconds.

What a visit is

A visit lasts as long as the browser tab. Its id lives in sessionStorage and ends when the tab closes. A new tab is a new visit. The visit's source is where its first page came from, so pages and payments later in the visit keep it.