Is there a way to read AAM UUID in a webSDK implementation? The 3rd party cookie is not readable using Adobe Launch. Client doesn't have the experience cloud extension enabled along with the webSDK. Any suggestions would be helpful. Thank you.
Solved! Go to Solution.
Views
Replies
Total Likes
Understand that you have included the AAM from your wed SDK implementation. However, Audience Manager saves this UUID as a cookie in the demdex.net which is 3rd party domain. You can inspect your network traffic and check the UUID value from the same (inspect --> Application --> Respective Domain --> UUID).
Then Copy and paste the demdex ID into the UUID field in the Visitor Profile Viewer under AAM UI tool and refresh to see the exact Trait and segment Realizations that has been qualified. Hope, this helps you better and strongly recommend to have the experience cloud id extension as part of your web sdk implementation for the better visitor identification.
Understand that you have included the AAM from your wed SDK implementation. However, Audience Manager saves this UUID as a cookie in the demdex.net which is 3rd party domain. You can inspect your network traffic and check the UUID value from the same (inspect --> Application --> Respective Domain --> UUID).
Then Copy and paste the demdex ID into the UUID field in the Visitor Profile Viewer under AAM UI tool and refresh to see the exact Trait and segment Realizations that has been qualified. Hope, this helps you better and strongly recommend to have the experience cloud id extension as part of your web sdk implementation for the better visitor identification.
Hi @Karthikeyan_Tamilmani - Hope, this will help you. Please let me know if you are looking for anything else.
Thanks Jayakrishna! It's helpful. Our client doesn't use the experience cloud extension. Is there any alternate solutions in this case?
Views
Replies
Total Likes
To clarify part of this statement, we do not recommend ID service (the Experience Cloud ID extension) to be on the page with your web SDK implementation. Web SDK is meant to be implemented on its own without legacy implementation code including ID service. To help with migration scenarios, you can leave prior ID service on the page and web SDK will try to “play nice” if ID service does exist on the page. But we don’t recommend you include ID service with web SDK on the page. In short, it can exist on the same page but we don’t recommend nor encourage that they’re together.
Hi @Karthikeyan_Tamilmani , what is the use case for collecting the UUID?
Views
Replies
Total Likes
@garrettchung @jayakrishnaaparthasarathy Thanks for jumping in here! Me and @Karthikeyan_Tamilmani are working in this together. Let me chime in with some more context:
1. Context: We are doing a WebSDK migration from AppMeasurement. In AppMeasurement, when we setup SSF, there is an option to set a first part cookie (which holds the UUID) and our client was reading this (using Launch) and pass UUID in an eVar.
2. Use Case: My client has some AAM integrations where 3rd party ID syncs are not feasible from websites (due to regulations). So they do an export of the UUID eVar and some behaviors (like Page Views, Events) using AA Data warehouse and then there is a data team that stitches UUID and incoming partner data.
3. Current scenario: Since SSF code is removed, we do not have the 1st party cookie which is holding UUID. The demdex cookie is secured 3rd party. So not readable from Launch. Hence wanted to check out if there are any ways to read it.
@jayakrishnaaparthasarathy - your solution would work for manual copy-paste, but we want to do it from Adobe Launch and set in an XDM variable and then copy to an eVar. If there is a solution, please let us know!
Views
Replies
Total Likes
Views
Like
Replies