> ## Documentation Index
> Fetch the complete documentation index at: https://tinyanalytics.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Website Heatmaps: Click, Rage-Click, and Scroll Maps
> See where visitors click and how far they scroll, rendered over your live page — without recording sessions, content, or anything a visitor typed.
A heatmap shows you what your visitors *do* on a page: where they click, where they get stuck
clicking, and how far down they actually scroll. TinyAnalytics renders all three over a live
preview of your page, from your existing [tracking script](/docs/install-tinyanalytics-tracking-script)
— there's no extra code to add.
Heatmaps here are deliberately different from session-replay tools: **nothing in the pipeline can
carry content**. That's the whole point — heatmaps that don't record your users.
## What exactly is captured?
When click capture is enabled for a site, each click records exactly this — and nothing else:
* two coordinate pairs (position in the viewport, position on the page),
* the viewport and page size at the time,
* whether the clicked element was pinned (a sticky header or floating button),
* the click type (`click` or `rageclick`),
* the page's path.
No CSS selectors, no element text, no input values, no query strings, and no DOM or session
recording. The [identify()](/docs/user-identification-analytics) id never reaches the heatmap store,
and click data expires automatically after **90 days**. Query strings are dropped before capture,
and any paths you've configured the tracker to skip or mask are skipped and masked here too.
## How do I turn it on?
Click capture is **off by default**. Enable it per site under **Site Settings → Tracking →
Heatmaps**. Once enabled, the tracker lazy-loads a small (\~1 KB) capture script on your pages;
while it's off, nothing loads and nothing is captured — sites that never opt in pay zero extra
bytes. Turning the toggle off later stops accepting capture immediately, even for pages that are
still open.
Scroll maps don't need the toggle at all: they're computed from the engagement data your
tracker already collects, so they work **retroactively** — including for date ranges before you
ever opened the Heatmaps page.
If you use a [first-party proxy](/docs/first-party-analytics-proxy), keep the prefix-wide forwarding
rule. Heatmaps use `/api/site/:siteId/tracking-config`, `/script-heatmap.js`, and `/api/heatmap`
through the same proxy prefix as the core tracking script.
## The three map modes
Open **Engagement → Heatmaps**, pick a page from the list (searchable, busiest first), and choose
a mode:
| Mode | Shows | Data source |
| --------------- | ------------------------------------------------------------------------------------------- | --------------------------------------- |
| **Clicks** | an intensity map of where visitors click — red is hottest | captured click coordinates |
| **Rage clicks** | where visitors click repeatedly in frustration (3+ clicks in the same spot within a second) | detected in the browser at capture time |
| **Scroll** | the share of sessions that reached each 10% depth of the page | existing engagement data |
The click modes also show a **fold line** — the median visitor's viewport bottom — with the share
of clicks that happen below it, and a summary of total clicks and unique visitors. You can weight
the map by raw clicks or by unique visitors.
## Device width bands
A click at x = 600 means something different on a phone than on a desktop monitor, so clicks are
never mixed across device sizes. Each map renders one **band** — Mobile, Tablet, or Desktop —
and only the clicks from viewports in that band, gently rescaled to the band's render width:
| Band | Viewport width | Rendered at |
| ------- | -------------- | ----------- |
| Mobile | under 768 px | 375 px |
| Tablet | 768 – 1099 px | 768 px |
| Desktop | 1100 px and up | 1440 px |
## The page preview
The map is drawn over a live `