AEP - How to use Login ID or ECID as primary identity? | Community
Skip to main content
A
AbhilashSh
Level 2
April 8, 2024
Solved

AEP - How to use Login ID or ECID as primary identity?

  • April 8, 2024
  • 1 reply
  • 4638 views

I have a query related to one of the use cases in AEP as I am new to AEP.

 

For an ecommerce website that has a login functionality, I have the userID that gets stored in data layer as soon as user logs in. I want to send data to both Adobe Analytics and AEP(as it would be beneficial at a later stage for CJA). 

Can you please let me know what would be the best practice while creating schema and identity? Should I add userID as primary identity or use ECID? If I choose userID as primary identity, what happens with the web interactions that were done prior to login (say product page/ home page view before user logs in where userID wont be available). Will the hits get discarded as there is no primary identity?

 

I was hoping to get an answer from you. Thanks in advance!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Kumar29917170hcyp

Hi @arpan-garg,

 

The mentioned Identity approach will ensure you are covered for below mentioned points:

  • When a full identity graph is updated, Identity Service deletes the oldest identity in the graph before adding the latest identity (FIFO). This is to maintain accuracy and relevance of identity data. This process of deletion follows the below priority:
    • Cookie ID
    • Device ID
    • Cross-Device ID, Email, and Phone

This delete of Identities works only on Primary Identity, so if you mark your know UserID as Primary, it will ensure that the known identity gets de-periodized.

https://experienceleague.adobe.com/en/docs/experience-platform/identity/guardrails#deletion-logic

  • The Privacy Profiles delete functionality works only on Primary Identities, so if your ECID is primary, your Privacy services will not delete the Profiles created from Web data.

Coming to the Shared Device problem you are facing, there are multiple solutions around FPID using seeded ECIDs:-
https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-ids

 

Let us connect to discuss more on the specifics of your problem.

 

Regards,

Kumar Saurabh

1 reply

K
Adobe Employee
Kumar29917170hcypAdobe Employee
Adobe Employee
April 8, 2024

HI @abhilashsh,

 

The recommended approach to stitch Web/App Data and Offline data is mentioned below:

  • Mark the User ID as Primary in the offline schema.
  • For the stitching to function, you can use the User ID from the Web/App as the Primary or Secondary. The data will be stitched across datasets using the Identity Namespace you select. Thus, to stitch the User Id, utilize the same namespace.

Note: For the web/app data, the product recommends marking known Identity as Primary.

If the User Id is available (for logged-in users), then it will be your Primary ID and your ECID will be your Secondary ID; if not, then ECID will be your Primary ID (for non-logged-in journey).
Documentation link:

 https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/overview#using-identitymap

  • The below link explains the process of marking the Known as Primary if available in Data Elements (option available in Data Collection)

https://experienceleague.adobe.com/en/docs/experience-platform/tags/extensions/client/web-sdk/data-element-types#xdm-object

 

Regards,

Kumar Saurabh

    arpan-garg
    Community Advisor
    arpan-gargCommunity Advisor
    Community Advisor
    April 9, 2024

    Hi @kumar29917170hcyp  I didn't tried the above mentioned approach and hence this question - If we use identitymap with CRM id as primary id if it exists and ECID as primary if CRM id doesn't exist, will this mitigate the problem we face while using shared device?

     

    Right now we face an issue when two users use the same device to login their identities and activities get merged. I believe with the above approach as well it should get merged because ECID is secondary.

     

    Thanks,

    Arpan Garg

     

     

      K
      Adobe Employee
      Kumar29917170hcypAdobe EmployeeAccepted solution
      Adobe Employee
      April 9, 2024

      Hi @arpan-garg,

       

      The mentioned Identity approach will ensure you are covered for below mentioned points:

      • When a full identity graph is updated, Identity Service deletes the oldest identity in the graph before adding the latest identity (FIFO). This is to maintain accuracy and relevance of identity data. This process of deletion follows the below priority:
        • Cookie ID
        • Device ID
        • Cross-Device ID, Email, and Phone

      This delete of Identities works only on Primary Identity, so if you mark your know UserID as Primary, it will ensure that the known identity gets de-periodized.

      https://experienceleague.adobe.com/en/docs/experience-platform/identity/guardrails#deletion-logic

      • The Privacy Profiles delete functionality works only on Primary Identities, so if your ECID is primary, your Privacy services will not delete the Profiles created from Web data.

      Coming to the Shared Device problem you are facing, there are multiple solutions around FPID using seeded ECIDs:-
      https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/identity/first-party-device-ids

       

      Let us connect to discuss more on the specifics of your problem.

       

      Regards,

      Kumar Saurabh

      Terms & ConditionsAccessibility statement

      Loading footer...