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
