Onetrust & Adobe Launch Integration, delay in OptanonActiveGroups to set

Question

I have completed the integration of Adobe OneTrust and Adobe Launch by following the instructions on this page: OneTrust Integration Guide.

I have added conditions in each rule regarding targeting and performance based on the OptanonActiveGroups provided, with everything set to opt-in by default.

However, I am encountering an issue with the GPC signal. When it is activated, it should block all cookies, but there is a delay in setting the OptanonActiveGroups, which causes some pixels to still fire.

Need to help to tackle this.

KumarRishii · Answer

The issue arises because the OptanonActiveGroups variable may not be set immediately, causing pixels to fire before consent is determined when the GPC signal is active. To resolve this, you can try below steps:

Ensure OptanonActiveGroups is fully set before firing tags using conditional checks.

Use Adobe Launch's "Data Element Changed" trigger to delay rule execution until consent is established.

Implement a global check for the GPC signal (navigator.globalPrivacyControl) to block all tracking if active.

Leverage OneTrust's event APIs to reinitialize tags after consent groups are updated.

Then Use developer tools to log and verify the timing of OptanonActiveGroups and pixel firing.

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded