Session Replays

Overview

Session Replays lets you watch back real visitor sessions as if you were looking over their shoulder. Every click, scroll, page navigation, and form input is captured and can be replayed in a full video-like player directly in your dashboard. This is invaluable for debugging bug reports, understanding user journeys, and identifying UX friction points.

Navigate to Dashboard → Audience → Session Replays to open the replay library.

Enabling Session Replays

Session replays are recorded by the Yaplet widget, but the feature must be enabled per widget:

Go to Dashboard → Widgets and select the widget you want to configure.
Scroll to the SDK Features section.
Toggle Session Replays on.
Save the widget settings.

Once enabled, the widget will automatically start recording visitor sessions using rrweb — a lightweight, privacy-conscious session recording library. Recordings are uploaded in segments and stitched together into full journeys on the server.

Session replay retention and maximum replay limits are managed globally by Yaplet. Older recordings are automatically cleaned up when limits are reached.

Replay Library

The Session Replays page displays a searchable, sortable table of all recorded visitor journeys:

Column	Description
Visitor	The visitor's email or name (if known)
Widget	Which widget captured the session, shown with its avatar
Entry URL	The first page the visitor landed on
Last URL	The last page visited in the session
Duration	Total session length in `MM:SS` format
Pages	Number of distinct pages visited during the session
Segments	How many recording segments make up the journey
Importance	AI-calculated importance level (Low, Medium, High, Critical)
Created	When the session was recorded

Filtering

Use the filter bar to find specific sessions:

Visitor email — search by the visitor's email address
URL — filter by entry URL
Widget — narrow down to sessions from specific widgets
Importance — show only sessions at certain importance levels
Country — filter by the visitor's country
Device — filter by mobile or desktop sessions

Importance Scoring

Every session is automatically scored for importance based on several signals:

Rage clicks — repeated clicks in the same area, indicating frustration
Console errors — JavaScript errors that occurred during the session
Network errors — failed API calls or resource loads
Session duration — unusually long or short sessions
Page count — how many pages the visitor navigated through
Identified visitor — sessions from known (logged-in or identified) visitors score higher

The score translates into four levels: Low, Medium, High, and Critical. High and critical sessions are the ones most likely to reveal real issues worth investigating.

Watching a Replay

Click the play button on any row to open the replay journey modal. The modal has two panels:

Segment Sidebar

The left panel lists all segments that make up the journey. Each segment shows:

Segment number
Importance level badge
Entry URL
Duration and timestamp

Click any segment to load its replay in the player.

Replay Player

The right panel contains a full-featured replay player with:

Play / Pause — start or stop playback
Progress scrubber — drag to jump to any point in the recording
Speed controls — play at 0.5x, 1x, 1.5x, or 2x speed
Skip idle — compress periods of inactivity so you only see meaningful interactions
Interaction timeline — colored markers above the progress bar show where clicks (blue), inputs (green), and scrolls (gray) happened — click any marker to jump directly to that moment

Use the Skip idle button to cut through long periods of inactivity. This is especially useful for sessions where the visitor left the tab open but wasn't actively using the page.

Session Replays in Tickets

When a visitor submits a ticket (bug report, feedback form, etc.) and session replays are enabled, the ticket automatically captures a replay of the visitor's session. You can watch this replay directly from the ticket view by clicking the View Replay button in the ticket's action panel.

This gives you immediate context for the issue without needing to search through the replay library — you see exactly what the visitor was doing when they submitted the ticket.

For more details on using replays within tickets, see the Ticket View documentation.

How It Works

Under the hood, session replays use rrweb to capture DOM mutations, mouse movements, clicks, scrolls, and input events as lightweight JSON snapshots. This approach:

Records a faithful reproduction of the page without capturing actual screenshots or video
Keeps recording payloads small (typically a few hundred KB per segment)
Respects privacy — password fields and sensitive inputs are automatically masked

Recordings are uploaded to Yaplet's storage as the visitor browses. Each page navigation or significant break creates a new segment, and all segments from the same browsing session are grouped into a journey.