Quick answer
Session replay reconstructs a single visitor session from recorded page structure changes, mouse movement, clicks, scrolls and inputs, so you can play it back like a video. It is a rebuild of the page, not a screen recording.
What is session replay?
Session replay lets you watch one visitor's session: where they moved, what they clicked, where they scrolled and hesitated, and what the page did in response. Most tools record the page's structure (the DOM) and every change to it, plus user events, then rebuild it in a player. It is not a camera on the screen, and nothing outside the tab is recorded.
When replay beats a report
Aggregate reports tell you where people struggle; replay shows why:
- A funnel step loses 40% of people, and the numbers alone do not explain it.
- A heatmap shows clicks on something that is not a link.
- Support gets "the button does nothing" and cannot reproduce it.
- A script error spikes and you need to see what the user did just before.
Choose sessions, do not browse
Watching random sessions wastes hours. Work from a question:
- Start from a drop. Pick the funnel step or page with the problem.
- Filter the list to sessions on that page with errors or rage clicks, and a minimum duration so bounces are skipped.
- Watch five to ten sessions and write down what repeats: a validation message nobody sees, a price that appears late, a tap target too small on mobile.
- Count it. Turn the pattern into an event or a funnel breakdown so you know how many people it affects before you fix it.
Privacy settings to decide first
| Setting | What to choose |
|---|---|
| Inputs | Mask them; never record what people type into forms |
| Sensitive pages | Exclude payment, ID, medical and account pages |
| Sampling | Record a share of sessions, not everything |
| Retention | Keep recordings only as long as you need them |
| Notice and consent | Say it in your privacy policy; ask for consent where required |
Session replay in TapCub
Replay is in All-platform analytics › Behavior › Session replay, for web visits only, and is off by default. An admin or owner turns it on in Settings and confirms the privacy points. Defaults: 10% sample, input values masked, recordings kept 30 days (1–90), up to 20 excluded path prefixes; password fields and blocks marked data-tc-ignore are never recorded. The list filters by errors, rage clicks, page and minimum duration, and the player has a timeline of the session's pageviews, events and errors. See the replay docs.
See also: Watch session recordings.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.
Product Adoption Consultant
Explores customer onboarding, live conversations, and self-service, turning common usage questions into practical guidance and improvements.