Session replay and heatmaps that show you why, not just what
Watch real visitor sessions and see click, scroll and movement heatmaps for any page — with inputs privacy-masked by default and rage-click detection built in, so you can find the exact moment a page stops working.
A dashboard can tell you that 40% of visitors leave your checkout page without buying. It cannot tell you whether they got confused, hit a broken button, or just changed their mind. Session replay and heatmaps close that gap — they show you the actual page, the actual scroll, the actual clicks, so "people are leaving" turns into "people can't find the form" or "people are clicking a label that doesn't do anything."
Analytics tells you that; replay tells you why
Cookieless web analytics — covered on its own page — is built for aggregate patterns: pageviews, referrers, goal completions, where traffic drops off in a funnel. It's the right tool for spotting that a page underperforms; it's the wrong tool for finding out why, because a conversion rate is a single number with no visual behind it. Session replay and heatmaps are the visual layer underneath that number: once analytics flags a page — a high exit rate, a funnel step people don't complete — replay and heatmaps let you watch what actually happened, for real visitors, and see the specific interaction costing you conversions. Analytics tells you where to look; replay tells you what you'll find.
Session recording, built on rrweb
WDIBoard records sessions using rrweb, an open approach to capturing a page as a sequence of DOM changes rather than a video file. A replay reconstructs the actual page — the real layout, the real elements, the real timing of what loaded when — instead of a blurry screen recording. You watch a cursor move, fields get focused, a menu open, a button get clicked, in the order it happened. Replays are filterable by page, device and goal, so you're not scrolling through a random sample hoping to spot the useful one — if analytics shows a drop-off on mobile specifically, you filter to mobile sessions on that page and start watching the ones that matter.
Click, scroll and movement heatmaps
A heatmap aggregates many sessions into one picture instead of asking you to watch them one at a time. WDIBoard builds three kinds for any page you're tracking:
- Click heatmaps show where visitors click, overlaid on the page — including clicks on things that aren't clickable, often the most useful signal on the map.
- Scroll heatmaps show how far down the page visitors get, pinpointing where attention drops off.
- Movement heatmaps show where the cursor lingers, which on desktop tracks closely with attention, even without a click.
Because they're built from many sessions, a heatmap answers a different question than any single replay can: not "what did this one visitor do" but "what does the typical visitor do here." Paired with individual replays, you get the pattern and the specific example that explains it.
Rage-click detection
A rage click is a fast, repeated click or tap in the same spot — what a person does when they click something, nothing happens, and they click again, faster, more frustrated each time. It's one of the clearest frustration signals a site can produce, and it's easy to miss in aggregate analytics because the click itself doesn't error or get logged as a bug. The visitor just leaves. WDIBoard detects these clusters automatically and surfaces them on the heatmap and in the session list, so a frustration pattern doesn't rely on someone noticing it by accident. It almost always means something that looks interactive isn't, or something that used to work has quietly broken.
A worked example: diagnosing a checkout page
Here's how the two tools work together, as a real investigation rather than a feature list.
-
Analytics flags the problem
Your cookieless analytics dashboard shows a checkout page with a high exit rate. You know something is wrong. You don't yet know what.
-
The scroll heatmap shows nobody reaches the form
You open the scroll heatmap for that page and see it: engagement falls off a cliff well above where the payment form actually sits. Most visitors never scroll far enough to see it. That's a different problem than "the form is confusing" — it's "the form is effectively invisible" because something above it, a promo banner or an oversized hero image, is pushing it below the fold.
-
The click heatmap and rage-click cluster find the second problem
Among visitors who do scroll far enough, the click heatmap shows a tight cluster on what looks like a "shipping options" toggle — except it isn't a toggle, it's static text styled like one. The rage-click detector has already flagged the cluster: visitors clicking it two, three, four times in quick succession, getting no response, then abandoning.
-
Replay confirms both, in context
You filter replays to that page on the goal "did not complete checkout" and watch a handful. The pattern plays out as individual behaviour: a visitor scrolls partway, doesn't reach the form, scrolls back up, clicks the fake toggle twice, closes the tab. One dashboard number, two heatmaps and a replay now point at the same two fixes: shorten what's above the form, and make the shipping toggle real or restyle it so it stops looking clickable.
That's the value of pairing the two tools: the heatmap shows where the problem is, in aggregate; the replay shows what it looks like for one real person, in motion.
Privacy: masked by default, because recording is a responsibility
Recording what someone types and how they move through your site is not a neutral feature — it's a capability that needs sensible defaults, not an opt-in trap. WDIBoard's recording is built around that:
- Inputs are privacy-masked by default. Typed form values are masked in the recording pipeline itself, before they're stored — not hidden afterward by a display filter you have to remember to apply.
- Recording is consent-aware. The recorder respects the consent state your site establishes, rather than capturing unconditionally and sorting it out afterward.
- Replays are filtered to what you need. Page, device and goal filters keep a review session focused on the interaction you're diagnosing, not a general browse through everyone's activity.
These are mechanics, not a compliance claim: masking, consent-awareness and filtering describe how the recorder is built. Whether that satisfies a legal obligation for your site is a judgment for you and your own advisor — WDIBoard doesn't make that determination.
Who this is for
Conversion and CRO-minded marketers
Turn a drop-off percentage into a specific, fixable interaction on the page.
Agencies debugging a client's site
Show a client exactly where visitors get stuck, with the same recordings and heatmaps used to diagnose it.
Developers chasing a UX bug that never throws an error
A rage-click cluster on an element that "looks fine" in code review is often the fastest way to spot what's actually broken.
Frequently asked questions
What's the difference between session replay and heatmaps?
A heatmap aggregates clicks, scroll depth or cursor movement across many sessions into one visual, showing overall patterns on a page. A session replay reconstructs one specific visit so you can watch what a real visitor did, in order. They're built to be used together.
Are form inputs recorded in session replay?
Input fields are privacy-masked by default — the recorder masks typed values before they're captured, rather than recording raw input and hiding it afterward.
What is rage-click detection?
It's automatic detection of fast, repeated clicks or taps in the same spot — a common signal that a visitor clicked something expecting a response and didn't get one. WDIBoard surfaces these clusters on heatmaps and in the session list automatically.
Does session recording respect visitor consent?
Recording is consent-aware — it respects the consent state established on your site rather than capturing unconditionally. It doesn't determine what consent your site needs to collect; that's a decision you make for your own site.
Can I filter replays and heatmaps by page or device?
Yes. Both replays and heatmaps can be filtered by page, device and goal, so you can go straight to the sessions relevant to the problem you're diagnosing instead of browsing everything.
Does session replay use rrweb?
Yes, recording is built on rrweb, which captures a page as a sequence of DOM changes rather than a video, so a replay reconstructs the real page and its real elements rather than showing a screen recording.
Watch your first session replay
Connect a site and WDIBoard starts building heatmaps and recording privacy-masked sessions right away.
Get early access