Expand my Community achievements bar.

SOLVED

Adobe Target flicker issues - Target loaded through Google Tag Manager

Avatar

Community Advisor

Hello, 

We're observing the flicker issues on page when Target loaded through GTM after accepting the cookie consent from the user. 

have added the pre hide snippet with modification which check the one trust consent still it's happening. Any input's to avoid the flicker 

Thanks

 

 

 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

In addition to what @alexbishop suggested, one approach that has worked for us is to "add" a module on the page to deliver the personalised message instead of changing the existing content. The approach works for personalisation use-cases as the main objective is to deliver the message. For any experimentation use-cases which require changing existing module, the approach Alex suggested in his second point can be used.

View solution in original post

2 Replies

Avatar

Employee Advisor

I've seen customers typically go one of two ways in this scenario:
i) Reload the whole page on-click of accept consent, which then will allow for the pre-hiding snippet & Target to run as per normal page load process; having said that, Target via GTM has its own challenges due to GTM being loaded async
ii) Hide the content behind the CMP pop up with some sort of dark overlay; Target can then apply page modifications when consent is given, at which point the overlay is removed; important that this sequence happens quickly though, so as to avoid the customer seeing a dark overlay and not being able to interact with the page for an extended period of time

If neither of these are feasible, the other option is to not do experimentation/personalisation on that first page load of cookie consent acceptance because there will always be some level of interruption to the customer experience

Avatar

Correct answer by
Community Advisor

In addition to what @alexbishop suggested, one approach that has worked for us is to "add" a module on the page to deliver the personalised message instead of changing the existing content. The approach works for personalisation use-cases as the main objective is to deliver the message. For any experimentation use-cases which require changing existing module, the approach Alex suggested in his second point can be used.