Session Recording

Session recording (also called session replay) captures a user's interactions on your website or app and plays them back as a video. You can watch exactly what a user did: where they moved their mouse, what they clicked, how far they scrolled, where they hesitated, what they typed (with sensitive fields masked), and where they rage-clicked out of frustration.

Why it matters: quantitative analytics tells you what is happening (conversion dropped 15% on the checkout page). Session recordings show you why. Maybe users cannot find the promo code field. Maybe the "Continue" button is hidden below the fold on mobile. Maybe the page is loading slowly and users leave before it finishes. Recordings add qualitative context to quantitative data, turning abstract metrics into visual, intuitive understanding.

Tools in the space: Hotjar and Microsoft Clarity are the most popular, with Clarity being completely free. FullStory and LogRocket offer more advanced features like search, segmentation, and developer-oriented debugging (network requests, console errors alongside the replay). PostHog includes session recording in its open-source analytics suite. Smartlook combines recordings with event-based analytics.

How to use them effectively: do not watch recordings randomly. Start with a quantitative insight (like a high drop-off step in a funnel), then filter recordings to users who dropped off at that step. Watch 15-20 sessions to identify patterns. Look for: confusion indicators (back-and-forth navigation, rage clicks, form abandonment), UX friction (small tap targets on mobile, unclear CTAs), and unexpected user behavior (using features in ways you did not intend).

Privacy considerations: session recording tools must handle personal data responsibly. Most tools automatically mask sensitive form fields (passwords, credit cards). You should configure additional masking for any PII fields. Ensure your privacy policy discloses the use of session recording, and comply with GDPR/CCPA requirements. Clarity and Hotjar provide built-in privacy controls.

Common mistakes: recording every session without a strategy for watching them, leading to thousands of unwatched recordings. Not combining recordings with quantitative data, which means you are watching random sessions instead of targeted ones. Over-reacting to individual sessions instead of looking for patterns across multiple recordings.

Practical example: a checkout funnel shows a 40% drop-off at the shipping address step. The team watches 25 recordings of users who abandoned at that step and discovers that the address auto-complete widget fails on Safari, forcing users to manually type their full address. Fixing the widget reduces the drop-off by 22%.