The reason for this is OneTrust needs to do various lookups, such as a geo lookup for the user to determine if they reside within various areas of restriction, e.g., the EU for GDPR or California for CCPA.
#Adobe preference manager code
Deploying OneTrust – The ideal approach is to have OneTrust embedded directly into the source code of the page, as high in the as possible. Now that we’ve outlined the scenario, let’s cover the different components.ġ. If we are unsure if a user has consented, we won’t send any tracking through Launch until we are certain of consent. We want to err on the side of caution for tracking users.I am just using “Performance” here as an example. (Please note: as you are working through the classification process, make sure to consult your legal team to determine your organization’s classifications. Of these, all have been classified as Performance. The client uses Adobe Experience Cloud ID Service, Adobe Target, and Adobe Analytics.The client and their legal team have classified each cookie into the appropriate “bucket” of Functional, Performance, or Advertising, and they’ve seen to other legal items like updating the privacy policy.The client and OneTrust have worked through an initial site scan and identified all the cookies being set, as well as what vendors/technologies are setting each cookie.The client either already uses or has chosen to use OneTrust as their consent management platform.Where I have found I need to make additional modifications, I’ll include links to helpful documentation.īefore we get into the technical details, let’s outline the “default” scenario and assumptions: Your scenario may be different, so this is intended as a general guideline. With CCPA going into effect on July 1st, I want to share the common approach I use to apply consent management restrictions to various technologies and tags within Adobe Launch. Since GDPR rolled out in the first half of 2018, there have been multiple technology changes to both the consent management and tag management landscape.
0 kommentar(er)
