Hi,
Why the second answer is correct? It is because the id of the event is not unique?
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @Michael_Soprano - In the AEP experience, an event's _id serves as its unique identifier. It is not possible to store multiple events with the same _id in the profile storage. If an event is ingested with an _id that already exists, it will not be added to the profile store. Consequently, the number of events associated with a profile will remain one. It's important to note that events sharing the same _id will still be ingested into the data lake. You can view all events with the same _id by running a query on the dataset. However, only the first event bearing that _id will be stored in the profile store.
Thanks,
Arpan
Yes. Only 1 record will be available in profile with a given _id. Second record won’t be processed to profile.
—ssj
Views
Replies
Total Likes
Hi @Michael_Soprano - In the AEP experience, an event's _id serves as its unique identifier. It is not possible to store multiple events with the same _id in the profile storage. If an event is ingested with an _id that already exists, it will not be added to the profile store. Consequently, the number of events associated with a profile will remain one. It's important to note that events sharing the same _id will still be ingested into the data lake. You can view all events with the same _id by running a query on the dataset. However, only the first event bearing that _id will be stored in the profile store.
Thanks,
Arpan
Views
Likes
Replies