Using Adobe Experience Cloud ID in Cookie Consent
If you use Adobe Experience Cloud ID Service to assist with the identification and cookie selection process of your website, you can integrate its functionality with the Cookie Consent module.
By using our OneTrust Universal Consent & Preference Management for Cookies extension, you can can also integrate directly with the Adobe Experience Cloud ID Service. Cookie categories can be configured to match with the Adobe categories being used so that when your users opt into a Cookie Category, they are also opting into an Adobe category.
OneTrust Universal Consent & Preference Management for Cookies
Adobe Documentation
To Use the Cookie Consent Extension
The Adobe ECID extension must be implemented with the Opt-In object enabled in your Adobe Launch account in order to leverage this integration. Do not enable Enable EU compliance for Adobe Analytics or GDPR Opt-In for Adobe Target.
For more information, see Adobe Experience Cloud Help.
To Manually Add the Cookie Consent Script
If you would prefer to not use the OneTrust provided extension, you can interact with Adobe Experience Cloud ID via a manual implementation. Although we recommend using the extension, use the script below if a manual method is needed. This code needs to be included in the OptanonWrapper.
- Add the OneTrust script in the
<head>tag of the HTML with the below script in theOptanonWrappercall back function and ensure the Adobe Launch script is loading asynchronously. - Replace the comma delimited value (,C0002,) with the comma delimited value for the group of performance cookies.
- Replace the comma delimited value (,C0003,) with the comma delimited value for the group of functional cookies.
- Replace the comma delimited value (,C0004,) with the comma delimited value for the group of targeting cookies.
- Include any Adobe categories that are not active.
- 5. Add a direct call for any custom rules to fire based on the ‘OnetrustActiveGroups’ dataLayer, if you want to handle the rules from the front end instead of the Launch container.
To test the integration, enter the following into your console and refresh the page:
_’satellite.setDebug(true)’
This will display a log of what is loading from the Launch library and the consent status. To see the consent status for all categories of Adobe enter, adobe.optIn.permissions.