ursboller​I would still like to know - how could that page C be identified as a "re-entry" page.Is there a way to capture these "Re-entry" pages, where within the same visit session the visitor might re-enter the site, possibly on a different tab, from the same or different referring domain?

Thanks Ursboller,Makes sense logically. I actually do see a dimension "Weekday/Weekend" which has 2 values: "weekend" and "weekday". If I apply "weekday" as a segment, it automatically updates any metric for the weekend to 0.I have implemented this segment as a filter for my traffic change alert and...

I have seen this question dated back to 2015, and at the time the answer was "you can't".I am hoping now with the intelligent alerts we can.I tried to use the "Weekday/weekend" dimension, but not quite sure it works. Is there an obvious solution I am missing?Thank you

Let's say I want to serve personalized content to the visitors with a particular browser extension, how can I identify such visitors in AA to create a segment?Thank you

Done: eVar-based container for segmentation

I think we need, for lack of a better description, a next-level container...The same customer might visit under different Adobe IDs. Let's say I capture the customer account in an eVar, so now multiple Adobe IDs have the same value in this eVar.Currently, the largest container available is "visitor"...

Thank you, that's what I thought too, but the classification rule builder does not allow for this kind of logic. Are you saying I'd have to SAINT it?

Thank you ursboller,I have already classified visitor ID and now have a dimension, and I do know how many distinct values I have in this dimension. How can I now segment by this dimension?A simple example - how do I segregate purchasers and non-purchasers not by Adobe Visitor ID but by my Account ID...

I am looking to capture not a specific static set of accounts, but rather dynamically AL the accounts that fall under a certain scenario.

Thanks Andrey, it would seem you were right the first time - there is no solution for my specific request.