Session Recordings
The Recordings screen lists all captured user sessions.
Recordings List
Navigate to Dashboard → Recordings.
Each row shows:
- Session start time and duration
- Page URL where the session started
- Browser and OS (parsed from User-Agent)
- ⚠️ Gap warning icon if the recording has missing segments
Filtering
| Filter | Options |
|---|---|
| Date range | Filter by session start date |
| Duration | Minimum session length (seconds) |
| Has gaps | Show only recordings with integrity issues |
| Has rage clicks | Show sessions with frustrated interactions |
Session Player
Click any session to open the rrweb player.
Player Controls
| Control | Action |
|---|---|
| Play / Pause | Space bar or on-screen button |
| Seek | Click anywhere on the progress bar |
| Speed | 1×, 2×, 4× playback speed |
| Skip inactive | Jump over periods of no activity |
Timeline Events
The player timeline shows coloured markers for:
- Clicks — green dots
- Rage clicks — red clusters
- Dead clicks — orange dots
- Errors — red exclamation marks (click to see the error detail)
- Segment boundaries — grey dividers (yellow if a gap exists before this segment)
Integrity Warning
If the recording has gaps (hasGaps: true), a yellow banner appears:
⚠️ This recording has missing segments: [1, 3]. Playback may skip.
Missing segments are shown as blank periods in the timeline.
Rage Clicks & Dead Clicks
Below the player, two panels show aggregated interaction data:
Rage Clicks
| Field | Description |
|---|---|
| Coordinates | X, Y position on the page |
| Selector | CSS selector of the target element |
| Count | Number of rapid clicks |
| Timestamp | When the rage click occurred |
Dead Clicks
| Field | Description |
|---|---|
| Coordinates | X, Y position |
| Selector | CSS selector of the target element |
| Timestamp | When the dead click occurred |
Use this data to identify frustrating or broken UI elements and prioritise fixes.
Notes, tags and search
A recording has no text of its own, so its searchable text is where the visit went and what your team wrote about it. The Notes & tags panel at the bottom of a recording is where that gets written.
Tags are labels with no author — a tag is not a statement, so nobody's name is attached. They
are trimmed and lowercased, so Checkout-Bug and checkout-bug are the same tag, and applying
one twice does nothing rather than creating a duplicate. Up to 50 characters each.
Notes are the team thread, oldest first. Like error comments, a note outlives its author's account: the address is copied onto the note when it is written, so a note written by somebody who has since left still says who wrote it. Notes cannot be deleted once posted.
Adding either needs the member role. Reading them needs only view access.
The search box on the recordings list matches all three of: a page URL the visit reached, a
tag, and a note body. So checkout-bug finds the sessions you tagged, and /cart finds
the sessions that got to the cart, from the same box.
There is deliberately no share link and no playlists. A shareable link is a public-access surface that needs its own security design rather than a checkbox, and playlists are a new way of organising sessions rather than an annotation on one. Recordings are visible only to signed-in members of the organization that owns the site.
Deleting Recordings
To delete a recording:
- Open the recording detail
- Click Delete in the top-right
- Confirm
Deleting a recording also removes all stored segment files.