Can we set up 2 eVar fields for same attibute in Adobe Analytics data Schema in CDP as Identity? | Adobe Higher Education
Skip to main content
M
mansibedi
Level 3
June 21, 2023
Répondu

Can we set up 2 eVar fields for same attibute in Adobe Analytics data Schema in CDP as Identity?

Hi team,

 

We have a Adobe Analytics connection in CDP for streaming data. One of the attribute we are passing through AA into CDP is Hashed Email, set up as say, eVar79. We are tagging another Hashed Email attribute of different encryption in AA, which will pass to CDP as say, new eVar80. Currently in CDP, existing Hashed Email tagging (evar79) is set up as Secondary Identity (with Adobe provided Hashed Email Identity namespace). Can we set up both the Hashed Email evar79 and evar80 as Secondary Identity to bring in existing Hashed encryption and new Hashed encryption as Identity and part of the same Namespace? 

OR will that be an issue and we need to map Hashed Email as Identity for only one of the Dimensions? 

 

 

Ce sujet a été fermé aux réponses.
Meilleure réponse par birthariya

Yes, it will just link the 2 emails, which I don't think will be an issue as they are the same email but just different hashing.

1 commentaire

B
birthariya
Level 3
June 21, 2023

It is possible to mark 2 attributes/fields as the identity that too under the same namespace.

In the approach that you mentioned, the email IDs are of different hashing, which can cause problems in certain downstream destinations (specifically people based)

M
mansibediAuteur
Level 3
June 26, 2023

Thanks @birthariya,

Yes the email IDs are of different hashing but old one will be decommissioned soon. It is only temporary to use till all sources are synced with the new hashing encryption. 

Till then, do you suggest it is feasible to mark 2 hashing fields as identity with same namespace? 

 

 

B
birthariyaRéponse
Level 3
June 28, 2023

Yes, it will just link the 2 emails, which I don't think will be an issue as they are the same email but just different hashing.

    Conditions d'utilisationAccessibility statement

    Loading footer...