Heatmaps: where visitors click and how far they scroll

Traffic tells you how many people opened a page. Heatmaps show what they did on it: what they click, what they skip, where they expect a link that isn't there, and how far down they actually scroll. Everything is drawn on top of your site itself, not in a table.

It lives in Marketing → Heatmaps in the CRM, on the Pro plan. There are two modes:

• Clicks — a heatmap: the more clicks a spot gets, the redder it turns. Next to it is a list of the most clicked elements.
• Scroll — the page is colored by the share of views that reached each height, with lines marking where 75%, 50%, 25% and 10% scrolled to.

#How to turn it on

1. Add the widget script to your site

   The same single tag used for analytics and leads — see the quickstart. If it's already there, you don't need to add anything.

2. Turn on collection on the heatmap page

   Marketing → Heatmaps, the “Click collection” switch at the top of the page. Collection is off by default: clicks on a live site add up to a lot of data, so only collect them where someone will look at the map.

3. Wait for the first visitors

   The widget picks up the setting within ten minutes — it remembers the answer so it doesn't have to ask the server on every page. After that, every click and every scroll lands on the map and shows up in the CRM within a few seconds.

#What is collected and what isn't

For each click, the widget sends:

• the element that was clicked — a short CSS path like #top>div:nth-of-type(1)>button:nth-of-type(1);
• the position inside the element — as fractions of its width and height, so the dot lands on the same part of the button on any screen;
• a fallback point on the page — in case the element no longer exists in the current layout;
• the window width — used to file the click under phone (narrower than 768 px), tablet (768–1023 px) or desktop;
• a “dead click” flag — whether it hit a link or button, or an image, text or empty space.

For each page view — how far down, in percent of its height, the person scrolled.

Never collected: element text, anything typed into fields, keystrokes and mouse movement. A click in an input field puts only the field itself on the map, not what's written in it. Clicks on our own chat and sign-in window don't end up on the map.

#How to view the map

The CRM opens a page of your site in a full-width frame — just like Live — and the widget draws the hotspots or scroll bands on top of it. Above the frame:

• Clicks or Scroll — the map mode.
• Device — desktop, tablet or phone. The frame takes the device's width, so clicks land on the layout they were made in.
• Page — pages with clicks in the period, most clicked first. You can also type a path.
• Period — 7, 30, 90 days or a custom range.
• Buttons to reload the page in the frame and to open it on the site in a new tab.

Below them is a line with the numbers for the selected page. In clicks mode: how many clicks, how many visitors clicked, and what share of clicks were dead clicks. In scroll mode: how many views, the average depth, and how many views reached 25, 50, 75 and 100% of the page.

The “What gets clicked” button in the same line opens a list of the most clicked elements over the frame. The labels are taken from the page itself — button text, image captions — not from visitor data. Click a row and the element scrolls to the center and gets highlighted. Following a link inside the frame opens the map of the page you went to.

#Dead clicks

The “Dead clicks” share and the “not a link” badge in the list are the most useful hints the map gives. These are clicks on a product image, a heading, a price: the person expected to go somewhere, and nothing happened. Often that's a ready-made list of fixes — make the image link to the product, turn the card heading into a button.

#Scroll

In scroll mode, the color shows the share of views that reached that height: red — everyone sees it, blue — almost no one. A labeled dashed line marks where every fourth visitor stops scrolling, then half, and so on. If an important block — pricing, a lead form — sits below the 25% line, fewer than a quarter of visitors see it.

#Who sees the map and who turns on collection

• The site owner — everything: views the map and turns collection on or off.
• Managers — according to their access to the “Marketing · Heatmaps” section in Managers: “View” lets them open the map but not touch the switch; “Edit” also lets them turn collection on or off. Without access, the section isn't in their menu.
• Every time collection is turned on or off, it's recorded in the site's Audit log: who and when.

Heatmaps are only available on the Pro plan. If the plan changes to one without them, or the CRM is closed after the paid period ends, collection stops on its own — new clicks aren't recorded even with the switch on. What's already collected stays until the end of its retention period and becomes visible again when the section comes back.

#What your site needs

• The widget script on the pages you want to see on the map.
• Permission to open the site in the CRM frame — the same as for Live: the X-Frame-Options and frame-ancestors headers. Without it, clicks are still collected, but the CRM can't overlay them on the page.
• data-crm-* markup and the Content API are not needed for the map.

#Why dots sometimes shift

A click is tied to an element, so the map survives different screen widths and small text edits. But if the layout is rebuilt — a block moved, more buttons appeared — some clicks won't find their elements. Those clicks are drawn at the fallback point, and a warning above the frame shows what share of them has “drifted”.

#React, Vue and Next sites

The widget detects navigation inside a single-page app on its own (just like page views): the previous page's scroll is sent, and the new one starts its own. The query string doesn't matter — /pricing?plan=pro and /pricing are one page on the map.

#Limits

• Retention — 90 days, after which clicks and scroll data are deleted.
• Points on the map — up to 4,000 distinct spots on a page per period: clicks on the same spot add up into one weighted point, so on a live site that's more than enough.
• The “What gets clicked” list — the 40 most clicked elements; the page list — the 200 most clicked pages.
• Clicks inside the CRM don't count: neither in the map frame nor in Live — that's your work, not visitors. Your own clicks on the open site do count, like any visitor's.
• Clicks, like all analytics, come from visitors' browsers. We filter out bots by browser signals and rate-limit requests from a single address, but there's no way to tell a fake from a real person for certain — here or in any other web analytics.

#If the map is empty

#Clicks don't show up

• The “Click collection” switch at the top of the page must be on. Clicks weren't collected before it was turned on — there's nothing to show.
• Less than ten minutes have passed since you turned it on — the widget doesn't know yet. Reload the site page later.
• Consent mode. If consent mode is on for the site, clicks only come from visitors who gave consent.
• The wrong period or device is selected. Try “Phone”, for example — this page may not have had any desktop clicks yet.
• The script isn't on this page — on sites with separate templates for different sections, it's easy to miss.

#The frame is empty or “The heatmap did not open”

• The site forbids embedding — the CRM shows which header is blocking it. Allow embedding in the CRM.
• “The heatmap did not open” — the page loaded, but the map layer didn't respond: the open page has no widget script, or the browser is holding an old copy of the page. Click “Try again” or the reload button above the frame.