Session Replays

Record and replay visitor sessions to understand behavior, debug problems, and see exactly what somebody experienced on your website.

Overview

Session Replays lets you watch real visitor sessions back as if you were looking over their shoulder. Clicks, scrolls, page navigation and form input are captured and played back in a video-like player inside your dashboard. It is invaluable for reproducing bug reports and for finding the places where your interface trips people up.

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

Enabling Session Replays

Recording is done by the Yaplet chat widget, and it is off until you turn it on:

  1. Open Brand → (your brand) → Chat widget in the sidebar.
  2. Go to the Install tab.
  3. Find the SDK Features section.
  4. Turn on Session Replays.
  5. Press Save changes. ::

Once the switch is on, a Recording Rules row appears in the same section. Press Configure rules to narrow what gets recorded to particular pages or particular visitors. It reads Recording all pages until you set a rule, and Rules configured afterwards.

Session replays are part of the Growth plan, or a $12/month add-on on any other plan (the free 14 days include them too). Having them grants the Session Replays permission, which your team's permission settings list under Audience, and that permission is what makes the SDK Features section and the Session Replays screen appear at all. So if the switch is nowhere to be found, check your plan or add-on first; if a colleague cannot find it while you can, they have not been given the permission.

Once enabled, the widget records sessions and groups them into full journeys.

Replay Library

The Session Replays page shows a searchable table of recorded journeys. Until the first one arrives it says No recordings yet — sessions appear once visitors browse a site with session replay turned on in the widget settings.

Above the table, a row of quick filters narrows the list in one click, each with a count: All sessions, Rage clicks, Errors, Identified, Longer than 5 min, Mobile and Pinned. The counts follow the date range you picked.

ColumnDescription
VisitorThe visitor's email, name or identifier, with their country flag. Underneath: the page the session started on and how long ago it was recorded. A bookmark appears next to the name when the recording is pinned
DeviceAn icon for desktop or mobile — hover it for the word
DurationTotal session length, as minutes and seconds (hours too for a long one)
PagesNumber of pages visited during the session
Rage clicksHow many rage clicks the session had (0 when none)
ErrorsConsole plus network errors — hover the number to see the split, for example 2 console · 1 network
ImportanceA ten-bar meter colored by level — hover it for the level (Low, Medium, High, Critical) and its score
WidgetWhich chat widget captured the session, shown with its avatar
RecordedWhen the session was recorded

Each row ends with two buttons: a bookmark (Pin recording / Unpin recording) and a play button (Watch recording).

Filtering

Use the search box, the date picker and the Filter table button to find specific sessions. The button opens a dialog — press Apply to use its filters and Reset to clear them:

  • Date range — limit the list to sessions recorded within a period (it starts wide, covering the last year, so nothing is hidden until you narrow it)
  • Visitor — search by the visitor's name, email or ID
  • Widget — narrow down to sessions from specific chat widgets
  • Importance — show only sessions at certain importance levels
  • Device — mobile or desktop sessions

Importance Scoring

Every session is scored automatically from 0 to 100 (shown as the ten-bar meter in the table), and the highest-scoring segment — a part in the viewer — sets the level for the whole journey. The score goes up with:

  • Rage clicks — repeated clicks in the same area, which usually mean frustration
  • Console errors — JavaScript errors that happened during the session
  • Network errors — failed requests
  • Custom events — events your own code tracked through the SDK
  • Session length, number of recorded events and pages visited — longer, busier sessions score higher
  • Identified visitor — a small bonus for sessions from people you have identified

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

Watching a Replay

Click the visitor's name or the play icon (Watch recording) on any row to open the replay. It opens full screen, with the visitor, the start time, the length, the page count and the importance level in the header. The header also has Previous recording and Next recording arrows — with a count such as 3 of 12 — that step through the list the way it is currently filtered, a bookmark to pin or unpin the recording, and Copy link, which gives you a link that opens straight on this recording. Close the window with the ✕ or the Esc key. The window has two panels.

Side Panel

