Heatmaps & zones

Which element earns the click, which one wastes it

Heatmaps are drawn over the page rebuilt from a real session, not a screenshot. Zones turn the clicks into a table per element, and Explain this page tells you what to change.

AI insights & Ask Agents Journeys Heatmaps & zones Forms Replay Segments Reports MCP Mobile Experiments Surveys Comments & sharing AI agent analytics Data platform

Zones

A row per element, with what the click is worth

The top 40 elements by clicks on a page, grouped by selector and labelled by your data-clickiq-name when you set one. For each:

Click rate (sessions that clicked it over sessions that viewed the page) and click share
Dead and rage clicks, and the dead rate
Time to first click, the median from the pageview
Lift: conversion of sessions that clicked it against those that did not
Reach: the share of sessions that scrolled far enough to see it

Hover a row and the element is outlined inside the rebuilt page; switch on the top 12 zones for the zoning view with click shares.

Click heatmap on the Ridgeline Shell Jacket product page with the top zones outlined and labelled (‘#1 ★ 4.8 · 3,012 reviews · 25%’, ‘#2 Add to cart · 16%’), a scroll-depth panel, and a Zones table listing clicks, click rate, rage, dead, time to first click and lift. — The most-clicked element on the page is the review stars (254 clicks), and 160 of those clicks (63%) are dead. ‘Add to cart’ has a 15.61× lift on conversion.

Explain this page

What to fix and what is working, from the table

The explanation is written from the real zone table, the scroll bands and a set of rule flags, and it may only cite them. On the demo cart page it reports that 303 of 830 clicks on the Apply coupon button did nothing (37%), with 153 rage clicks, and that sessions which clicked it converted at 28% against 69% for those that did not. The Checkout link has an 8.7× lift, but people wait a median 17 seconds before clicking it.

The answer is checked: findings must be of a known kind and name selectors that exist in the table; otherwise the rules answer is used. From here, Investigate sessions on this page starts an investigation over the frustrated ones.

‘Explain this page’ panel for /cart (691 sessions, 1,368 clicks) with an AI narrative, five findings (Dead clicks: ‘Coupon button broken for 37% of clicks’; Rage clicks; Converts: ‘Checkout button is the conversion engine’; Hesitation; Scroll) and a five-item ‘What to change’ list. — The finding: button#apply-coupon gets 61% of all clicks (830), 37% of them dead, and sessions that click it convert at 28% against 69% for those that don’t (lift 0.41×). The first item under ‘What to change’ is to fix that dead-click bug.

How it works

From raw clicks to a checked explanation of one page

The snapshot is a real session's DOM rebuilt by rrweb, so the overlay lines up with the element even on a single-page app.

What you can ask

Questions this answers

Type them into Ask, give them to an agent as a goal, or send them through MCP from your own assistant.

Explain /cartFindings: dead, rage, winner, hesitation, scroll

Which element do people click that does nothing?Dead clicks per element with the sessions

Is the checkout button seen on mobile?Reach and click rate for the mobile layout

Which call to action is ignored?Elements most people see but under 2% click

Does clicking the reviews link help conversion?Lift for that zone, with a custom goal if you set one

How far down the page do people get?Scroll bands: the share reaching 50% and 90%

Outcomes

What teams do with it

Fix broken controls the day they ship

Dead and rage zones surface as signals with the sessions and the revenue at risk.

Move what converts into view

Lift and reach together show a winning element that half the visitors never see.

Settle layout debates with numbers

Click share and time to first click per element, by device.

Where it stops. Native screens have tap, rage and dead layers but no scroll layer. Reach is approximate: it uses each session's deepest scroll and the page's median height; sessions without a scroll sample are left out.