How a scroll depth trigger works
You set one or more thresholds down the page — a proportion of the total height, or a fixed distance in pixels — and Google Tag Manager watches the browser as the visitor moves. Each time a threshold is crossed, the trigger fires once for that page view, and any tag attached to it sends its event. Horizontal thresholds work the same way for pages that scroll sideways, though those are rare.
Two variables come with it. One reports which threshold was reached, the other whether it was vertical or horizontal, and both can be passed into GA4 so the depth is stored with the event rather than split across separate tags.
Why it matters
Most business pages put the important material a long way down: the price section, the contact form, the answers to the questions people came with. Scroll depth is the only cheap way to find out whether anyone ever gets there. If almost nobody reaches the form, moving the form is a better use of a morning than rewriting the headline.
It reads especially well alongside page length on phones. A page that fits comfortably on a laptop can run to several screens on a handset, which is how most people in Nepal will see it, and the depth figures show that difference plainly.
Where scroll depth triggers go wrong
Proportional thresholds assume the page has a settled height, and many do not. Lazy-loaded images, accordions that expand, comment sections and infinite feeds all change the total as the visitor moves, so the same threshold means different content at different moments. On a short page, the deepest threshold can be crossed before anybody scrolls at all, which makes the page look wildly engaging.
The other trap is volume. Add thresholds every few steps down a long article and each visit sends a stream of events that swamps the ones you care about. And depth is not reading: a visitor flicking to the footer for a phone number passes every marker on the way.
How to use it well
Pick two or three points that mean something on that particular page — the top of the pricing block, the start of the enquiry form — and use pixel distances where the page height is unstable. Name the events after what sits at that depth rather than after the number, so the report is readable a year later.
Then use it as a diagnostic, not a scoreboard. Read it next to scroll depth reports from a heatmap tool if you have one, and pair it with a timer trigger when you want some sense of whether the time spent matches the distance travelled. Keep these events out of the conversion actions that feed automated bidding; they describe behaviour, they do not represent value.