Is it possible you have a conflicting Adobe Analytics processing rule which is overwriting the value with just the URL path?Can't think of any other way data would be affected between data warehouse and the reporting interface.

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:a custom prop or an eVar which is capturing 'previous page'and the out of the box 'page' dimensionI'm suggesting b...

'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' reporti.e. when you break 'previous page' down by ...

Apologies Urs, didn't mean to steal the credit!

Urs also has the answer to the how to segment on the last hit.  We got into a discussion about this the other day against an idea on the forum.  You can check out his solution here: Make it possible to segment on the hit of the exit page and entry page

Nice idea.  I think you'd also need some kind of auto-refresh option for the Workspace so the data remained current.

some kind of time based expiry of the public sharing of the dashboard would also be very useful

To directly answer your question, you can absolutely set an event without having to use an eVar.However, the reporting in your post should be possible through segmentation/a calculate metric without using an event or an eVar at all if you've got your implementation right.  Whether you are capturing ...

Great!

Hi Jen, great to hear you are still working on the export Just wondered if you are still considering changes to the format of the export to make it easier to work with?(as per your comment in the following thread: https://forums.adobe.com/ideas/10152 )