Expand my Community achievements bar.

SOLVED

Clarification/Issue on AEP Behaviour for Experience Event Schema Profiles

Avatar

Level 1

Hi Team,
I'm currently working on a use case involving the creation of a schema using XDM Experience Event and the setup of a dataset with profile integration. One observation that has surfaced is that when data is ingested multiple times for the same record, the event tab in the profile seems to capture only the initial record, disregarding subsequent ones. Could you please clarify if this is the expected behaviour when using an Experience Event Schema-based profile? 


_aepxxxx.id
 is the primary identity below.

 

First Data Ingestion:

[ { "_aepxxxx": { "value": 5, "id": "5697826" }, "timestamp": "2023-09-12T13:35:30.000Z", "_id": "5697826" } ]

 

Next Data Ingestion:
[ { "_aepxxxx": { "value": 6, "id": "5697826" }, "timestamp": "2023-09-12T13:35:30.000Z", "_id": "5697826" } ]

 

Existing Outcome: The event tab is only showing the first event with a value of 5.


Desired Outcome: The event tab only shows both events and the latest value should be set.

1 Accepted Solution

Avatar

Correct answer by
Level 3

Hi,

This is because of the _id field within the Experience Event Class that serves as a distinctive identifier for any event.

In cases where duplicate events are identified, events are discarded if an event with the identical _id already exists in the Profile Store.

 

However, you will have all the records in the Datalake.

 

 

View solution in original post

4 Replies

Avatar

Employee

Hi @Anubhav_7897 

 

This is expected as you are using the same _id value for all records. So platform considers them as same event and blocked subsequent records to avoid duplication. If you ingest with a different _id value you'll be able to see them in event tab.

 

Regards,

Arijit Ghosh

Avatar

Correct answer by
Level 3

Hi,

This is because of the _id field within the Experience Event Class that serves as a distinctive identifier for any event.

In cases where duplicate events are identified, events are discarded if an event with the identical _id already exists in the Profile Store.

 

However, you will have all the records in the Datalake.