Guides
Session replay and privacy
Turn on session replay, control sampling, and mask sensitive content before it leaves the browser.
Turn it on
Replay is controlled from Project settings → Session replay, not in code: switch it on, set the sample rate (for example 20% of sessions) and the minimum duration (short bounces are not kept or counted).
The browser SDK picks the settings up on the next page load and loads the recorder only when needed. Recordings are sent every few seconds and when the page is hidden. You can also call tracklyne.startSessionRecording() and stopSessionRecording() yourself.
Masking
By default every input is masked: the replay shows that someone typed, never what. On top of that:
| Add to an element | Effect |
|---|---|
class="tl-mask" | Its text is masked in the replay |
class="tl-no-capture" | Replaced by an empty box of the same size; also excluded from autocapture and heatmaps |
class="tl-ignore-input" | What is typed in this input is not recorded at all |
<div class="tl-no-capture">
<img src="/id-card.png" alt="Identity card" />
</div>Masking happens in the browser, before anything is sent. Masked content never reaches our servers.
Retention
Replays are kept for your plan's retention window (90 days on Free, 1 year on Pro, 2 years on Scale) and then deleted. You can delete a single recording at any time.