Expand my Community achievements bar.

Adobe Experience Platform (AEP) & Apps User Groups are live to Network, learn, and share in your regional locations.
SOLVED

Mobile app is available only for logged in users

Avatar

Level 10

The best way to track identities is Identity Map?

Should I use email as a primary identity?

https://developer.adobe.com/client-sdks/edge/identity-for-edge-network/api-reference/#identitymap

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

Depends on whether you consider Email to be an identity namespace unique to one specific profile.

If so, flag it as primary.

 

If not, ECID will/should implicitly be used as a primary identity in your request.

Cheers from Switzerland!


View solution in original post

2 Replies

Avatar

Correct answer by
Community Advisor and Adobe Champion

Depends on whether you consider Email to be an identity namespace unique to one specific profile.

If so, flag it as primary.

 

If not, ECID will/should implicitly be used as a primary identity in your request.

Cheers from Switzerland!


Avatar

Level 4

identityMap is the best way to track identities in the Adobe Experience Platform Web/Mobile SDK.

 

In practical implementation, for AEP SDK Experience Event data, ECID should be used to be used a Primary Identity or not use a primary identity at all and just use Email as a Secondary Identity. Using Email as Primary Identity is appropriate if you can ensure that every event from Adobe Experience Platform Mobile SDK will have a valid Email value (this is difficult even for login based apps as Splash screen and initial login screens will not have Emails captured yet.

 

While passing data to AEP, Primary identity can not hold any null value. if Email is used as Primary Identity all those events will error out and will not be ingested in AEP. ECID is automatically generated and included by the AEP Web and Mobile SDKs, ensuring every event carries a valid, non-null primary identity.

 

Email can be a secondary Identity for profile enrichment purpose. Although unverified Email can also create Profile stitching and quality issues.