Session replay
Session replay records how visitors use your pages (scrolls, clicks, page changes) so that you can watch a visit back. It is turned on per project in the dashboard, within your plan's quota.
What is recorded
- The page structure and its changes, clicks, focus, scrolls and navigations. Mouse movement is not recorded.
- All form inputs are masked: what visitors type is never recorded.
- Browser console errors and warnings (up to 200 per session), to help debugging.
Recording stops for the rest of the page as soon as the server declines it: replay off for the project, or quota reached.
Hiding content
Add these classes to elements that must not appear in recordings:
| Class | Effect |
|---|---|
rr-block | The element is replaced by an empty box of the same size. |
rr-mask | Its text is masked. |
rr-ignore | Input in this field is not recorded. |
<div class="rr-block">Account balance: 12 430 €</div>
<p class="rr-mask">Jane Doe, 12 rue de la Paix</p>
Content Security Policy
When a recording starts, the recorder is loaded from https://cdn.sublimanalytics.com (replay.min.js, packer.min.js, console-plugin.min.js). Under a strict CSP, either allow that origin in script-src, or bundle the recorder with the npm package:
init({
projectId: 'YOUR_PROJECT_ID',
replay: () => import('@sublim_analytics/tracker/replay'),
});
See CDN files for the full list of origins.
Turning it off
Turn it off for the project in the dashboard, or for a site from the snippet:
sublim.o = { projectId: 'YOUR_PROJECT_ID', sessionReplay: false };
This also turns off the frustration signals.