Scroll Depth Tracking: Measure Engagement Beyond the Fold
Scroll depth tracking measures how much of a page a user actually sees, not just that they landed on it. It fires analytics tags at specific scroll points, like 25% or 75% down the page, to gauge engagement on long articles.
Why it exists
Standard pageview analytics can't tell you if a user saw content below the fold. Scroll depth tracking was created to solve this by providing data on how far down a page a user actually travels, giving a better proxy for content engagement.
The mental model
Think of scroll depth tracking as a series of invisible tripwires on a webpage. A pageview tells you someone entered the room. Scroll depth tells you if they walked past the 25%, 50%, and 75% marks, indicating how much of the room they actually explored.
How it works
A scroll depth trigger is configured to fire tags when a user scrolls past defined points. You set these thresholds as either percentages of the page height (e.g., 25, 50, 75) or a specific number of pixels. You can track both vertical and horizontal scrolling. When a user scrolls to 90% on a page with thresholds at 25, 50, and 90, the tag will fire three times—once for each threshold crossed. The trigger fires only once per threshold per page load. When it fires, it populates variables like the threshold reached, the units (pixels or percent), and the scroll direction.
When to use it
Use scroll depth tracking to measure reader engagement on long-form content like blog posts or documentation to see how many users reach the end. It's also valuable on landing pages to confirm that users are scrolling down to see key calls-to-action. For accuracy, it's best to enable the trigger after the window has fully loaded so it can correctly calculate the page dimensions.
When not to use it
Do not use the scroll depth trigger on pages with infinite scroll or other dynamically loaded content. The trigger calculates page size on load, so it becomes inaccurate on pages whose dimensions change significantly after loading. Use the 'Element Visibility' trigger for those cases. Also, if a scroll point is visible in the viewport on page load, the trigger will fire immediately, even without a user scroll action.
One canonical example
In Google Tag Manager, you create a new 'Scroll Depth' trigger. You select 'Vertical Scroll Depths' and 'Percentages', then enter '25,50,75,90'. You associate this trigger with a Google Analytics event tag. Now, as a user scrolls down the page, an event is sent to Google Analytics each time they cross the 25%, 50%, 75%, and 90% marks of the page height.
Interview question
Which scenario would cause scroll depth tracking to provide unreliable engagement data?
- a.A user quickly scrolls past multiple configured depth thresholds.
- b.The first scroll depth threshold is already visible when the page initially loads.
- c.The page contains very little content, making all thresholds easy to reach.
- d.The webpage's total height changes after its initial load.Correct
Why? this is the answer
The card states that scroll depth tracking is inaccurate for dynamically loaded content because it calculates page size on load, making it unreliable if dimensions change. Rapid scrolling (option A) does not make the data unreliable; the system is designed to fire for each crossed threshold.
Just read this? Test yourself on what you have been reading.
Read the original → support.google.com
- #analytics
- #tag manager
- #user engagement
- #metrics
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on analytics — each one lists the topics its interview covers.
See open roles