Solved
person and event container
Hi team,
The filter is Created based on the fan include and event Container how does the values differs if we use it like this
which one would give the best values to consider on creating a filter
Hi @dineshpr ,
It looks like your organization has renamed the "person" container to "fan." So when you see others talking about "person", that's the same as "fan" for you.
If you have a fan level container, it's going to look at all of the data for each person visiting your site. If the conditions are met, it will return all the information for that person.
At an event level, an event is a single hit/action. So that means that all the conditions need to happen in the same hit. I see you have two conditions, a journey version and an audience segment. Putting these in an event container means they both have to happen in the same event.
If you were to put the two conditions in a fan level segment without the event container, it means that the person would have to see that journey version at some point, and then also see the audience segment, but not necessarily at the same time. At the fan level, both need to exist at some point in that customers journey, but not necessarily together.
The event container means that they both have to happen together in the same event. Then putting the event container into a fan segment means that it will return all of the information for fans that have at least one hit/event that matches both of those conditions.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.