Comment on the moment
Leave a note on a range of the timeline, tag a teammate, and hand over the exact fifteen seconds worth watching.
Session replay & heatmaps
Stop reading about the drop-off. Watch it happen.
Recordings attached to the metric that moved, with rage clicks, error bursts and abandoned forms already flagged. The twenty sessions that explain the number are waiting for you — you do not have to go and find them.
- Inputs masked by default
- Consent-gated
- Heatmaps included
How it is different
A replay library is not the product. Knowing which one to open is.
Evidence
The sessions come attached to the number.
The drop-off on the chart opens the recordings from the window it happened in, filtered to the sessions with friction in them. You are not searching a library by timestamp — the ones worth watching are already in front of you.
- Opened from the chart that moved, not from a search box
- Jump from a chart straight into the session that produced it
- No timestamp hunting, no second tool to keep in sync
Sessions behind this number412 with friction
- AKRage click
Checkout · 2m 22s
Desktop · Chrome · London
- BJForm abandon
Signup · 3m 28s
Desktop · Chrome · Berlin
- CIError burst
Pricing · 4m 42s
Desktop · Chrome · Austin
- DHForm abandon
Settings · 5m 44s
Desktop · Chrome · Toronto
Friction, found for you
Twenty sessions worth watching, not two thousand.
Rage clicks, error bursts and abandoned forms are detected and labelled as they arrive, so the list you open is already the interesting part of the library.
- Rage clicks, error bursts and form abandons flagged
- Filter by friction type, page, device or campaign
- Heatmaps built from the same events — click, scroll and attention
Sessions with frictionLast 28 days
Sessions100%
Friction found73%
Rage clicks36%
Biggest drop — 37% lost here · watch the friction sessions
Fixed10%
Why teams stall
Everyone buys replay. Almost nobody watches it.
“Two thousand recordings. Now what?”
Replay tools hand you a library and a search box. Finding the twenty sessions that explain the drop is the actual work, and nobody has time for it.
“The number moved. I cannot see why.”
Your metrics live in one tool and your recordings in another, so the sessions behind a drop have to be hunted by timestamp and hope.
“Legal wants to know what we record.”
A replay rollout stalls for a quarter because nobody can say, in one sentence, what is captured and who can see it.
Clip trimmed · 0:55 – 1:35
Forty seconds.
Not four minutes.
Friction is detected as sessions arrive, so the clip you open starts at the rage click instead of four minutes before it.
Detected as it arrived
1:00Rage click×7 on a disabled Apply1:31Error shown“That code isn’t valid”2:39Field abandonedPromo code, never resubmitted3:52Tab closedNo order placed
Privacy
The part that usually stops the rollout, settled up front.
Recording sessionyoursite.com/checkout
Masked by default
Inputs are masked before anything leaves the browser. Turning masking off is a decision you make deliberately, not a default you discover later.
Consent decides
Recording is gated by the consent banner. Decline and replay never starts — the same gate that governs events, not a separate switch to remember.
One sentence for legal
What is captured, where it is stored and who can open it, written down — so the rollout is a conversation rather than a quarter.
- Zero setup
- Replay comes with the tag you already installed. There is no second SDK and no separate project to create.
- Pre-filtered
- Friction is detected as sessions arrive, so the list you open is the interesting part of the library.
- One bill
- Replay and heatmaps are included on every paid plan rather than priced as their own product.
Also included
Heatmaps per device
Click, scroll and attention maps per page and per device, from the same event stream your analytics run on.
Device-accurate playback
Seven viewport profiles, so a mobile session plays back at mobile proportions instead of a squeezed desktop.
Console and network
The errors that fired during the session sit under the timeline, so a support ticket becomes a bug report.
All of it on the same events your analytics already run on — nothing extra to instrument.
In your words
The questions replay is actually for.
Type it in plain English and the sessions come back with the answer.
- What are people doing right before they abandon checkout?
- Which button do users keep clicking that does nothing?
- Is this a mobile layout problem or a pricing problem?
- Show me the sessions where the form errored.
- Can I hand the team the exact fifteen seconds that went wrong?
Before you ask
What legal, and your CTO, will want to know.
Replay should not be a second subscription.
Recording, heatmaps, comments and device-accurate playback are included on every paid plan — with product analytics, web analytics, goals and experiments on the same bill.
- Free to start, no credit card
- Heatmaps included, not an add-on
- Delete a recording — or a whole site — on request