Thank you, guys. I'll post what ChatGTP says. I feeded your answers as well. I think this could help other people.Short answer:You can’t. Adobe Experience Platform does not support rejecting records or files at ingestion time based on duplicated Identity values. Everything gets ingested into AEP Dat...

When creating the audience, check the merge policy in use, and also, make sure the rules you use when creating the audience are specific enough. if not, you will see other results, and not what you expect.

hi @Vinoth_Govind , I think you're referring to this _id field in a bare bone schema:In my case, I'm using personID as the identity and primary identity. So I guess _id is null or automatically populated by Adobe. In any case, as you mentioned, Adobe doesn't care if you ingest duplicated records, in...

I just created my first journey in Adobe Journey Optimizer. Everything seems ok, I see  3 emails were delivered. I have recieved the email. However, I was wondering how can I validate exactly to which addresses the emails were delivered to?     

HI @MA1985v1  was that custom solution implemented via API? May you elaborate more on that? Ty

I uploaded the same JSON file containing 3 records multiple times, and all records were ingested successfully. I expected AEP to reject duplicated records based on the Identity field, but that didn’t happen.My understanding was that marking a field as an Identity (and Primary Identity) would behave ...

Hi, I have some data that becomes available every day at 6:00 a.m., and other data that is available daily at 2:00 p.m.Is there a way to trigger the audience creation (segmentation) job on demand, or at least configure or change the time at which it runs? 

Hi @Tof_Jossic , quick question—slightly off-topic from the original post.When ingesting data in AEP, is it ingested into the schema or into a dataset?I’m new to AEP, and my understanding is that the schema defines the structure (the skeleton), which is then used to create a dataset where the actual...

I found the issue: When creating an audience, what you should do is click the wheel and select the merge policy. The rule you use to build will use the merge policy to return results and it should be the same as the one you use when creating the profiles. 

I think the issue is here:How do you check if a merge policy is active for segmentation? and the dataset is included and not overriden by another data set that lacks email? I'd appreciate if you can share some screenshots.Thank you.