Profile stitching using custom profiles and Adobe Analytics data in AEP | Community
Skip to main content
S
sharmilap
Level 2
November 20, 2023
Solved

Profile stitching using custom profiles and Adobe Analytics data in AEP

  • November 20, 2023
  • 2 replies
  • 2240 views

Hi,

 

We have ingested contact profiles with email address as the primary identifier. We also have Adobe Analytics data streaming into our AEP environment. For some of the profiles that have been registered using their email address on our website, we notice that the Adobe Analytics data is not stitched together with the email address from the backend. This makes the email address and Adobe analytics visitor data as two different profiles in AEP.

 

Can someone explain why the event data from Adobe Analytics did not get stitched to the corresponding email address even after the user registration occurred on our website?

 

Thanks

Sharmila

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 abhinavbalooni

Hi @sharmilap 

You would need some common identifier in AA data as well to stitch the data. In your current setup, there is no way for AEP to know it is the same user. For your AA data, AEP knows one id - ECID and for your contact profiles, AEP knows the email address. There needs to be an 'authenticated' identifier in AA, possibly a backend unique id which would also be part of fhe contact profile from backend. Unless that happens, AEP has no way of knowing it is the same user and would continue creating two separate profiles.

 

Hope the above helps.

 

Regards,

Abhinav

2 replies

P
Prateek-Garg
Level 2
November 21, 2023

Hi Sharmila,

 

Does email from contact profiles and email from Adobe Analytics are categorized under same namespace in Identity? Note: For identities from different datasets to get stitched together they need to marked as Identities and under same namespace. In your case the namespace need to be same for emails for datasets having contact profiles and Adobe Analytics.

 

Thanks.

Prateek

    abhinavbalooni
    Community Advisor
    abhinavbalooniCommunity Advisor
    Community Advisor
    November 21, 2023

    Hi @sharmilap 

     

    There are two things you would check here:

    1. In the case of Adobe Analytics data, I am assuming it is coming through Web SDK, have you marked email as an identity field ?

    2. As @prateek-garg mentioned, if you have marked the email field as an identity, then you need to ensure that the namespace you are using for this field is the same as the one you are using in the contact dataset for email field.

     

    My hunch is, it might be the issue that the email field in AA dataset is not marked as an identity.

     

    Regards,

    Abhinav

      S
      sharmilapAuthor
      Level 2
      November 21, 2023

      Thanks @prateek-garg & @abhinavbalooni  for your responses.

       

      We don't use web SDK for AA data streaming yet.

       

      The schema for AA data does not have email address and it is not one the values being sent. The identity field on this schema is currently one of the prop<n> fields which contains the Adobe MC Id, so definitely not the same identity namespace. We have internal identifiers to indicate the user in AA data and not the email address itself(for security reasons, maybe?). 

      abhinavbalooni
      Community Advisor
      abhinavbalooniCommunity AdvisorAccepted solution
      Community Advisor
      November 21, 2023

      Hi @sharmilap 

      You would need some common identifier in AA data as well to stitch the data. In your current setup, there is no way for AEP to know it is the same user. For your AA data, AEP knows one id - ECID and for your contact profiles, AEP knows the email address. There needs to be an 'authenticated' identifier in AA, possibly a backend unique id which would also be part of fhe contact profile from backend. Unless that happens, AEP has no way of knowing it is the same user and would continue creating two separate profiles.

       

      Hope the above helps.

       

      Regards,

      Abhinav

        Terms & ConditionsAccessibility statement

        Loading footer...