Analytics and Tracking

Scroll Map

Also called Scroll heatmap, scroll depth map

A colour overlay showing what share of visitors reach each depth of a page before they stop.

Quick facts: Scroll Map

Category
Analytics and Tracking
Also called
Scroll heatmap, scroll depth map
Level
Beginner
Affects
Page layout, call to action placement, content length
Where to see it
Microsoft Clarity, Hotjar, GA4 scroll events via Google Tag Manager
In this article4
  1. What a scroll map measures
  2. Why scroll maps matter
  3. Common mistakes with scroll maps
  4. What to do about it

What a scroll map measures

A small script records how far down the page each visitor gets, then the tool paints the page as a gradient. The top band, which everyone sees, is drawn hot. Bands further down cool as fewer and fewer people reach them. Where the colour changes sharply, a large group of visitors stopped at the same point.

The number behind the colour is the share of visitors who reached each depth, so it only ever falls as you go down. That makes the shape more informative than any single reading. A gentle, even fade means people are working steadily through the content. A cliff edge means something at that point sent them away, or convinced them the page had ended.

Scroll depth is not attention. Someone can flick to the bottom of a long article in a second without reading a word, and a scroll map counts that as a full read. Pairing depth with time on the page, or with a heatmap of clicks, is what turns it into evidence.

Why scroll maps matter

Most disagreements about page layout are really disagreements about what visitors see, and a scroll map settles them with data instead of opinion. If the enquiry form sits below the point most people reach, its position is the problem, not its wording.

It is particularly useful for mobile-heavy audiences, which describes most traffic in Nepal. A section that sits comfortably in view on a desktop monitor can be several swipes down on a phone, and the two scroll maps for the same page often tell opposite stories. Reading them separately is the point of looking at all.

Common mistakes with scroll maps

The first is reading a fall-off as failure. Not everyone needs the whole page. A visitor who reached the pricing section, understood it and left may have got exactly what they came for, and pushing them further down would not have helped.

The second is trusting a map built on too few sessions, or one that mixes phones and desktops into a single overlay. The third is forgetting that lazy-loaded content, sticky headers and pages whose height changes as elements load can all confuse the measurement, so the depth recorded does not correspond to the layout you are looking at.

The fourth is aiming at the wrong target. Making people scroll further is not an objective; getting the right people to the right section is.

What to do about it

Start by marking the point on the page where interest drops sharply and looking at what sits immediately above it. A long unbroken block of text, an unexpected banner, a section that reads like the end of the page, or a wall of related links will all stop people. Fixing that one point usually moves the whole curve down.

Next, check that the things you need people to see sit above the depth most visitors reach, and move the call to action if it does not. Then look at the page on a phone and repeat the exercise, because that is where the gap is normally worst. Treat what you find as a hypothesis and confirm it with a proper test rather than shipping on the strength of the overlay alone. Used this way, scroll maps are one of the cheapest inputs into conversion rate optimisation a small site has.

Do and do not

Do

  • Read mobile and desktop maps separately
  • Look at what sits just above a sharp drop
  • Confirm any layout change with a proper test

Do not

  • Treat deeper scrolling as a goal in itself
  • Read scroll depth as proof of reading
  • Judge a page on a handful of sessions

Questions people ask about this

How much of a page should visitors scroll?

There is no target to hit. What matters is whether people reach the parts of the page that do the work: the offer, the proof and the call to action. A short page that everyone finishes and a long page most people leave halfway through can both be doing their job, provided the essentials sit above the point where interest fades.

Does a scroll map tell me whether people read the content?

No. It records how far the page moved, not whether anyone took it in. Somebody can flick to the bottom in a second and be counted as reaching the end. Read scroll depth alongside time spent on the page and click data, and treat a fast, deep scroll as skimming rather than as engagement.

Do I need a paid tool to see scroll maps?

Not necessarily. Microsoft Clarity provides scroll maps at no cost, and Google Tag Manager can send scroll depth events into GA4 if you would rather keep everything in your analytics. Paid tools add convenience, filtering and session recordings, but the basic picture of where visitors stop is available without spending anything.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.