コミュニティアチーブメントバーを展開する。

Submissions are now open for the 2026 Adobe Experience Maker Awards
解決済み

How to evaluate scrolling percentage

Avatar

Level 1

Hello fellows,

 

I have a question with segment scroll data interpretation. Why the scroll: less than 25% seen is 100%?

Is it because I put two pages into the filter so that the number got wrong?

Thank you for answering.

トピック

トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。

1 受け入れられたソリューション

Avatar

正解者
Community Advisor and Adobe Champion

Hi, keep in mind that the Percent as it's showing in the Workspace is based on the row number divided by the "total", and you are looking at Visitors (which would show the same users in each row of the report).

 

Your Total Visitors in your example are 5260 Visitors, and the "Scroll Less than 25%" is 5258 Visitors (5258 / 5260 rounds to 100%)

 

Your "scroll percentage" is a page based metric.. each page will record individually, but you are paring with a Visitor metric.. so odds are, most visitors hit at least one page where they scrolled less than 25%... 

 

You might be better off looking at Max Scroll Depth by Pages, not by Visitor to get the percentage of pages by scroll depth. 

元の投稿で解決策を見る

2 返信

Avatar

正解者
Community Advisor and Adobe Champion

Hi, keep in mind that the Percent as it's showing in the Workspace is based on the row number divided by the "total", and you are looking at Visitors (which would show the same users in each row of the report).

 

Your Total Visitors in your example are 5260 Visitors, and the "Scroll Less than 25%" is 5258 Visitors (5258 / 5260 rounds to 100%)

 

Your "scroll percentage" is a page based metric.. each page will record individually, but you are paring with a Visitor metric.. so odds are, most visitors hit at least one page where they scrolled less than 25%... 

 

You might be better off looking at Max Scroll Depth by Pages, not by Visitor to get the percentage of pages by scroll depth. 

Avatar

Community Advisor and Adobe Champion

Also, understanding how all your segments are built would help... if the segments are built with the wrong scope you may be reporting on unexpected data sets.