I think I 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. How can I segment on that account ID when the largest container available is "visitor", which is based on the Adobe ID?
For example, separating Purchasers and Non-purchasers is not possible by Adobe ID, 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 there's got to be a solution, but I can't seem to figure it out.
you need to further classify the visitorID "the corresponding customer ever bought or not". means you need a subrelation on your customerID "buyer" which allows to filter on the visitors...
I guess you're looking at something like the People Metric. unfortunatelly it is not available by default, maybe coming one day as "global metric"
a) classify your visitor ID's and "approx distict count" see see how many classified values you had (eg. different customers) or to create segments based on certain classification values
b) habe a look if Customer Attributes could help you to answer some questions
I'm not aware of a way to do this either. What we'd need is a 'people' segment bucket, but 'visitor' is the broadest we currently provide.
This would make an excellent idea thread - Vicky if you'd like to create it, I can pass it around internally and collect thoughts and maybe even see if there are discussions currently happening for it. Don't forget to link it here as well!
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.
If you capture customer account number in an eVar, and then the same customer account number visits your site on 3 separate devices, a segment that looks for visitors with that specific customer account number would capture all 3 of my visits & unique visitors on the site. You won't be able to combine these 3 different devices into the same unique visitor, but as long as the customer logged in on all 3 devices, you'll be able to see them with a "visitor" level segment.