Desired outcome
We have a metric that indicates what percentage of page visitors either reads or scans content on a given page, and be able to compare engagement across pages. We would interpret a 50% scroll depth event at evidence that a user is doing this.
GA pre-set unique scroll event requires a user to scroll at least 90% through the vertical depth of a page to be counted. Even if a learning resources visitor only reads part of a page, it would be helpful to distinguish a partial read or scan from a simple page load without reviewing the full page. That's why a lower, 50% scroll-depth event is needed as well.
Expected behaviour to be measured
When a user scrolls more that 50% through the vertical depth of a page, an event is triggered, and the count increases by 1. The metric should be visible on the pages and screens engagement report, filtered by page title and screen name.
Desired outcome We have a metric that indicates what percentage of page visitors either reads or scans content on a given page, and be able to compare engagement across pages. We would interpret a 50% scroll depth event at evidence that a user is doing this.
GA pre-set unique scroll event requires a user to scroll at least 90% through the vertical depth of a page to be counted. Even if a learning resources visitor only reads part of a page, it would be helpful to distinguish a partial read or scan from a simple page load without reviewing the full page. That's why a lower, 50% scroll-depth event is needed as well.
Expected behaviour to be measured When a user scrolls more that 50% through the vertical depth of a page, an event is triggered, and the count increases by 1. The metric should be visible on the pages and screens engagement report, filtered by page title and screen name.