Session replay
Watch the exact session where things went wrong.
Every session recorded, tied to a real person, and linked to the errors and drop-offs it produced. Stop guessing what happened. Watch it.
Every recording opens from the person, the error, or the funnel step it belongs to.
What you get
Pixel-accurate playback
Sessions replay exactly as the visitor saw them: scrolls, clicks, inputs, and page transitions.
Linked to errors
Every JavaScript error is grouped and linked to the replay of the session that hit it.
Frustration signals
Rage clicks and dead clicks are flagged automatically, so the worst sessions surface first.
Tied to real people
Replays attach to visitor profiles. Watch every session one person has ever had, in order.
Privacy masking
Sensitive inputs are masked before they leave the browser. What you never capture can never leak.
Zero setup
Recording starts with the same one-line snippet as everything else. No separate tool, no extra tag.
What is session replay?
Session replay records how a visitor actually experienced your site and lets you play it back like a video: every scroll, click, and page change. Instead of inferring behavior from charts, you watch it directly. You see where someone hesitated, what they tried to click, and the exact moment they gave up.
In OakData, replay isn't a bolt-on. It's captured by the same snippet that powers your analytics, so every recording is already connected to the visitor's profile, their events, and the funnel step they were on.
From a bad metric to the exact session
A drop-off number tells you something broke. A replay shows you what. When checkout conversion dips, filter to the sessions that reached checkout and didn't finish, then watch them: the error toast that never cleared, the coupon field that ate the tap, the form that reset on back navigation.
Because errors are grouped and linked to their recordings, going from "TypeError in checkout.tsx" to watching a real user hit it takes one click. Your agent can pull the same replay list over MCP.
Privacy comes standard
Replay only earns its place if you can trust what it captures. OakData masks sensitive inputs at the source, before data ever leaves the visitor's browser, and gives you control over what gets recorded. The replay privacy docs cover exactly how masking works.
Questions
Session replay records a visitor's real interactions with your site (scrolling, clicking, typing, navigating) and plays them back like a video, so you can see exactly what they experienced instead of guessing from aggregate charts.
No. Recording happens in the browser asynchronously and data is batched before it's sent, so it doesn't block rendering or interaction. It's the same snippet that powers the rest of OakData.
Sensitive inputs are masked in the browser before anything is transmitted, so passwords and private data never reach our servers. You control the masking rules, and the replay privacy docs cover the details.
Yes. Every JavaScript error is grouped, counted, and linked to the recordings of the sessions that hit it, so you can go from an error report to watching a real occurrence in one click.
No. Replay, analytics, funnels, heatmaps, and error monitoring all come from the same snippet and live on the same visitor profile. Every feature is included at every pricing tier.
Related
Try it
Session replay is five minutes away.
One snippet, every feature, at every tier. Free for the first 14 days.
14-day free trial