Click and tap maps
Every tap and mis-click, plotted where it landed. The map is built from click events, so a hotspot is somewhere a person actually pressed.
A click map rendered over a capture of the real page, with the busiest zones ranked and scroll depth tracked page by page. It runs off the tag you already have.
“The analytics say the page converts badly. They do not say which part of it.”
A funnel step tells you where people leave. It cannot tell you what they were reaching for when they did.
“Someone screenshots the page in Figma and draws arrows on it from memory.”
The redesign argument gets won by whoever is most confident, because nobody has the actual clicks.
“We keep putting things below the fold and hoping.”
Without scroll depth per page you cannot tell a section nobody wants from a section nobody reached.
Depth decides
The average visitor stops scrolling at 58%, and the busiest zone below that line collects 2% of what the best one does. The zones are found, ranked and boxed for you — where they sit on the page is the finding.
Every tap and mis-click, plotted where it landed. The map is built from click events, so a hotspot is somewhere a person actually pressed.
The map sits on a capture of the page taken on demand, so a hotspot is over the button it belongs to rather than floating on a wireframe.
Zones are clustered and ordered by interactions and unique visitors, each openable to see what was being hit inside it.
Average scroll depth per page, tracked over time — so a section nobody wanted reads differently from one nobody reached.
Zones are ranked by interactions, unique visitors and share of the page's activity — not named, because the element identity behind a zone is not something we read yet.
Nothing here needs a funnel built first or an event named. Open the page, read the map.