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

Coffee Break: Join us on Wednesday, April 5th at 10am PT to chat with Ben Gaines, Director of Product Management for Adobe Analytics. Ben will be online to answer your Analytics and Adobe Summit questions.

Next pages % adds up to more than 100$ in flow diagram

Avatar

Level 1

When I use the flow diagram to see which pages users are going to next (from page name in centre), I would have thought the next pages % breakdown would all add up to 100% but it doesn't. Can somehow explain how to get an accurate picture of where users are going to?

 

tuproducer_0-1674612747507.png

 

1 Reply

Avatar

Community Advisor

By any chance do you have a segment applied to the panel that might be causing an issue...

 

I find it strange that there are entries, but no exits from your page in the middle... I suspect there are a number of users exiting the site from that page, but there is a segment applied that is preventing it from properly showing in the diagram?

 

Jennifer_Dungan_0-1674622393484.png

 

The little green spot at the top left of the page is entries, normally there should be a corresponding "exits"

 

Jennifer_Dungan_1-1674622462166.png

Update: I should add that a segment could be causing a lot of different oddities with how this is displaying... when I try this, my totals line up... so I don't think it's an inherent issue with the flow diagram, but something on top that is resulting is less than desired results....

Avatar

Level 1

Thanks Jennifer! The only segment I am using is a basic geographical one - filtering activity by to a single city. When I remove this however you are right, exits appear and the next pages add up to 100%. Must be something in the config of the segment? Thanks. 

Avatar

Community Advisor

Well that is odd.. you wouldn't think that just limiting the data based on a geographical location would cause that... was your segment Hit, Visit, or Visitor level attribution? Hit should be the safest...