Make content changes pre cookie consent | Community
Skip to main content
SamMa10
SamMa10
March 19, 2025
Question

Make content changes pre cookie consent

  • March 19, 2025
  • 1 reply
  • 791 views

With the cookie compliance we're unable to run Target as it drops cookies pre consent. We're now wanting to run A/B testing on the first page of the journey but this causes a 'flicker' as the customer sees the original content, then after accepting Target kicks in and shows the new content.

 

Is there a way for us to make the content changes pre-consent, in a way that cookies are not deployed? If a customer was to opt out of cookies I know we wouldn't be able to track their performance (which is fine) but would help us test there at least.

 

TL;DR - Can I launch Target without cookies for content changes before opt in. 

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
March 19, 2025

Hi @samma10 

To better understand your setup and requirements, I have a few questions 

  • Are you using a specific Consent Management Platform (CMP) or relying on a custom solution?
  • Have you used the pre-hide snippet to mitigate the flicker? 
  • How your Adobe Target has been setup? Are you using at.js or WebSDK approach? 

Could you please provide this input so that it helps to narrow down better approach for your problem.

Thanks

SamMa10
SamMa10Author
March 19, 2025

Hi @gokul_agiwal 

 

  1. We are, we're using Onetrust to manage cookies. We're checking for customers to opt into Performance and then use Launch to push 'adobe.optIn.approveAll()' when this happens.
  2. We have, but the flicker is caused due to the content changes post consent. Meaning the old content is visible behind the cookie consent module and visibly changes once consent obtained.
  3. Using at.js deployed via Launch.

 

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
March 25, 2025

Hi @samma10  Apologies for late reply on this thread. 

 

Are you still facing issues?   in my case, we're using one trust and having the anti-flicker (pre-hide) script added with alignment of user consent. This means, the pre-hide snippet will not get loaded for non consented user.

  • Pre-hiding should be applied when a response from Target and the Edge network is likely to happen.
  • Pre-hiding should be avoided in scenarios where it is not necessary, to optimize user experience and performance metrics.
Terms & ConditionsAccessibility statement

Loading footer...