Wakeline
← All features
Understand

Session replay

Watch how real users move through your product to see exactly where they get stuck. Replay real sessions — clicks, scrolls, and navigation — with privacy built in.

replay · session_8f3a
Upgrade
0:140:42

See real journeys

Replay actual sessions to understand how people navigate — not how you assume they do.

Find the friction

Spot exactly where users hesitate, loop back, or drop off.

Private by default

Passwords, emails, and any field you mark are masked before anything leaves the browser.

how it works

Live in three steps.

01

Turn it on

Enable capture and set your sample rate.

02

Let it record

Sessions stream in from your installed app.

03

Watch & learn

Scrub the timeline, follow the cursor, fix the snag.

a real example

Watching five checkout drop-offs instead of guessing.

The funnel says users abandon at shipping details. Nobody knows why — so everyone has a theory. Five replays end the theorizing.

01

Build the playlist

Create a playlist: URL contains /checkout, duration at least 30 seconds, identified users only. New matching sessions join automatically — a standing watchlist, not a one-off search.

02

Watch at speed

Play at 2×, with skip-idle jumping the away-from-tab gaps. Violet dots mark every click on the timeline — jump dot to dot instead of scrubbing blind.

03

See the actual problem

Three of five sessions: rapid-fire clicks on the address validator as it rejects a correct-but-unusually-formatted postcode. Not a UX mystery — a regex bug.

04

Close the loop

File the bug with the replay attached; watch the same playlist after the fix ships to confirm the pattern is gone. Then aim a tooltip at the field for the interim.

What to expect: An afternoon of watching beats a month of debating. Masking is on by default — passwords, emails, phone numbers, and anything you mark with data-wakeline-mask never leave the user's browser.

honest limits

When not to use session replay.

No pattern fits every job. Here’s where we’d point you at something else — sometimes ours, sometimes not.

As surveillance

Replay exists to fix experiences, not to monitor individuals. Watching a specific person's sessions without a support or debugging reason is a line — access it accordingly and delete on request (one click per session).

Replacing aggregate analytics

Ten sessions are anecdotes; funnels are the census. Use replay to explain a number the funnel already flagged, not to invent patterns from whatever you happened to watch.

Full-volume recording on huge traffic

You rarely need every session — that is what the sample rate is for. Record a percentage, keep retention tight (default 30 days), and let playlists concentrate the sessions worth a human's time.

Compliance-restricted screens

For screens with regulated data, mask aggressively with data-wakeline-mask — or keep the SDK off those routes entirely. When in doubt, your privacy team outranks your curiosity.

questions

Session replay: common questions.

Still stuck? Read the docs or talk to us.

What does a replay capture?

Clicks, scrolls, navigation, and DOM changes reconstructed into a watchable session — with a scrubbable timeline, 1×/2×/4×/8× speeds, click dots you can jump between, and amber idle bands that skip-idle hops over automatically.

How is user privacy handled?

Mask-sensitive-inputs is on by default: passwords, emails, and phone numbers are hidden, and anything you mark with data-wakeline-mask is masked even if the toggle were off. Masked content never leaves the browser, and any session can be deleted immediately for privacy requests.

Will recording slow my app down?

The recorder is built to be lightweight, and the sample rate lets you dial volume to your traffic — record 10% of sessions on a high-traffic app and you keep plenty of signal at a fraction of the footprint.

How long are sessions kept?

Your retention setting, 1–365 days (default 30) — older sessions delete automatically. Short retention is usually right: replays are for recent diagnosis, not an archive.

What are playlists for?

Auto-grouping sessions by conditions — URL contains, minimum duration, identified-only. "Checkout drop-offs: /checkout, ≥30s" builds itself a watchlist; new matching sessions join without anyone curating.

See it on your own app.

Ship your first guide in minutes. Free to start — no credit card.