Hello Adobe Community,
I hope you’re all doing well!
We are currently looking into integrating WebSDK with OneTrust for consent management on our websites and webapps. Our goal is to ensure that if a user returns to the site, they are not prompted for consent more than once. To do this, we want to align the user ID stored in OneTrust with the ID managed and collected by AEP’s identity service.
Here are a couple of key points we’d like to clarify:
Any advice or guidance on how to best achieve this would be greatly appreciated!
Thanks in advance for your help!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hello @JeanBaro ,
If you are using OneTrust for consent management, then OneTrust serves as your primary tool for preference management. OneTrust stores this data in its database with a unique identifier, which can be an email or phone number.
You can utilize the out-of-the-box integration between OneTrust and AEP to transfer consent data from OneTrust to AEP. This integration streamlines consent management and ensures that consent information is updated in AEP datasets in real time. When ingesting data, make sure to use the same identifier across both platforms.
To maintain the same identity, you can send data to both OneTrust and AEP by ingesting the same identifier via the SDK that passes to OneTrust. This will ensure that when data is returned from OneTrust to AEP, it can be linked based on this identifier.
However, if this identifier is cookie-based (like ECID) and not the primary identifier, the household issue will still persist.
I hope this information helps you!
Best regards,
Parvesh
Hello @JeanBaro ,
If you are using OneTrust for consent management, then OneTrust serves as your primary tool for preference management. OneTrust stores this data in its database with a unique identifier, which can be an email or phone number.
You can utilize the out-of-the-box integration between OneTrust and AEP to transfer consent data from OneTrust to AEP. This integration streamlines consent management and ensures that consent information is updated in AEP datasets in real time. When ingesting data, make sure to use the same identifier across both platforms.
To maintain the same identity, you can send data to both OneTrust and AEP by ingesting the same identifier via the SDK that passes to OneTrust. This will ensure that when data is returned from OneTrust to AEP, it can be linked based on this identifier.
However, if this identifier is cookie-based (like ECID) and not the primary identifier, the household issue will still persist.
I hope this information helps you!
Best regards,
Parvesh
This is amazing! Thanks so much!
Just to share some additional info I came across. I found these links that discuss a more "standard" integration between the two platforms. Thought it might be helpful to others as well!
https://www.onetrust.com/blog/onetrust-adobe-automated-consent-orchestration-2/
https://experienceleague.adobe.com/en/docs/platform-learn/implement-web-sdk/consent-management/setup...
https://exchange.adobe.com/apps/ec/100340/onetrust-consent-management-for-cookies
https://www.youtube.com/watch?v=ZJKPfh4Mg2Y&pp=ygUYQWRvYmUgQ29uc2VudCBtYW5hZ2VtZW50
https://www.youtube.com/watch?v=qANKzfuoYlM
https://www.youtube.com/watch?v=e31DQ27-NhQ
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies