We have implemented Target using Asynchronous Launch.
As per the link : https://docs.adobelaunch.com/extension-reference/adobe-extensions/adobe-target-extension , if we use Asynchronous way to push Target through the Launch, we need to add Pre-hiding snippet. We have done the same, but after the addition of Pre-hiding snippet our page goes blank for few seconds and then loads.
Do we have any solution to fix this? Kindly advice
By default the snippet pre-hides the whole HTML BODY.If you only want to pre-hide certain HTML elements and not the entire page.
You can achieve that by customizing the style parameter. It can be replaced with something that pre-hides only particular regions of the page.
You can refer this documentation to see this in detail:
Let us know, If you have any follow-up queries or concerns.
The page is expected to go blank for a few microseconds with at.js. This was included to avoid any flicker on the page. This might take upto few seconds on slow network connections though.
In your Launch Target rule do you have the body hiding enabled? If not, then it wouldn't reveal page until the pre-hiding timeout happens (3000 ms).
Dear TanviAgarwal ,
Thanks for the revert. But page blank for few seconds is also not a good experience right?
Our IT Team is not okay with the blank screen for few seconds. Do we have any other option to arrest this?
Dear ryanr8 ,
I have enabled the same. If it is enabled, don't we need Pre-hiding snippet? Kindly advice.
Yes, the body hiding enabled requires the pre-hiding snippet be implemented outside of Launch and before the Launch inclusion script tag when Launch is loading async.
If you've implemented correctly you should not see the page go blank for a few seconds. If you want to direct message me screen shots of your setup in Launch and send a url to check I'd be happy to review it for you.
just found this thread since we're looking into the same issue, async at.js loading (through Tealium tag manager).
Correct me if I'm wrong but the pre-hide snippet will cause anyone with an ad blocker to have a white screen for a few seconds, right? Is there any newer way around it (using 2.3.0), and is the 3s timeout value still best practice?