Heatmaps that know who paid
See what people press on each page of your site and each screen of your app, laid over a real picture of it. One switch keeps only the clicks of people who paid later, and each count opens the replays behind it.
What people press, and what it led to
On a picture of the real page
Once a day Sumly takes a picture of your busiest public pages, on a desktop and on a phone, and lays the heat of every click over it, with the count and share on the busiest buttons.
People who paid
Where payments are tied to visits, one switch shows only the clicks of people who paid later, and the list of buttons sorts by what led to money.
Rage and dead clicks
Three or more fast clicks on one thing, and clicks on things that look pressable but do nothing, listed under the page as where it went wrong.
How far down they get
The share of views that reach a quarter, half and three quarters of the page, and the end.
Taps in your app
With the SDK in React Native or Expo, taps land on a picture of each screen the app sends, with text fields covered. Rage and dead taps too.
Replays under the heat
Click a count to watch the replays of the people who pressed it. Replay is off until you turn it on, then by default only for visitors who agreed, with what they type always masked.
Off until you turn it on
Clicks and replays are switched on per project, so nothing is collected that you did not ask for.
- Clicks on a siteTurn on Every click, without marking in the project's settings and add data-autocapture to the script tag.
- Taps in an appautocapture: true and the Touches wrapper in the SDK.
- ReplaysOff, only visitors who agreed to cookies, or everyone. Kept 30 days, no IP address kept.
- On your live siteOpen on yoursite.com paints the heat over the page itself for 15 minutes, and nothing you click there counts.
- How longSingle clicks 30 days, the count on each element 25 months, page pictures 30 days.
Questions about heatmaps
Which pages get a picture?
The busiest public pages of each project, ten per screen size, on the project's own domain. Sumly visits them like a visitor with no sign-in and follows robots.txt.
Can I see heat for one kind of visitor?
Yes: all visitors, or only the people who paid later. The switch shows where a project ties payments to visits.
Does it slow my site down?
No. The same one line that counts visits sends the clicks; there is no second script.
What does a replay record?
The page and what people do on it. What they type, passwords and card fields are always masked, and anything marked data-sumly-ignore is never recorded.
Do bots end up in the heat?
No. A view the bot filter keeps out is never a visit, so its clicks and replays are dropped too.
Goes well with
Try it with your own projects
Sign in with Google or a code by e-mail and connect your first project. The first 14 days of a paid plan are free, with no card.
Start free trialOr look around first: open the live demo.