Heatmaps & experience

Heatmaps aggregate by page template and do not draw funnel steps; those are Funnels. Which page people open next is Paths.

ConsoleAll-platform analyticsBehaviorHeatmaps

How to configure

Autocapture has to be on. If it is off, the page says so and links to project settings.

ConsoleAll-platform analyticsConfigurationSettings

Collection only records clickable elements. Password fields, anything under data-wc-ignore, the support widget, and selectors on your deny list are skipped. Element text is off by default. Scroll reach stays empty until Scroll depth is enabled in autocapture. Sampling is stable per device; below 100% the page does not listen at all.

On the heatmap, pick a row in the page list. Rows are merged by path template. Then pick a device: all, desktop, mobile, or tablet. Tabs are Clicks, Rage clicks, Scroll reach, and Elements. The date range is the statistics range, at most 92 days. You can filter by viewport width and try to lay the live page under the heat. If that fails, the coordinate map remains.

There is no metric row, breakdown, or compare period. People counts are distinct visitors.

How to read the result

The page list shows clicks, rage clicks, sessions, average maximum scroll depth at leave, and the share of clicks that have document coordinates. Inside a page, color runs from blue to red with density. With document coordinates, the vertical axis is the full page. Older clicks have only viewport coordinates, and the chart says so. The element table is the most clicked controls, their share, and visitors. Each scroll row is the share of visits that reached that depth or further.

Limits & definitions

A rage click is decided in the collector: the third click within 300 milliseconds and 50 pixels. It is not clustered later on the server. Clicks without document coordinates cannot be placed on the full page. The heatmap does not store a picture of the page; the overlay needs a URL you can still open. Session replay is a separate path, Session replay.

Session replay

Replay shows one session; clicks stacked across many people are Heatmaps & experience, and summaries such as bounce rate are Session analysis. How a session is cut is Sessions.

ConsoleAll-platform analyticsBehaviorSession replay

The page has two tabs: Recordings and Settings. Session details and the person timeline in Web analytics can also jump to the replay of that session.

How to configure

Replay is off by default. While off, the Recordings tab shows an explanation and an Open settings button.

Open the Settings tab as an admin or owner. Turning the switch on opens a confirmation. You confirm that the privacy policy tells visitors about recording, its purpose, and retention; that in the China mode recording needs consent and in the global mode it does not run when the privacy tier is too low, with the server deciding; that pages with payment, ID, or medical forms are on the exclude list; and that input masking stays on.

Options:

Option	Default	Notes
Sample rate	10%	0 to 100, 10 or less is recommended; above 10 shows a storage and performance warning
Mask input values	On	Input values are recorded as asterisks; keeping this on is strongly advised
Mask all text	Off	All page text is recorded as asterisks, for back-office style pages
Retention days	30	1 to 90 days; the cleanup job deletes after that
Excluded paths	Empty	Path prefixes starting with /, one per line, up to 20; these pages are not recorded
Recorder script URL	Built-in recorder served next to w.js	Must be https; set it only to load your own copy

After saving, the collector picks it up at its next handshake, about 10 seconds.

Collector behavior: web visits only. The sampling decision is made once per session and stored in session storage, not in a cookie. Password fields, blocks with data-wc-ignore or wc-no-replay, and the support widget are never recorded. It sends about every 5 seconds or 200 events. One session stays under 8MB before compression; over the cap, or after the project turns replay off, the server tells the collector to stop and it records no more.

There is also a separate path: set an https link template in web settings, and session details and the person timeline show Open replay pointing to your own replay service. Placeholders are session, visitor, device, person, and start time. If any event already carries a session or replay URL, that URL wins.

ConsoleWeb analyticsConfigurationWeb settings

How to read the result

Top stats. Recorded sessions, storage used (with the size before compression), sample rate, retention days, and the time of the oldest recording.

List. One row per session: time, visitor, entry page, duration, pages, rage clicks, errors, size. Filter by issues (all, errors or rage, errors, rage clicks), by page path prefix, and by minimum duration in seconds, over at most 92 days. Play replay on a row opens the player.

Player. Playback uses the rrweb player, which ships with the console and loads when you open the page. You can pause, scrub, play at 1, 2, 4, or 8 times speed, and idle stretches are skipped automatically. On the right, a timeline lists the session's page views, events, and errors; click an item to jump to that time. The timeline takes up to 500 events and 100 errors from that session. The player page also has links back to the list and to the session details. If inputs were masked while recording, the page says so.

Limits & definitions

• Chunks are stored per session. Opening one session decompresses them in order and rebuilds the events. With no data the page says the session has no replay, which may mean it is past retention or was deleted.
• Turning replay off does not delete recordings: they stay playable and are deleted after retention, but nothing new is recorded.
• Deleting one session or several (select them in the list) needs an admin; purging every replay in the project needs the owner. Deleting only removes replay chunks and does not affect session statistics. A privacy deletion for a visitor also removes that visitor's chunks.
• Every role that can enter the project can view the list, stats, and player. Only admins and above can change settings; read-only roles see a notice.
• Only the web is recorded, not apps or mini programs. This is not a replay of a support conversation.