Session Replay

Definition

Session replay captures a reconstruction of a user's interactions with a digital product. The recording includes clicks, scrolls, mouse movements, form inputs, page transitions, and errors. Unlike screen recording, session replay tools typically capture DOM changes rather than video, resulting in smaller file sizes and easier masking of sensitive data.

Modern session replay tools integrate with product analytics platforms, letting PMs jump from an aggregate funnel chart directly to individual sessions where users dropped off. This bridge between quantitative and qualitative data makes session replay one of the most practical research tools available to product teams. The product analytics hub covers how session replay fits into a broader analytics stack alongside tools like Amplitude, Mixpanel, and PostHog.

The technology works by injecting a lightweight script that observes DOM mutations and user events. These events are serialized and stored, then replayed in a viewer that reconstructs the page as the user saw it. Most tools add 1-3% overhead to page load, making them viable for production use. The Product Analytics Handbook covers how to pair session replay with quantitative metrics for deeper insights.

Why It Matters for Product Managers

Numbers tell you where problems exist. Session replay shows you what the problems actually look like. A PM staring at a funnel chart knows that 35% of users abandon the settings page. A PM watching three session replays of that page sees users scrolling past the save button because it renders below the fold on laptop screens.

Session replay also reduces the feedback loop between shipping a feature and understanding its impact. Instead of scheduling usability tests two weeks after launch, PMs can watch real users interact with the feature within hours of release.

For cross-functional alignment, session replays are powerful artifacts. Sharing a 30-second clip of a user struggling with a flow is more persuasive than any chart or ticket description. Engineers, designers, and stakeholders develop empathy for user pain when they watch it happen in real time.

Session Replay vs Heatmaps vs Analytics

These three tools complement each other. Understanding the differences helps you use each one effectively.

Product analytics answers "what" at scale. 2,000 users visited the pricing page. 800 clicked "Start Free Trial." 400 completed signup. Analytics gives you the numbers and lets you segment by user properties. It works across your entire user base.

Heatmaps answer "where" at the page level. They aggregate click positions, scroll depth, and mouse movement across many sessions to show which parts of a page get attention and which get ignored. Heatmaps are useful for evaluating page layout and CTA placement.

Session replay answers "why" at the individual level. You watch a single user's complete interaction to understand their decision-making process, confusion points, and workflow patterns. Session replay is the most time-intensive but produces the deepest qualitative insights.

The workflow: analytics reveals a problem (high drop-off). Heatmaps narrow it down (nobody scrolls past the fold). Session replay explains it (users get stuck on a confusing form field and give up). A/B testing validates the fix.

How Session Replay Works

Most session replay implementations follow a consistent pattern. A JavaScript snippet captures DOM state and user events. These events stream to a backend that stores and indexes them. A web-based viewer reconstructs the session, allowing playback at various speeds with timeline scrubbing.

Key capabilities to evaluate when choosing a session replay tool:

• Automatic PII masking for form fields, text content, and images
• Error correlation linking JavaScript errors to the exact session where they occurred
• Segmentation to filter sessions by user properties, pages visited, or events triggered
• Funnel integration to jump from drop-off points directly to relevant sessions
• Rage click detection to surface sessions where users clicked repeatedly on non-interactive elements

Comparing Session Replay Tools

Here is how the major tools compare for PM use cases.

FullStory. The most polished replay experience. Strong search (find sessions where a user clicked a specific element), frustration signals (rage clicks, dead clicks, error clicks), and integration with analytics platforms. Expensive at scale.

Hotjar. Combines session replay with heatmaps and surveys. Good for smaller teams that want an all-in-one qualitative research tool. Recording quality and filtering are less sophisticated than FullStory.

PostHog. Open-source platform that includes session replay alongside analytics, feature flags, and A/B testing. Best for engineering-heavy teams that want everything in one tool. Replay quality has improved significantly but still trails dedicated tools.

LogRocket. Developer-focused. Strong at correlating JavaScript errors, network requests, and console logs with session replays. Best for debugging production issues rather than UX research.

Microsoft Clarity. Free. Solid heatmaps and basic session replay. Good for teams with zero budget. Lacks the filtering and segmentation depth of paid tools.

For most product teams, start with Hotjar or PostHog to validate the practice, then graduate to FullStory when session replay becomes a regular part of your workflow.

A Practical Workflow for Using Session Replay

Watching random sessions is a waste of time. Here is a structured approach that produces actionable insights.

Step 1: Start with a question. Pull a specific question from your analytics data. "Why did 60% of users drop off at step 3 of onboarding?" or "How are users interacting with the new dashboard?"

Step 2: Filter sessions. Use your replay tool's filters to find relevant sessions. Filter by the page or event where the problem occurs, user segment, time period, and session duration. Most tools let you filter by error occurrence and frustration signals too.

Step 3: Watch 10-15 sessions. Not 2, not 50. Ten to fifteen sessions is enough to identify patterns without consuming your entire day. Take notes on recurring behaviors.

Step 4: Identify patterns. Look for behaviors that appear in 3+ sessions. A single user doing something odd is an anecdote. Five users doing the same odd thing is a pattern.

Step 5: Form hypotheses. Translate patterns into testable hypotheses. "Users drop off at step 3 because the CTA text is ambiguous" is testable. "Step 3 is confusing" is not.

Step 6: Share clips. Extract 15-30 second clips of the most telling sessions. Share them in the team Slack channel or attach them to Jira tickets. Clips are the most persuasive artifacts session replay produces.

Implementation Checklist

• Configure PII masking rules before enabling recording in production
• Set sampling rates to balance insight coverage with storage costs
• Define segments for high-priority user groups (new users, paying customers, churning accounts)
• Create saved filters for key flows (onboarding, checkout, feature adoption)
• Establish a weekly review cadence where PMs watch 10-15 sessions
• Integrate session replay links into bug reports and feature tickets
• Review privacy policy and update consent mechanisms as needed

Common Mistakes

1. Watching sessions without a hypothesis. Random session watching is time-consuming and rarely actionable. Start with a specific question from your analytics data, then use session replay to investigate it.

1. Skipping privacy configuration. Deploying session replay without proper PII masking creates compliance risk and erodes user trust. Always configure masking before enabling production recording.

1. Over-indexing on individual sessions. A single user's behavior can be misleading. Watch enough sessions to identify patterns before drawing conclusions. Combine session replay findings with A/B testing to validate hypotheses at scale.

1. Recording everything at 100% sample rate. Full sampling is expensive and unnecessary. For most products, 10-25% sampling captures enough sessions to identify patterns. Increase sampling for specific segments (new users, enterprise accounts) where every session matters.

Measuring Success

Track these indicators to assess your session replay practice:

• Insights per week: Number of actionable findings surfaced from replay reviews
• Time to root cause: How quickly the team identifies the cause of UX issues after detection
• Replay-driven changes: Features or fixes shipped based on session replay evidence
• Coverage rate: Percentage of sessions recorded versus total sessions
• Privacy compliance: Zero incidents of exposed PII in recordings

Related Concepts

Session replay pairs naturally with product analytics to move between aggregate patterns and individual behavior. Usability testing provides structured qualitative research, while session replay captures unstructured real-world behavior. Cohort analysis helps identify which user segments to focus replay reviews on, and A/B testing validates the hypotheses that replay sessions generate. Funnel analysis often serves as the starting point for targeted session replay investigations.