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 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 record and watch session replays?
- 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
Turn on autocapture (Pro plan and above), plus Scroll depth for scroll maps. Then open All-platform analytics → Behavior → Heatmaps, pick a page and a device, and switch between Clicks, Rage clicks, Scroll reach and Elements.
Before you start
Heatmaps are built from autocapture, so there is no separate heatmap script.
- Turn on autocapture in the autocapture card under Web analyticsConfigurationSDK code. Autocapture is included from the Pro plan.
- Turn on Scroll depth in the same card if you want scroll maps. Scroll reach stays empty until it is on.
- Optionally limit the pages: the card has page scope rules (
*as a wildcard, such as/product/*) and a list of elements to skip.
Data builds up from the moment autocapture is on. Heatmaps do not cover visits before that.
Open a page's heatmap
- Go to All-platform analyticsBehaviorHeatmaps.
- Pick a page from the list. Rows are merged by path template, so
/product/123and/product/456sit in one row. - Pick a device: all, desktop, mobile or tablet. Layouts differ, so read them separately.
- Pick a tab and a date range of up to 92 days.
| Tab | What it shows |
|---|---|
| Clicks | Where people clicked, from blue (few) to red (many) |
| Rage clicks | Spots with three quick clicks close together, a sign something did not respond |
| Scroll reach | The share of visits that reached each depth or further |
| Elements | The most clicked controls, their share and visitors |
Seeing the real page underneath
TapCub can lay your live page under the heat. The address defaults to https:// plus the project's main domain plus the page path. For a multi-domain site or local testing, change the page origin next to the switch; this is saved in your browser only.
If your site refuses to be shown in a frame, the overlay stays blank. The coordinate map still works, and you can capture a background image instead.
What is not recorded
Password fields, anything inside data-tc-ignore, the chat widget and elements on your deny list. Element text is off by default.
Clear data
Use Clear all on the autocapture card, or clear one page from its heatmap. Events you accepted in the event inbox and events sent from code are kept. For a single session rather than many people at once, use session replay.
See also: how to read a heatmap, rage click and track scroll depth.
See also: Watch session recordings.
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.