The right panel has three tabs:

  • Activity — a Search activity box and the filter buttons All, Pages, Clicks, Typing and Scrolls, then the list of what the visitor did in the current part: its time, what happened (Page view, Clicked, Typed into a field or Scrolled) and, for page views, the path. Click an entry to jump the player to that moment; the entry at the playhead is highlighted and follows the playback. A line above the list says which part you are in (for example Part 2 of 5) and its address.
  • Parts (N) — the parts the journey is made of (the segments mentioned elsewhere on this page), each with its number, its address, its length and date, and its importance level (shown unless it is Low). Click one to load it in the player. Where the visitor was idle for more than half a minute between two parts, the gap is drawn between them with its length and the word away. When the journey has more than one part, a Play parts back to back switch at the top plays the next part automatically when the current one ends.
  • Details — What happened tiles counting Clicks, Typing, Scrolls, Rage clicks, Console errors and Network errors; a Session list with Visitor ID (with a copy button), Country, Device, Widget, Started, Duration, Pages, Entry page and Exit page; and the Importance score with its level.

Replay Player

The main area is the player. The page's address sits on top, with a button to Open this page in a new tab, and the controls are underneath:

  • Play / Pause — start or stop playback (the space bar does the same)
  • Previous part / Next part — move between parts (shown when the journey has more than one)
  • Back 10 seconds / Forward 10 seconds — skip around in small steps
  • Progress bar — click or drag to jump anywhere in the recording. Dots above it mark clicks and typing, and taller marks show page changes
  • Playback speed — 0.5x, 1x, 1.5x, 2x, 4x or 8x; Yaplet remembers your choice
  • Skip inactivity — a switch that compresses periods of inactivity so you only watch the parts where something happened; it is off until you turn it on, and Yaplet remembers your choice
  • Full screen — expand the player to the whole window
Skip inactivity is worth switching on. It cuts straight through the stretches where the visitor left the tab open and did nothing.

Pinning a Recording

The bookmark icon on a row — or in the recording's header — pins a journey (Pin recording; Unpin recording takes it back). Pinned journeys float to the top of the list, show as Pinned in the quick filters and — more importantly — are never removed to make room for newer ones. At most half of a chat widget's recording slots can be held by pinned journeys, so a pin can be refused when you are already at that half.

Session Replays in Tickets

When a visitor submits a ticket while session replays are enabled, the recording of their session is attached to it. Open the ticket and choose View replay to watch it without hunting through the library — you see exactly what they were doing when they wrote to you.

For more on replays inside tickets, see the Ticket View documentation.

How It Works

Yaplet captures changes to the page, mouse movement, clicks, scrolling and input as lightweight snapshots rather than screenshots or video, so the playback is a faithful reconstruction of the page rather than a film of it. All the segments from one browsing session (shown as parts in the viewer) are grouped into a journey.

Sessions in phone browsers are recorded and played back the same way, and the Mobile quick filter finds them. Screens inside a native iOS or Android app are not recorded.

Password fields are masked automatically. Nothing else is. If a page displays data you don't want in a recording, mark it in your own HTML: gl-mask on an element replaces its text with placeholder characters, and gl-block blanks the element out entirely.

AI Apps Read Recordings as Text

Every recorded visit is also kept as a short text timeline: the pages opened, what was clicked, which fields were filled in — by their label, never what was typed — scrolling, idle time, rage clicks, clicks that changed nothing, and clicks the page was slow to answer.

An AI app connected to Yaplet through the MCP Server, and Yaplet, the assistant in your dashboard, can use these timelines to find visits, read one step by step, and sum up many visits at once to see where people get stuck — for example, which button gets the most rage clicks.

  • It needs the same Session Replays permission and plan as this page.
  • Text your website masks from recording stays hidden in the timeline too.
  • Reading the timelines costs no AI credits by itself: Yaplet only hands over the text, and the AI app that reads it does the thinking.
  • Only visits recorded since November 2026 have a timeline.
  • A timeline stays when its recording is deleted to make room for newer ones. It goes when its visitor, its chat widget or your workspace is deleted, or when a chat widget (one website) has more than its newest 2,000 timelines.

How Long Recordings Are Kept

Recordings are limited by your plan rather than by age. Each chat widget gets a number of recording slots; a longer, heavier recording takes up more than one. When the slots are full, the oldest unpinned journey is deleted to make room.

The nightly cleanup that removes long-idle visitors never touches somebody who owns a session replay, so a recording does not disappear because its visitor stopped coming back.

How long Yaplet keeps visitor data

The full schedule — conversations, website activity records, empty chats and visitors — with what is exempt from each. It is in this section, under Audience.

© 2026 Yaplet. All rights reserved.