Enable sampled replay
sessionReplaySampleRate is evaluated only for sessions included by sessionSampleRate. See
RUM data sampling for the effective-rate calculation.
Start or stop recording manually
sessionSampleRate. Starting recording
creates a new full DOM snapshot so the replay can be reconstructed.
Recorded events
The recorder captures:- full DOM snapshots and incremental DOM mutations;
- pointer movement and clicks;
- scrolling and viewport changes;
- input interaction with values masked;
- stylesheet state and accessible inline styles;
- media state supported by rrweb.
checkoutInterval:
Privacy controls
All input values are masked. With the defaultdefaultPrivacyLevel: 'mask', all page text is also
masked. Define block, mask, and ignore selectors before enabling production replay.
Optional high-volume capture
The following options are disabled by default because these options can substantially increase payload and storage size:Transport and retention
Replay uses a separate queue and defaults to a 10-second flush interval with 100 events per batch. UsereplayFlushInterval and replayBatchSize to tune client behavior. MoleSignal compresses replay
segments in object storage and expires stored segments after the platform’s default stream retention,
set in Settings → Data retention.
Verify replay
1
Record a non-sensitive test journey
Navigate through multiple pages, click controls, scroll, and trigger one DOM update.
2
Open the session
Go to RUM → Explorer, query
session.has_replay = true on Sessions, and open the newly recorded session.3
Check reconstruction and masking
Verify the page structure, event timing, progress controls, blocked regions, and masked values.
4
Check what the session page shows
A session shows a replay only after MoleSignal receives a valid full DOM snapshot; until then the session page shows the action timeline.
Data sampling
Estimate replay coverage and volume.
Privacy
Define the recording boundary before rollout.