I'm planning to implement the Target pre-hiding snippet in the <head> of our production site using AEP Web SDK.
However, at this stage, I'm considering placing the pre-hiding snippet without including the Target script or the Launch script.
Is it advisable to place the Target pre-hiding snippet alone without the accompanying Target and Launch scripts? Will this impact or break the current user experience?
If there are potential issues, what would the impact be? If it's safe, how does it not affect the user experience?
CCing Top Contributors for quick response @prads @kandersen @Gokul_Agiwal @alexbishop @Ryan_Roberts_
Thanks for the wonderful support!
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Hi @DhanA2 ,
I don't have any experience with sites having it implemented without Target or Launch. However, the script itself is not Target or Launch dependent, so it will execute regardless of Target being deployed or not.
The purpose of the script is:
As Target is not on the page your users will experience a blank page for 3 seconds, as Target is not in place to remove the style element.
I would advise against deploying the script!
Hi @DhanA2 ,
I don't have any experience with sites having it implemented without Target or Launch. However, the script itself is not Target or Launch dependent, so it will execute regardless of Target being deployed or not.
The purpose of the script is:
As Target is not on the page your users will experience a blank page for 3 seconds, as Target is not in place to remove the style element.
I would advise against deploying the script!
not clear what is the use case here if you not using Target/Launch Script as pre -hiding snippet is specific to address flicker and user experience due to Target/Launch Script implementation.
Without Target/Launch Script, it would work but might hide content and you might need to think of writing the custom script to show content @DhanA2
The pre-hiding snippet is designed to hide content until Adobe Target has loaded. Its primary role is to prevent users from seeing default content before Target has a chance to deliver the appropriate experience.
As Target is not on the page your users will experience a blank page for seconds that you have defined. Users may experience a delay or flicker.
Please let me know if this helps.
Thanks