Hi @JeanBaro_ There is a unique "Profile ID" pertaining to each profile in AEP. When searching for a specific ID within the tool, once you navigate to the Identity Graph, you can capture this ID in the URL. As for being able to use it downstream, I'm not entirely sure to be honest. 

Hi @akwankl From my understanding, this is a known issue within the identity stitching of AEP. I have heard there are active investigations of the hope to correct this, but as of now, it cannot be avoided. David

Hi @kendallhall Profiles are composed of attributes, identities, audience memberships and behaviors. The profile ID that I believe you are mentioning, is the overall ID that is assigned to the specific profile. You can only map profile attributes to a destination, not the profile itself.Thanks,David

Hi @Flower22 Attached is the link for AEP API'shttps://developer.adobe.com/experience-platform-apis/ Hope this helps!David

Hi @HariKo1 In monitoring tab in AEP, you will see "batch end-to-end" and "streaming end-to-end". As long as you have streaming dataflows created, you will see data there. Thanks,David

Thanks for the feedback! @brekrut 

You shouldn't have to rebuild the segments, if they are still using the same data points that are being re-ingested into the new dataset. Are you still seeing any issues?

Hi @brekrut  I was also able to access and complete the form

I second @_Manoj_Kumar_ ! They are merge policy specific, I had encountered this same query in the past.

@Indra ok I understand now. It should be erroring out due to same field group id, name, etc. One thing I notice is that you are using an OOTB field group, to which i’m not entirely sure if that could be of any reason why. It may be worth logging a ticket with Adobe support referencing your sandbox a...