SOLVED
Anti-flicker
1 Accepted Solution
Correct answer by
You only need the pre-hiding snippet if Target is loaded asynchronously. It is asynchronous via the GTM.
However, here you still have to consider which rules are created in GTM to load Target. If there are rules or conditions that control whether the target should be loaded at all (e.g. Consent etc.) - this is important to know.
An elegant method is - to write a kind of wrapper code around the pre-hiding snippet - which checks the same condition if Target should be loaded at all. Classic example is if Consent is present or not. So in case Target is not loaded intitially - the pre-hiding snippet will not be executed.
If Target should be loaded - then Target itself removes the pre-hiding via at.js.
I agree with @Gaureshk_Kodag. I wouldn't change anything in at.js itself. That doesn't make much sense because you don't want to change the code every time you update the at.js because there is a new version. Besides, the logic in the at.js is correct and works even if the interaction with the pre-hidings snippet is correct. It is important to mention that the pre-hidings snippet is executed as early as possible in the head.
Correct answer by
You only need the pre-hiding snippet if Target is loaded asynchronously. It is asynchronous via the GTM.
However, here you still have to consider which rules are created in GTM to load Target. If there are rules or conditions that control whether the target should be loaded at all (e.g. Consent etc.) - this is important to know.
An elegant method is - to write a kind of wrapper code around the pre-hiding snippet - which checks the same condition if Target should be loaded at all. Classic example is if Consent is present or not. So in case Target is not loaded intitially - the pre-hiding snippet will not be executed.
If Target should be loaded - then Target itself removes the pre-hiding via at.js.
Yes the at.js is powerful in itself and can also cover e.g. a SPA accordingly and also holds an own pre-hiding in itself which can also be influenced via e.g. the targetGlobalSettings() function. But this should not bother you.
But do you have flickering problems in general?
