How to retrieve UUID in Adobe WebSDK Implementation | Community
Skip to main content
S
Santhosh_M
October 23, 2024
Solved

How to retrieve UUID in Adobe WebSDK Implementation

  • October 23, 2024
  • 1 reply
  • 840 views

We have migrated from client side adobe solutions (App Measurement, Experience Cloud ID ) to Adobe WebSDK setup. In old appmeasurment extension, we have enabled the option to store the AAM cookie to a first party cookie with UUID returned from AAM.

 

Since the VisitorAPI.js service (Experience Cloud ID extension) is disabled in launch now, we do not have the demdex third party cookie or the first party UUID cookie present in current WebSDK pages.

 

We need help to know, how to retrieve the UUID first party cookie with WebSDK setup, so we can pass it to an adobe analytics eVar.


Appreciate if anyone can assist.

 

Thanks

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 Parvesh_Parmar

Hello @santhosh_m , 

 

With the move to Adobe WebSDK, you’ll primarily use ECID (Experience Cloud ID) instead of the previously stored UUID in the VisitorAPI.js setup. WebSDK uses ECID as the default unique identifier across Adobe products, providing consistent cross-solution tracking.

 

I saw the  Challenges with Historical Data during this transformation. If your previous data collected with UUID and new with ECID. WebSDK does not automatically sync historical UUID data with ECID. Therefore, existing segments or data relying on the UUID will not directly align with new ECID-based data.

If possible, pass both the UUID (if still available) and the new ECID during a transition period. This allows time to collect both identifiers, making it easier to map or link historical data to new sessions.

 

If historical continuity is critical, consider mapping UUIDs to ECIDs in your data warehouse, allowing you to link past data to the new identifiers. This can be complex and may require support from Adobe Consulting Services to develop a custom solution.

 

 

Kr,

Parvesh

1 reply

kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
October 28, 2024

@parvesh_parmar @arpan-garg would you please take a moment to review this question? We would be grateful for any wisdom you could share on this question.

Kautuk Sahni
Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity AdvisorAccepted solution
Community Advisor
October 29, 2024

Hello @santhosh_m , 

 

With the move to Adobe WebSDK, you’ll primarily use ECID (Experience Cloud ID) instead of the previously stored UUID in the VisitorAPI.js setup. WebSDK uses ECID as the default unique identifier across Adobe products, providing consistent cross-solution tracking.

 

I saw the  Challenges with Historical Data during this transformation. If your previous data collected with UUID and new with ECID. WebSDK does not automatically sync historical UUID data with ECID. Therefore, existing segments or data relying on the UUID will not directly align with new ECID-based data.

If possible, pass both the UUID (if still available) and the new ECID during a transition period. This allows time to collect both identifiers, making it easier to map or link historical data to new sessions.

 

If historical continuity is critical, consider mapping UUIDs to ECIDs in your data warehouse, allowing you to link past data to the new identifiers. This can be complex and may require support from Adobe Consulting Services to develop a custom solution.

 

 

Kr,

Parvesh

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

    Loading footer...