Reviewing Sessions

A fast way to get value from recordings is: filter → watch → tag → act. This page covers how to triage sessions, interpret timeline markers, and turn sessions into an action list.

Sessions list filters — Screenshot to add: Sessions list showing filters (device, frustration, page, duration, errors, tags).

Start with the right filters

Frustration: focus on sessions with rage clicks, dead clicks, or high frustration score.
Page / entry page: filter to a specific funnel step (product pages, cart, collection pages).
Duration: short sessions often indicate confusion; long sessions can indicate decision fatigue.
Errors: filter sessions with JS errors or failed network requests (if enabled).

Privacy note

Recording respects consent and blocks sensitive paths (such as checkout/account). If recording is disabled or consent is denied, you’ll see fewer sessions and some pages won’t be recorded.

Use the timeline to jump to moments that matter

Session player timeline — Screenshot to add: Session player showing timeline markers (page views, frustration, JS errors, network failures).

Timeline markers help you skip straight to key moments (page views, frustration events, errors). When you’re trying to answer “what went wrong?”, this is much faster than watching from the start.

Operationalize: tags, notes, and review queue

Tags and notes UI — Screenshot to add: Session detail with tags/notes and review queue controls.

Tags: label sessions like “checkout friction”, “pricing confusion”, “mobile layout”.
Notes: add the hypothesis (“CTA not visible on mobile”) and the next action.
Review queue: create a small queue of sessions to revisit after you ship a change.

Cross-links: prove with heatmaps and experiments

Use heatmaps to see if session behavior matches the broader pattern.
Use A/B tests to measure the impact of a change.
Use surveys to capture “why” in the visitor’s own words.