Adobe Experience Platform

pradeep_joshi20 · 6/26/25

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 · 6/26/25

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.

pradeep_joshi20 · 7/14/25

This look more of work around. Already have done those. But looking for some solutions rather then checking from navigator.globalPrivacyControl, any way from onetrust & exiting rules can work as expected.

kautuk_sahni · 7/1/25

@pradeep_joshi20 Just checking in — were you able to resolve your issue?
We’d love to hear how things worked out. If the suggestions above helped, marking a response as correct can guide others with similar questions. And if you found another solution, feel free to share it — your insights could really benefit the community. Thanks again for being part of the conversation!