Skip to content

Session Recording

A Session is a recording of a real user’s interaction captured by your deployed widget. When a user interacts with your application through the widget, their on-screen activity is recorded so you can replay exactly what they experienced — their navigation, clicks, scrolling, and conversation with the widget.

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.

By default, the recorder captures input field contents. To keep specific elements or inputs out of recordings, mark them in your own page markup with these rrweb CSS classes:

  • rr-block — the element is recorded as a placeholder; its contents are not captured.
  • rr-ignore — input events on the element are not recorded.

Apply these classes to any element that may contain sensitive information (for example, password or payment fields) before deploying the widget.

Recorded sessions appear in two places in the dashboard:

  • Sessions page — A dedicated page listing all recorded sessions for the current Application.
  • Widget → Activity tab — Recent sessions appear inline alongside user prompts, with a session-activity chart. Filter the feed by All, Prompts, or Sessions.

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 sessions by status:

| Filter | Shows | |--------|-------| | All | Every recorded session | | Active | Sessions currently in progress | | Completed | Sessions that have ended |

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 UX Research.
  • 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.