Redirect Offer in Adobe Target works only after cookie consent & page refresh — how do other enterprises handle this?

[GauravDu1]

Hi everyone,

We’re running a geo-based redirect activity in Adobe Target (using the “Redirect to URL” offer) on our corporate site (EY.com).

Here’s what we’ve observed:

• On first visit, before cookie consent is accepted (OneTrust banner visible), Adobe Target is blocked from loading — so the redirect doesn’t fire.

• Once a user accepts cookies, the page doesn’t auto-reload, so Target still doesn’t initialize.

• The redirect works only after a manual page refresh (when Target finally loads).
  
  

  Questions:

  1. Is this expected behavior when Adobe Target is gated behind OneTrust consent?

  2. How do other enterprises handle geo-based redirects for first-time visitors — before Target can load?

[bjoern__koth · Accepted solution]

Hi @GauravDu1 

are you deploying Target the old way with the Target / at.js extension in combination with the Adobe Visitor ID Service or are you deploying it using Web SDK?

In general, you are able to listen to OneTrust consent changes by registering a callback function you can use as trigger to for instance trigger a direct call that your other rules (such as Target) can listen to.

https://developer.onetrust.com/onetrust/docs/javascript-api -> search for "onconsentchanged"

OneTrust.OnConsentChanged(function() {});

In there, do something like _satellite.track("consent_changed") and listen to this as direct call event to re-/trigger your target rule. You may want to add a "max frequency" condition to that rule to make sure it does not trigger more than once.

If you're using the Visitor ID Service, you may also leverage the Adobe.optIn API to queue and release your Adobe tools.

But non-Adobe tools may need this direct call approach to make them fire upon given consent.

[GauravDu1]

Thanks 🙂 this one trust acceptance worked.