Quick answer
Scroll depth is how far down a page a visitor got, measured as the furthest point reached and usually shown as a percentage of page height. It shows whether content was seen, not whether it was read, and percentages cannot be compared between pages of different length.
Formula: Depth (%) = (scroll position + viewport height) ÷ page height × 100, taking the largest value in the visit
What is scroll depth?
Scroll depth is how far down a page a visitor got, usually reported as a percentage of the page's height: the 25%, 50%, 75% and 100% marks are common. It answers one question, "did the content get seen?", and only that. It does not say whether anyone read it.
For one visit, scroll depth is the furthest point reached, not where the visitor ended up. Someone who scrolls to the bottom and back to the top still counts as 100%. For a page, you then summarise many visits in one of two ways: the average maximum depth, or a reach curve showing the share of visits that got at least as far as each depth.
How scroll depth is measured
The usual formula uses the bottom edge of the screen, because that is the last pixel the visitor could see:
depth (%) = (scroll position + viewport height) ÷ page height × 100, taking the largest value in the visit.
Two details change every number:
- The first screen already counts. On a page 2,400 px tall viewed in an 800 px window, the visitor sees 33% before scrolling. On a 9,600 px page the same window shows 8.3%.
- Page height is not constant. Lazy-loaded images, accordions, infinite scroll and cookie banners change the denominator, so the same visit can score differently on different days.
Tools also differ in what they record. Google Analytics 4's enhanced measurement fires a single scroll event, once per page, when about 90% of the page's height has been shown. Other tools fire events at 25, 50, 75 and 100%, or sample the position continuously and build a curve. A single 90% event answers "did they reach the end?" but cannot show where people drop off.
Scroll depth is not reading
Three behaviours produce the same depth and mean very different things: reading carefully, skimming, and a quick flick to the bottom to look for a price or a button. Eye-tracking gives context. Nielsen Norman Group's 2018 study of 120 participants found that people spent about 57% of their viewing time above the fold (down from about 80% in 2010) and about 74% within the first two screenfuls. People do scroll, but attention thins quickly.
So read scroll depth next to two other measures.
| Metric | Answers | Weakness |
|---|---|---|
| Scroll depth | How much of the page was shown | Fast scrolling counts the same as reading |
| Time on page | How long the page stayed in view | Last page of a visit is hard to time; a tab left open inflates it |
| Engaged session | Whether the visit did anything beyond landing | A session-level flag, not tied to one page |
A page with deep scroll and a few seconds on page was skimmed. A page with shallow scroll and a long time was probably read at the top (or left open). Only together do they say something.
Worked example: why long and short pages cannot be compared directly
Sample data: two pages, 1,000 visits each, an 800 px viewport. Page A is 2,400 px tall. Page B is a long guide, 9,600 px tall. Reach is the share of visits whose depth was at least the mark.
| Depth mark | Page A reach | Page B reach |
|---|---|---|
| 25% | 100% (first screen already shows 33%) | 55% |
| 50% | 71% | 26% |
| 75% | 48% | 12% |
| 100% | 30% | 4% |
Read naively, page B is far worse: only 4% reach the end against 30%. But the marks are not the same distance. Match them in pixels. A's 100% mark is 2,400 px, which on page B is the 25% mark. At that same depth, 55% of B's visitors got there against 30% of A's. The long page holds readers better at equal distance; it just has far more distance to cover.
The same trap exists with averages. Page C: all 1,000 visits stop at about 50%. Page D: 500 visits stop at 10% and 500 reach 90%. Both have an average maximum depth of 50% ((0.1 × 500 + 0.9 × 500) ÷ 1,000 = 0.5). Yet 50% of D's visits reach the 75% mark and none of C's do, while only 50% of D's reach the 25% mark against all of C's. An average cannot tell a uniform page from a split one, so look at the curve.
Scroll maps: reading the curve on the page
A scroll map draws the reach curve on the page itself, usually as a colour gradient from hot (almost everyone sees this) at the top to cold at the bottom. It is the same data as the reach table above. Three patterns repay a second look:
- A steep drop near the top. Many visitors left after the first screen. Check that the opening matches what brought them, and how fast the page loads.
- A sharp edge in the middle. Often sits just above something that looks like the end of the page, such as a full-width banner or a large gap (a false bottom).
- A gentle slope to the bottom. What you want on a long article.
Compare the curve with where the content that matters sits. If only 30% of visits reach the sign-up block, move it up or add one higher. Always choose a device first: a long page is many screens on a phone and two on a desktop.
Common mistakes
- Comparing percentages across pages of different length. Use pixels or screens, as in the example.
- Treating 100% as the goal. Reaching the footer is not an outcome. Compare reach with where the call to action sits.
- Ignoring short pages. On a page no taller than the window, everyone "reaches 100%" on arrival.
- Mixing devices. Phone and desktop layouts differ. Read them separately.
- Reading an average. Look at the reach curve, not one number.
- Forgetting dynamic pages. Infinite scroll and lazy content make "percent of page" move while the visit is happening.
- Concluding "they did not like it". Shallow depth can also mean the answer was at the top, the page loaded slowly or the traffic was wrong for the page.
Scroll depth and scroll maps in TapCub
Take the sample guide (page B). Here is how to measure it in TapCub.
- Turn it on. Scroll depth is part of autocapture, which needs the Pro plan or higher, and it is off by default. Under Web analytics › Configuration › SDK code, turn on autocapture, then Scroll depth in the same card. No code change is needed, and data builds up from the moment you switch it on. See track scroll depth.
- Open the page. In All-platform analytics › Behavior › Heatmaps, the page list shows clicks, rage clicks, sessions and the average maximum scroll depth when people left. Rows are merged by path template, so product pages with different ids share one row.
- Pick a device first. Choose all, desktop, mobile or tablet before reading anything.
- Read the Scroll reach tab. For each depth it shows the share of visits that reached it or went further, for a date range of up to 92 days. Look for where the curve falls fastest and compare it with your key content. See create a heatmap.
- Mind the limits. Pages and elements you exclude in the autocapture card are not measured, and with a sample rate below 100% a device that was sampled out records nothing on that page. The heatmap has no metric row, breakdown or compare period, and it does not show page height, so check the page's length yourself before comparing two pages. The autocapture view in the SQL playground also carries scroll depth, for queries of your own.
TapCub reports the share of the page reached; it does not tell you whether the content was read. Pair it with time on page and engaged sessions, and see heatmaps and click maps.
Sources
- Google Analytics Help, Enhanced measurement events (the
scrollevent fires once when about 90% of the page height is shown). - Nielsen Norman Group, Scrolling and Attention (2018 eye-tracking study, 120 participants).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Data Analyst
Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.