Session Replay (Recordings)

What is Session Replay?

Session Replay enables you to experience your product exactly as your users do. It reconstructs user journeys by recording interactions—such as clicks, scrolls, and inputs—allowing you to watch a high-fidelity playback of the user experience.

Why use Session Replay?

  • Troubleshoot Faster: Eliminate the guesswork by seeing the exact steps a user took before encountering a bug.
  • Optimize UX: Identify friction points, confusing navigation, or "rage clicks" that quantitative data helps you miss.
  • Audit Interactions: Validate complex user flows, from completing a checkout to interacting with AI agents, ensuring every touchpoint performs as expected.
  • Validate Features: Watch real users interact with new deployments to confirm features are being used as intended.

Recording Settings & Configuration

Manage how sessions are captured and ensure user privacy through the Recording Settings page.

  1. Recording Activation

Enable/Disable: Use the master toggle to turn session recording on or off for your entire application.

Sample Rate: Define the percentage of user sessions to record (e.g., 100 for all sessions, 50 for half). Click Update to save changes.

  1. Form Privacy

Protect sensitive user data by defining how form fields are handled during recording:

MASK: Replaces the text content with asterisks or placeholders (e.g., for textareas).

UNMASK: Captures the actual text entered (use only for non-sensitive fields like search bars).

EXCLUDE: Completely ignores the element and its interactions (e.g., radio buttons).

How to Protect sensitive user data by defining how form fields are handled during recording:

SettingDescriptionExamples
MASKReplaces the text content with asterisks or placeholders.Textareas
UNMASKCaptures the actual text entered (use only for non-sensitive fields).Search bars
EXCLUDECompletely ignores the element and its interactions.Radio buttons
  1. Element Data Capture Rules

Create custom rules to exclude or mask specific UI components based on CSS selectors:

Passwords: Automatically excluded by default (input[type=password]).

Sensitive UI: Exclude elements like credit card fields ([autocomplete^=cc-]) or progress bars to maintain a clean recording and protect PII.