AA connector sending identity map with ECID as primary identity while schema already has a primary identity

[pk11111]

Hello,

We are using the AA source connector to import data from AA into AEP and Profile. One of the eVars is our CRM ID and it is labeled it as a primary identity in the Adobe Analytics experienceEvent template schema. However, streaming data coming from the AA connector also sends an identity map with the ECID labeled as primary identity. 

What happens in this case? Is the Profile built using the ECID or the CRM ID as a primary ID? We would like the schema to use the CRM ID as a primary ID.

Thanks.

[abhinavbalooni]

Hey @pk11111 

I am assuming you used the default schema while using AA source connector?

In that case, even if you are passing the crm id in an eVar, AEP has no way of knowing that. If ECID is the primary identity, profile will be created on the ecid and since your analytics evar capturing crm id isn't mapped as an identity, it would not stitch as an identity and only ECID would show up as an identity.

To the other query, primary identity field needs to be there on every valid row. That means, your crm id would need to be on every hit that you want to ingest in AEP. Is that the case ? Reason why ECID is set as a primary identity by default for an AA source connector is cause it is an anonymous cookie id and knowing the user with a first party id from the first interaction onwards is not usually possible.

Cheers,

Abhinav

[pk11111 · Accepted solution]

Hi @abhinavbalooni ,

Thanks so much for your reply. Indeed, we are using the Adobe Analytics experienceEvent template in the schema. The CRM ID is labeled as a primary identity. When looking at Profiles, I can see both the ECID and CRM ID are correctly being displayed as identities.

That being said, I believe the ECID overrides the CRM ID because in Query Service, there are many rows where the CRM ID is empty despite it being labeled as a primary ID.