More in Product analytics
- Autocapture and the AI event inbox
- Build a funnel that explains drop-off
- Identify users across web, app and mini-programs
- What is autocapture, and how does it work?
- How do I review and accept events in the inbox?
- What are unplanned events, and how do I manage them?
- When should I use a funnel instead of a goal or path?
- How do I build a funnel?
- How do I read where a funnel drops off?
- What is identified mode, and should I turn it on?
- How do I call login to identify a user?
- How is one person merged across devices?
- How does identity work on apps and mini-programs?
- How do I track clicks on outbound links?
- How do I track file downloads?
- How do I track form submissions?
- How do I track custom events?
- How do I track button clicks?
- How do I create a heatmap?
- How do I track scroll depth?
- How do I track ecommerce purchases and revenue?
- How do I set up goals and track conversions?
- How do I query my data with SQL?
- How do I create a custom metric?
- How do I analyze accounts with groups?
- How do I connect AI agents with MCP?
- How do I ask the AI assistant about my data?
- How do I create user segments?
- How do I run an RFM analysis?
- How do I analyze user paths?
- How do I build a retention report?
- How do I analyze how an event is distributed?
- How do I create a tracking plan?
- How do I view a user’s profile and activity?
- How do I read the lifecycle report (new, returning, resurrecting, dormant)?
- How do I compare attribution models for a conversion?
- All guides in this category
Still have a question?
Could not find it? A person reads every message, usually within a few hours on business days.
Chat with usShort answer
Open All-platform analytics › Behavior › Session replay. Replay is off by default: an admin or owner turns it on in the Settings tab, confirms the privacy checklist and picks a sample rate (10% by default). New sessions are then recorded on your website, and the Recordings tab lists them with duration, pages, rage clicks and errors. Click Play replay to watch one.
A session replay rebuilds what a visitor saw and did in one visit: page changes, scrolling, clicks and typing (with input values masked). It is for understanding a single session; for clicks stacked across many visitors, use a heatmap.
Turn on session recording
- Go to All-platform analytics › Behavior › Session replay and open the Settings tab. You need the admin or owner role.
- Switch recording on. A confirmation asks you to confirm that:
- your privacy policy tells visitors about recording, its purpose and retention;
- in China mode recording waits for consent, and in global mode it does not run when the privacy tier is too low (the server decides);
- pages with payment, ID or medical forms are on the excluded paths list;
- input masking stays on.
- Set the options and save. The collector picks up the change at its next handshake, about 10 seconds later.
| Option | Default | Notes |
|---|---|---|
| Sample rate | 10% | 0 to 100; 10% or less is recommended. Above 10% you see a storage and performance warning |
| Mask input values | On | Typed values are recorded as asterisks. Keep this on |
| Mask all text | Off | All page text is recorded as asterisks, useful for back-office pages |
| Retention days | 30 | 1 to 90 days; recordings are deleted after that |
| Excluded paths | Empty | Up to 20 path prefixes starting with /, one per line; these pages are never recorded |
| Recorder script URL | Built-in recorder | Must be https. Change it only to load your own copy |
The sampling decision is made once per session and kept in session storage, not in a cookie. Password fields, any block marked data-tc-ignore or wc-no-replay, and the support chat widget are never recorded.
Find the sessions worth watching
The top of the Recordings tab shows recorded sessions, storage used, sample rate, retention days and the oldest recording. Each row in the list is one session: time, visitor, entry page, duration, pages, rage clicks, errors and size.
Use the filters to skip the uneventful ones:
- Issues: all, errors or rage clicks, errors only, or rage clicks only.
- Page path prefix: for example
/checkoutto see only sessions that touched checkout. - Minimum duration in seconds, to skip bounces.
The range can go back up to 92 days, limited by your retention setting. You can also jump to a replay from session details and from a person's timeline in Web analytics.
Watch a replay
Click Play replay on a row. In the player you can pause, scrub, and play at 1×, 2×, 4× or 8×; idle stretches are skipped automatically. The timeline on the right lists the session's pageviews, events and errors (up to 500 events and 100 errors). Click an item to jump to that moment, for example straight to the error a visitor hit. If inputs were masked during recording, the player says so.
A useful routine: filter to errors or rage clicks on one important path, watch five sessions, and note what they have in common before opening a ticket.
Privacy and limits
- Only website visits are recorded, not apps or mini programs, and not support conversations.
- One session stays under 8 MB before compression. Over that cap, or after replay is turned off, the server tells the collector to stop.
- Turning replay off keeps existing recordings playable until their retention ends; nothing new is recorded.
- Deleting selected recordings needs an admin; purging all replays in the project needs the owner. Deleting removes only the replay, not the session statistics. A privacy deletion for a visitor also removes their recordings.
- Every role that can open the project can view recordings. Only admins and above can change settings.
To keep personal data out of recordings, also see Keep personal data out of TapCub.
FAQ
Why does a session say it has no replay? It was not sampled, it is past retention, it was deleted, or the visit was on a page in the excluded paths. Replay also does not run when the privacy tier is too low or consent is missing in China mode.
Can I use my own replay tool instead? Yes. In Web analytics › Configuration › Web settings, set an https link template; session details and the person timeline then show Open replay pointing to your service. Placeholders are session, visitor, device, person and start time.
Does recording slow the page down? The recorder sends data about every 5 seconds or every 200 events and is loaded only for sampled sessions. Keep the sample rate at 10% or lower on high-traffic sites.
Related
Did this answer your question?
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.