Core features
Heatmaps
Rendered over the page itself, so “nobody sees the second CTA” stops being a hunch.
Two maps
- Clicks — where people actually click, including the things that are not links.
- Scroll — how far down the page visitors get, so you can see where attention stops.
Both are split by device, because a desktop click map and a mobile one rarely tell the same story.
How the page underneath is shown
Seentics renders your live page inside the viewer and draws the heat layer over it. You can switch to Heat only to see the data on its own — useful when the page has changed since the data was collected and the overlay no longer lines up.
Heatmaps come from recording data
Click and scroll points are derived from the same event stream as replays, so a page needs traffic with recording enabled before a map has anything to show.
Reading a map
- Red is the highest concentration of clicks in that map, not an absolute number — a busy page and a quiet one both have a red spot.
- The point count is shown in the header. A map built from a few dozen points is an anecdote, not a finding.
- Compare like with like: filter to one device before drawing conclusions about placement.
Excluding elements
Elements marked data-seentics-block are not captured, so they will not appear in a heatmap either. See the tracker reference.