Open the recording at the error
Replay correlates recordings with the application, environment, session and recorded time. When a captured error has matching coverage, open playback at its timestamp. Person links appear after analytics resolves the session identity, so you can follow the investigation into the relevant profile with the required permissions.
Collect deliberately
Recording starts only after an operator enables collection for an environment and the visitor grants the separate replay consent. Session sampling can record selected visits throughout. Error-buffer sampling can hold a masked snapshot and recent interactions locally, then upload when a captured SDK error triggers it.
Keep sensitive content out of playback
Text and input values are masked, and masking cannot be disabled. Exclude entire elements with private selectors. Playback runs in a script-disabled sandbox without fetching the recorded website's assets. Metadata browsing and payload playback have different permission requirements, and operators can delete a recording with an audited reason.
Put it to work.
Start with one application and verify the data you send.
- Add @saaspro/replay alongside the browser SDK and exclude private areas of your interface.
- Enable environment collection, choose sampling and retention, and wire separate analytics and replay consent choices.
- Find a recording in Analytics, or follow a captured error to the matching playback timestamp.
Replay reconstructs masked layout and interactions; it is not video or a pixel-perfect screenshot. Images, canvas, media, embedded frames and network bodies are excluded. Duration, storage, sampling and retention limits determine available coverage.
Module availability and retention vary by plan. Compare plans and limits.