Quick answer
A click map is a heatmap that shows where visitors click or tap on a page, aggregated across visits, with busier spots in warmer colors. It shows where people clicked, not why they did not, so read it with scroll depth, rage clicks and dead clicks, split by device.
Formula: Click-through rate = clicks on an element ÷ page views (or ÷ views that scrolled to the element)
What is a click map?
A click map is a heatmap that shows where visitors clicked or tapped on a page, aggregated across many visits. Each click is placed at its position on the page, and areas with more clicks are drawn in warmer colors, so the most-used links, buttons and images stand out at a glance. Most click maps also come with an element list: the controls ranked by clicks, with each one's share of all clicks.
A click map answers one question well: where did people click? It does not answer why they did not click somewhere. A button with no heat may be ignored, may be below the point most visitors scroll to, or may be invisible on phones. That is why a click map should be read together with scroll depth, rage clicks and dead clicks, and always split by device.
Click map vs scroll map vs move map
| Map | What it records | Question it answers | Works on touch devices? | Typical misread |
|---|---|---|---|---|
| Click map | Clicks and taps, by position or element | Which elements get used? | Yes (taps) | "No clicks" read as "not interesting" when it was not seen |
| Scroll map | How far down each visit got | How many visitors see each part of the page? | Yes | Average depth used instead of the share reaching each point |
| Move (hover) map | Mouse pointer positions | Where does the cursor linger? | No: touch screens have no hover | Cursor position treated as eye position |
| Rage click map | Rapid repeated clicks in one spot | Where are people frustrated? | Yes | Counted as engagement |
| Element list | Clicks per element, ranked | What exactly was clicked, regardless of layout? | Yes | Ignoring elements with zero clicks |
The CSS Media Queries specification lets a page detect whether the primary input can hover at all (hover: none on most phones), which is the technical reason move maps say nothing about mobile visitors. A click on the web is a defined event, specified in W3C UI Events: per MDN's reference, an element receives click when a pointing-device button is pressed and released inside it, or when a touch gesture is performed on it, so taps and mouse clicks land in the same map.
How to read a click map
- Pick one page template and one device. Aggregate product pages by template (
/product/*), and look at desktop and mobile separately; their layouts differ, so the coordinates do not line up. - Check the sample first. How many page views and clicks is the map built on? A map from 40 visits shows individuals, not patterns.
- Read the element list before the colors. Heat intensity is relative to the busiest spot on that map. The element list gives absolute clicks and shares.
- Turn clicks into a rate. Clicks on an element ÷ page views of the page = click-through rate. Only rates can be compared across pages, periods and devices.
- Line it up with scroll depth. For anything below the first screen, divide clicks by the views that actually reached that depth.
- Look for frustration. Rage clicks show where people expected something to happen; dead clicks, clicks that produce no change, show where something looks clickable but is not.
A longer walkthrough of reading heat colors, with examples, is in how to read a heatmap.
Worked example: one button, two devices
Sample data: a "Start free trial" button on a pricing page, measured over two weeks.
| Page views | Clicks | Click-through rate | |
|---|---|---|---|
| All devices | 1,200 | 84 | 7.0% |
| Desktop | 500 | 60 | 12.0% |
| Mobile | 700 | 24 | 3.4% |
The all-devices figure, 84 ÷ 1,200 = 7.0%, describes nobody. Split it and desktop converts at 60 ÷ 500 = 12.0%, mobile at 24 ÷ 700 = 3.4%: desktop is 3.5 times higher. The click map alone would suggest the mobile button is unappealing.
Now add scroll depth. The button sits about 1,900 pixels down on mobile, below a long feature list, and only 35% of mobile views reach it; on desktop it is near the top and 80% of views reach it.
| Views reaching the button | Clicks | Click-through rate of those who saw it | |
|---|---|---|---|
| Desktop | 500 × 80% = 400 | 60 | 15.0% |
| Mobile | 700 × 35% = 245 | 24 | 9.8% |
Among visitors who actually saw it, the gap shrinks from 3.5 times to about 1.5 times. Most of the mobile problem is visibility, not the button. The fix is layout, moving the call to action above the feature list on small screens, which is a page-structure decision covered in website layout.
Check the noise too. With 24 clicks out of 700 views, a 95% confidence interval for the mobile rate is roughly 3.4% ± 1.3 points (normal approximation: 1.96 × √(0.034 × 0.966 ÷ 700)); desktop is 12.0% ± 2.8 points. The intervals do not overlap, so the device gap is real, but a map built on a tenth of this traffic would not support the same conclusion.
Common mistakes with click maps
- Too little data. A few dozen clicks can make a random visitor's habit look like a pattern. Wait for a few hundred page views per device before drawing conclusions.
- Mixing old and new layouts. After a redesign, clicks from the old version land on coordinates that now hold different elements. Start the date range on release day.
- Mixing devices. A combined map overlays desktop and mobile coordinates that refer to different layouts.
- Ignoring dynamic content. Carousels, personalized blocks and cookie banners move elements around; coordinate heat over them is unreliable, so use the element list.
- Reading color as volume. Red on a quiet page may be fewer clicks than yellow on a busy one.
- Treating rage clicks as interest. Repeated rapid clicks usually mean a slow or broken control; see rage click.
- Forgetting what the tool does not record. Some tools record only clickable elements, so clicks on plain images or text never appear. Know your tool before concluding "nobody clicks there".
Click maps in TapCub
The pricing-page example maps directly onto TapCub's heatmap view:
- Turn on collection. Heatmaps are built from autocapture (Pro plan and above), switched on in Web analytics › Configuration › SDK code. Turn on Scroll depth in the same card, otherwise scroll reach stays empty. Data builds up from that moment; earlier visits are not covered. Setup steps: create a heatmap.
- Open the page and pick a device. In All-platform analytics › Behavior › Heatmaps, pages are merged by path template. Choose all, desktop, mobile or tablet, and set a date range of up to 92 days, starting after your last redesign. The page list shows clicks, rage clicks, sessions and average maximum scroll depth.
- Switch tabs to read the full picture. Clicks shows the heat, Elements ranks the most-clicked controls with their share and visitors, Scroll reach shows the share of visits reaching each depth or further, and Rage clicks shows frustration, defined as the third click within 300 milliseconds and 50 pixels. That is the click-plus-scroll calculation from the example.
- Know what is not recorded. Collection only records clickable elements, and skips password fields, anything marked
data-tc-ignoreand the support widget. TapCub does not detect dead clicks yet. To see one visitor's path to the button, open session replay, which is off by default.
See also: What is scroll depth? Definition, formula and how to read it.
Sources
- W3C, UI Events (definition of the
clickevent). - MDN Web Docs, Element: click event.
- W3C, Media Queries Level 4 (the
hoverandpointermedia features). - NIST/SEMATECH e-Handbook of Statistical Methods, 7.2.4 Does the proportion of defectives meet requirements? (confidence intervals for a proportion).
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 Experience Specialist
Writes about product experience, practical workflows, and growth, turning complex processes into clear steps for everyday decisions.