Session replay: capture and understand user behaviour
Watch what a user did, jump there from the error that interrupted them, and see everything that user did before and after. We host it, mask it, and run it for you.
Replay that starts from the problem
Most session recording tools give you a list of recordings and a search box. Ours starts from the signal: an error in the error tracker links to the replay that threw it, and the replay links to that user's full history across sessions, so you see the whole customer journey under one identity. You go from "this exception fired 40 times" to "here is what those users were trying to do" without stitching three tools together.
What you get
-
One script, replay included
The same lightweight script that captures product analytics and JavaScript errors arms the recorder. There is no second vendor to install or to explain in your consent banner.
-
Privacy-first masking, tested on every change
Masking runs in the browser before data leaves the page. Text input is masked by default, and the masking rules are covered by a conformance suite so a rule cannot silently regress.
-
A lazy recorder that stays out of the way
The base script is about 6 KB gzipped and carries no recorder. The recorder loads only on pages where replay is armed, bringing the armed weight to about 28 KB gzipped.
-
Replay never takes down analytics
Under load the pipeline sheds replay data first and keeps accepting events, so a traffic spike degrades recordings before it touches your numbers.
-
Managed, with a human contact
We size storage and retention to your traffic, watch the pipeline, and are the people you message when something looks wrong.
How teams use it
The loop we run on every engagement: an error spike shows up, we open the replays behind it, we read what those users were doing, and we write up the fix with the evidence attached. You approve it, and we implement it inside your systems or hand it to your team. That is the agentic analytics side of the service, and replay is the evidence it runs on. If you are comparing this with a self-serve platform, the PostHog, Amplitude, Mixpanel and LogRocket comparisons cover replay allowances and retention side by side. For what the loop produced for one client, read the case study.
Frequently asked questions
Does session replay slow down my site?
The base script is about 6 KB gzipped and contains no recorder. The recorder loads lazily, only on pages where replay is armed, and the page weight with replay armed is about 28 KB gzipped. Pages where replay never arms pay for the base script only.
How is personal data handled in recordings?
Masking happens in the browser before anything is sent. Text input is masked by default, and the masking rules are covered by a conformance suite that runs on every change so a rule cannot silently regress. Retention is agreed with you at onboarding.
How long are replays kept?
Retention is set per customer when we scope the engagement, based on your traffic and what you need replays for. There is no fixed sampling rate or per-replay fee to reason about; we size the pipeline for your volume and manage the storage.