Description
Reviews reconstructed recordings of real user sessions to see clicks, scrolls, hesitations and errors behind analytics metrics, at scale and without moderation.
Session replay tools capture DOM changes and user input events, then reconstruct sessions as videos showing how individual users moved through a product. They bridge quantitative analytics and qualitative observation: an analyst can filter for sessions that dropped from a funnel step, triggered an error or showed rage clicks, and watch what happened. Rigour comes from sampling deliberately (filtering by the behaviour of interest and reviewing a defined number, such as 20-50 sessions), coding observations with a consistent scheme rather than noting anecdotes, counting how often each issue appears, and validating hypotheses quantitatively. Privacy is integral: sensitive fields must be masked, consent and legal requirements respected, and retention limited. Replays show what users did but not their intentions, so pairing with interviews or tests remains important.
Attributes
- Discipline
- Product Analytics & Strategy
- Loss type
- Active
- Stage
- Post-launch
- Data
- Qualitative
- Effort
- Days
Steps
- Define the question and filter criteria (e.g. sessions abandoning at checkout step 3 on mobile).
- Confirm masking of sensitive fields and compliance with consent and data retention rules.
- Sample a defined number of sessions, typically 20-50, randomly within the filter.
- Code each session with a consistent scheme: issues, hesitations, errors and workarounds.
- Count issue frequencies and confirm patterns with quantitative signals such as rage-click or error events.
- Prioritise fixes and validate them with A/B tests or follow-up usability testing.
Sources
- UX Research
Also known as
- Session Replay
- Session recording
- Screen recording analytics
Categories
- Analytics & Behaviour
- Product Analytics & Strategy