WebSDK and OneTrust Integration for Consistent Consent and User ID Management | Community
Skip to main content
J
JeanBaro
October 1, 2024
Solved

WebSDK and OneTrust Integration for Consistent Consent and User ID Management

  • October 1, 2024
  • 1 reply
  • 1826 views

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:

  1. How can we ensure that the same user is not asked for consent twice when they return to the site? I heard there is a HOUSE HOLD issue with current AEP, but I am not sure about that issue.
  2. How can we keep the user ID in OneTrust consistent with the one collected and managed by AEP’s identity service, allowing seamless consent tracking across sessions?

Any advice or guidance on how to best achieve this would be greatly appreciated!

 

Thanks in advance for your help!

 

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 @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

1 reply

Parvesh_Parmar
Community Advisor
Parvesh_ParmarCommunity AdvisorAccepted solution
Community Advisor
October 1, 2024

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

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

    Loading footer...