Skip to content

Session Recording

A Session captures a real user’s interaction, recorded by your deployed widget. When Session recording is enabled in widget settings, their on-screen activity is recorded. You can replay exactly what they experienced — their navigation, clicks, scrolling, and conversation with the widget.

Session recording uses rrweb, which captures the DOM and user events rather than video frames, producing a lightweight, faithful replay.

A session captures the user’s on-screen activity from the moment the widget initializes a chat. This includes page navigation, clicks, scrolling, input, and interactions with the widget.

Every input value is masked by default — Sessions capture that a field was typed into, never what was typed. No configuration is needed to protect password or payment fields.

To exclude more of your page, mark elements in your own markup with either class:

Class Effect
mtx-mask / rr-mask Text content inside the element is masked.
mtx-block / rr-block The element is replaced by a placeholder and never recorded.

Both the mtx- and rrweb’s native rr- prefixes are honoured, so existing rr-block / rr-mask markup keeps working.

Recorded sessions live on the Activity tab of the Widget page — there is no separate Sessions page. The tab merges sessions with user prompts into one feed, below the session totals and the session-activity chart.

Each session row shows:

  • Landing URL — Where the session took place (domain and path).
  • When — The time the session started.
  • Events — How many interactions were captured.

You can also see at a glance how many sessions are Total, Active, and Completed, plus the total event count.

Filter the activity feed to the part you care about:

Filter Shows
All Sessions and user prompts together
Prompts Only the questions users asked the widget
Sessions Only recorded sessions

Click any session that has replay data to open a full replay of the user’s actions. The replay shows exactly what the user saw and did, including their conversation with the widget, and opens in a fullscreen viewer for detailed review.

  • Understand user behavior — See how users navigate your product and where they spend time.
  • Identify UX friction — Spot pages or workflows where users struggle or drop off, then dig deeper with Heatmaps.
  • Debug reported issues — Watch what actually happened when a user reports a problem instead of guessing.
  • Validate response quality — Confirm the widget is giving helpful, accurate responses in real conversations.