Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

Interpreting page scroll depth data

Avatar

Level 1

Hello, Could some one help me understanding page scroll depth data that i see. I understand that it is collected through a plug-in but i am not sure how to read the data, i see. what does 100/100 vs 100/58 vs 100/150 means for example? Thank you for your help in advance.

advancedanalytics_0-1605629313081.png

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@advancedanalytics If you're using the s.getPercentPageViewed() plugin, the two values likely reflect the maximum percent of the page viewed and the percent of the page that was visible when the page initially loaded. For example:

  • 100|50 - 100% of the page was viewed, while 50% of the page was visible when the page loaded. (The visitor had to scroll to see the remaining 50%.)
  • 58|58 - 58% of the page was initially visible, and the visitor never scrolled to see anything lower, so the maximum percent of the page viewed was also 58%.

View solution in original post

4 Replies

Avatar

Correct answer by
Community Advisor

@advancedanalytics If you're using the s.getPercentPageViewed() plugin, the two values likely reflect the maximum percent of the page viewed and the percent of the page that was visible when the page initially loaded. For example:

  • 100|50 - 100% of the page was viewed, while 50% of the page was visible when the page loaded. (The visitor had to scroll to see the remaining 50%.)
  • 58|58 - 58% of the page was initially visible, and the visitor never scrolled to see anything lower, so the maximum percent of the page viewed was also 58%.

Avatar

Level 1
Thank you Brian. That helps. But, i also see numbers as 100/188 and 100/145, etc. So, i assume 100% of the page was viewed but how's the page length more than 100?

Avatar

Community Advisor
Without seeing the implementation or knowing for sure exactly how it has been configured, it's hard to say what those represent. It could be an oddity related to a single page app, an unexpected JavaScript or cookie/storage issue, or a number of other issues. I'm assuming, though, these values are the exception? If I were you, I'd segment down to the exact page(s) where you're seeing these values and do some live QA to see what's going on.

Avatar

Level 1
Thank you so much. I would do some QA to see what might be going on behind that ratio. Really appreciate your time in answering my questions.