Hello all,
I am struggling to find a real next page flow report from Adobe Analytics. I work a lot with the previous page dimension and I just want the same format of dimension but for next page.
The flow in Workspace for some reason I can't understand it is only accounting for less than 0,5% of the total visits of a filtered segment. Using Page URL, Journey Pathing or Page dimensions just goes from 500K visits to 2K.
See here how many visits we have in a segment for one year:
This is what I see in the flow diagram using Page URL (v25):
Same happens when using "Page" or "Journey Path".
Could anyone share what is your process of analyzing next pages flow of your sites? Furthermore, a table would be much more helpful than a diagram for analysis purposes.
Thank you,
Solved! Go to Solution.
Yes, I think you've understood what I'm getting at.
At the beginning of your original post you said you "work a lot with the previous page dimension"
So I assume you've got access to both:
I'm suggesting breaking down 'previous page' by 'page', which in affect becomes a 'next page' report
(If you don't have a prop or eVar with 'previous page' captured into it then you should get whoever looks after your implementation to use the Get Previous Value JavaScript plugin to capture the previous page name value into a prop or eVar.)
'Next page' in a table format:
It sounds like you are capturing the 'previous page' into a prop or an eVar and using this as breakdown on 'page' to see what the previous page was.
Conceptually you can just reverse these dimensions to get a 'next page' report
i.e. when you break 'previous page' down by 'page', previous page = page, and 'page' = 'next page'
Does that make sense?
I see, you are suggesting to use my list of URLs as Previous Pages so the "Pages" are the next ones right?
It's a good point!!
Views
Replies
Total Likes
Yes, I think you've understood what I'm getting at.
At the beginning of your original post you said you "work a lot with the previous page dimension"
So I assume you've got access to both:
I'm suggesting breaking down 'previous page' by 'page', which in affect becomes a 'next page' report
(If you don't have a prop or eVar with 'previous page' captured into it then you should get whoever looks after your implementation to use the Get Previous Value JavaScript plugin to capture the previous page name value into a prop or eVar.)