Expand my Community achievements bar.

Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.

Event web dataset - Identity Map vs custom ECID field as primary identitifier

Avatar

Level 10

Is it better to use some custom field with ECID as a primary identity or to used Identity Map?
What is the advantage of Identity Map?

4 Replies

Avatar

Community Advisor

Hello @Michael_Soprano ,


As I understand, it is recommended to use ECID as a secondary identity and not combine it with the primary identity in the event schema.

Here's how you can set it up:

• In the profile schema, create the CRM ID as the primary key, assigning it a namespace (e.g., CRM_ID). Make sure to enable it for profile.
• In the event table, create both ECID and CRM ID as secondary keys, assigning the correct namespace. For the CRM ID, use the same namespace as the profile schema.

There are two possible scenarios to consider:

1. When you receive event data with ECID but without CRM ID, a profile will be created based on the ECID, and an identity map will be generated.
2. When a customer logs in after some time and sends both ECID and CRM ID, all previous events without CRM ID will be linked to the CRM profile and ECID records will be merge with it.

For more information on this topic, you can refer to the Adobe Experience Platform Identity Service documentation: https://experienceleague.adobe.com/en/docs/experience-platform/identity/home#

 

Best regards,
Parvesh

 

Parvesh Parmar – Adobe Community Advisor
https://www.linkedin.com/in/parvesh-parmar/

Avatar

Employee Advisor

With Web SDK, it's best to pass all identities via the identityMap. All of the support in the Web SDK Tags extension is designed to support this approach. You wouldn't be able to set the ECID on the first hit of a new visitor in a custom field.

Avatar

Level 3

if you consider independent ECID attribute as identity, you will end up marking this  attribute as primary identity, because there will always be anonymous browsing events which will only have ECID as identity. which also means that when it is login browsing still ECID will be primary identity.

 

As a good practice, it is recommended to have login id as primary identity if its available and consider ECID as secondary identity. when it is anonymous browsing then consider ECID as primary identity. This flexibility will be available only when you use identityMap and marking identityMap as identity.

Avatar

Community Advisor

One of my Adobe consultants once told me as rule of thumb

  • for profile schema datasets, use dedicated fields 
  • for event datasets, use the identityMap

But as @dwright @already wrote, if you're using the WebSDK, you won't need to explicitly send it anyway since it gets implicitly added to your requests.

 

If not present, the Edge network will treat your ECID as primary identity, so in WebSDK calls, there is no need to define a separate identityMap anyway.

 

If you need to have it in your data e.g., to be used in CJA or so, I would rather use datastream mapping to map it to your target field.

Cheers from Switzerland!