presagioTHE FOUNDER'S PERSPECTIVE
THE PRESAGIO HELP CENTER

From finding
to moment.

Session replay guide · 13 September 2026

See the interaction behind an outcome. Start with an event, find its recording and open the moment that matters.

Replay is a deliberate choice. Your administrator must enable the website policy, your installation must opt in, and your visitor must separately permit replay. Existing installations do not start recording automatically.

Start with an answer. Watch the moment.

  1. Open a journey’s event evidence, a conversion under Acquisition, or a stored event under Activity → Detailed events.
  2. Select Find recording. Presagio checks for an authorized recording covering that exact event’s source, browser and session.
  3. Select Watch session to open the player at the event’s relative time.

Play or pause, change speed, drag the timeline or use keyboard controls. The top navigation remains available and the return button takes you to the originating view. Deep links retain the recording, source and selected time; browser history preserves the surrounding analytics context.

Positions change at observed timestamps, without inferred movement between them. An event may fall inside a segment without having a visible marker. The demo uses clearly labeled fictional recordings to demonstrate the same flow.

Enable a website deliberately.

In connection setup, the Private session reconstruction card shows the website’s current replay policy. An owner or administrator can explicitly enable or disable it. If the policy cannot be confirmed, check again before changing it; a lost response does not prove a write failed.

When generating the integration package, Include optional session replay in this installation is unchecked by default. Selecting it adds replay: { enabled: true } to the browser SDK configuration. Copy the updated package into your frontend and connect your consent controls.

Private reconstruction. Clear boundaries.

The first version reconstructs page geometry, pointer and click positions, viewport changes and supported event markers. It is not video. Text, input values, HTML, arbitrary CSS, page URLs, images and remote resources are not included in playback.

Password fields, editable areas, embedded frames, canvas and other excluded regions remain opaque. Unsupported content looks simpler than the original page. No customer page is loaded as a fallback.

Recordings are private. Every manifest and chunk read checks current access and lifecycle state. Deletion or expiry can make a previously saved link unavailable.

Know what the evidence can show.

BoundaryWhat to expect
Up to ten minutes per segmentStructural, queue or upload limits can stop capture earlier.
Seven-day retentionReplay data expires seven days after capture begins.
Partial captureAn incomplete segment or stopped reason is shown explicitly. A missing final chunk is never presented as complete.
Missing sequenceThe chain is unavailable rather than silently playing through a gap.
No matching recordingConsent may not have been granted, capture may have been disabled, or the segment may have expired or been removed.

This guide describes replay’s first release. It does not mean recording is enabled for your website. Check the source policy, installation and consent configuration before expecting recordings.

The earlier downloadable PDF does not cover replay. Use this web supplement alongside the main help guide.