SESSION REPLAY
See the journey behind the signal
Replay recorded sessions in the Noxtica console, beside risk and diagnostic context. Recording begins after your tenant policy, consent and privacy gates admit it.
WHAT IT DOES
Review sessions with privacy gates in front
Session replay records page structure and interactions for sessions that pass your tenant's gates.
Admission gates
- Tenant policy
- Legal basis
- Privacy signals
- Sampling
- Consent
Every gate must admit a session. Until then a bounded buffer stays in browser memory and is not sent.
Recording begins
Console player
Risk context beside the recording
- Interaction evidence
- Diagnostics
A replay is a reconstruction of page structure and interactions, not a video.
Password field
Password, credential and card fields stay masked at every setting.
Recording that waits for admission
Tenant replay policy, legal basis, privacy signals, sampling and consent must all admit a session. Until then, a bounded buffer stays in browser memory and is not sent.
Masking set by the customer
Your team chooses how much page content is masked. Password, credential and card fields stay masked at every setting. Looser settings record more readable text.
A session view built for review
Open a recorded session to see its timeline, interaction evidence and diagnostics. Risk context appears beside the recording.
Find sessions worth reviewing
Search recorded sessions and look for similar ones to widen an investigation.
HOW IT WORKS
From page load to reviewed session
Replay is a separate data path from risk lookups and has its own admission gates.
Your page
Early-capture helper and collector
The helper holds a bounded buffer in memory. It has no transport.
Admission gates
Admission decides
Buffered in memory, not sent
Tenant policy, legal basis, privacy signals, sampling and consent are checked. Denying or disabling replay discards the buffer.
Console
Replay beside risk and diagnostics
Admitted sessions
Played under operator roles and retention settings.
Load the browser script
Your pages load a small early-capture helper and the Noxtica browser collector. The helper holds a bounded buffer in memory and has no transport.
Admission decides
Tenant policy, legal basis, privacy signals, sampling and consent are checked. Denying or disabling replay discards the early buffer.
Review in the console
Admitted sessions are replayed in the console beside risk and diagnostic context, under operator roles and retention settings.
WHERE IT FITS
Questions replay helps answer
Replay adds context to a signal. It does not replace the signal or your policy.
What happened around a risk signal?
A score tells you what changed. A replay can help explain where it happened and what the visitor experienced.
Where did a journey break?
Interaction evidence and diagnostics can help support and engineering teams find the step that failed.
Can support join a live session?
For eligible in-progress sessions, a live view can support consented investigation. It asks for its own consent and a separately authorized role.
HOW TEAMS CONNECT IT
Connect it in your pages and console
Replay uses the same browser collector as the rest of Noxtica.
- Add the early-capture helper and the Noxtica browser collector to the pages you want covered.
- Connect your consent tool so the page reports replay consent through the documented browser consent call.
- Set replay policy, masking, sampling and retention in the Noxtica console.
LIMITS
Boundaries and responsibilities
Replay records sensitive interaction content. These limits apply to every deployment.
- Controlled availability. Recording is off until a tenant enables it, and access is agreed with Noxtica for each tenant.
- You are responsible for notices, consent, masking, sampling and retention. You must also make sure special-category data and government identifiers are not recorded without a lawful basis.
- A replay is a reconstruction of page structure and interactions, not a video. Some styles, images or elements may not appear as the visitor saw them. Sampling and plan limits apply.
- Risk context beside a recording is probabilistic and can be wrong. Your team decides what to do with it.
Monitoring and replay must follow your notices, consent and masking settings, and our acceptable use rules.Read the acceptable use policy
FAQ
Questions about session replay
Does replay record every visitor?
No. A session is recorded when tenant policy, legal basis, privacy signals, sampling and consent all admit it. Denying or disabling replay discards the early buffer.
Who decides how much is masked?
Your team does. Masking is a tenant setting, and looser settings record more readable text. Review the setting with your privacy advisers.
Does monitoring consent also cover replay?
No. Replay has its own consent category, separate from analytics and monitoring.
Related products
SESSION REPLAY
Ask about session replay access
Access is agreed with Noxtica for each tenant. Contact the team to confirm eligibility, domains and your consent setup.