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", which is based on the Adobe ID. It'd be great if we could segment on an eVar that groups multiple Adobe IDs.
For example, separating Purchasers and Non-purchasers by Adobe ID is not meaningful, as the same account might do a part of the journey under one Adobe ID and another part under another.
I am fairly certain it's a common situation, so maybe this deserves consideration?
