Adobe Target Pre hiding snippet impacts page performance | Community
Skip to main content
S
SrikanthPo3
Level 5
June 30, 2026
Question

Adobe Target Pre hiding snippet impacts page performance

  • June 30, 2026
  • 1 reply
  • 90 views

Hi Team,

We are using Adobe Target legacy pre-hiding JavaScript snippet with 1500ms timeout to avoid flickering but page performance tools flagged this as a potential cause for low scores in desktop and mobile. Adobe support team suggested to use Flicker Manager V2(Beta) with timeout 2000ms and 1500ms but we still see flickering.

Our Launch configuration has Adobe Target V2 extension configured with 3000ms timeout. I read in few articles that these two timeout configurations complement each and are required.

I have couple of questions

  1. Is pre hiding snippet required to be loaded on web pages where we do not have A/B test activity or personalized content? Or can we load only on pages where they are configured?
  2. Did anyone use Flicker Manager V1/V2 ? Does it solve the flickering and page performance issues?

1 reply

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
July 1, 2026

Hi ​@SrikanthPo3 

A few thoughts based on my experience with Target implementations: 

Is pre hiding snippet required to be loaded on web pages where we do not have A/B test activity or personalized content? Or can we load only on pages where they are configured? 

If a page has no A/B tests or personalized content, there is typically no risk of flicker, so applying a global pre-hiding snippet across all pages may add unnecessary rendering overhead and negatively impact Lighthouse/PageSpeed scores. Adobe also notes that hiding the entire page (body { opacity: 0 }) can worsen rendering performance metrics. 

Rather than hiding the entire page, Adobe recommends hiding only the containers that may be personalized. This approach usually provides a better balance between flicker prevention and page performance.  

https://experienceleague.adobe.com/en/docs/experience-platform/collection/use-cases/personalization/manage-flicker

 

Did anyone use Flicker Manager V1/V2 ? Does it solve the flickering and page performance issues? 

So far, I haven’t tried Flicker Manager V2 - beta version - as it’s not yet enabled for my org but you can read more about it below 

https://experienceleague.adobe.com/en/docs/target/using/administer/content-pre-hiding 

 

About timings - 

The pre-hide timeout and the Adobe Target v2 extension timeout serve different purposes. 

  • Pre-hide timeout (1500ms/2000ms) = how long content stays hidden before being revealed.
  • Target extension timeout (3000ms) = how long at.js waits for a Target response before treating the request as timed out

So I would suggest 

  • Verify when at.js/websdk is actually loading relative to Launch and page rendering. 
  • Check Target response times in browser DevTools.
  • Instead of hiding the entire body, hide only personalized containers. This often improves performance scores significantly. 
  • Confirm whether flickering occurs only on pages with activities or across all pages.
  • For Flicker V2- check once with Adobe Support team. 

Try out and let us know how it’s going - Happy to help further. 

Thank you. 

Thanks, Gokul
S
SrikanthPo3Author
Level 5
July 2, 2026

Thanks ​@Gokul_Agiwal for your response.

I have raised Adobe Support ticket for the same and the response I got for the question whether pre-hiding snippet is required on all pages is that it is required on all pages where Launch script loads, but I am still not convinced with this response

Gokul_Agiwal
Community Advisor
Gokul_AgiwalCommunity Advisor
Community Advisor
July 2, 2026

Hi ​@SrikanthPo3  Sometimes support team may not have the full picture. 

In documentation only Adobe specifically recommends targeting only the containers that may be personalized for better performance.  See below 

https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/at-js/manage-flicker-with-atjs#managing-flicker-when-loading-atjs-asynchronously 

https://experienceleague.adobe.com/en/docs/target-dev/developer/client-side/at-js-implementation/target-atjs-faq#can-i-load-the-target-library-asynchronously

However if you’ve started using Flicker Manager V2 - which is still in beta version, May worth to try adding snippet directly in page. 

Can you tell how’s your target implementation has been setup? Are you using at.js/websdk? 

So we can go bit deeper. Hope this helps. 

Thank you 

Thanks, Gokul
Terms & ConditionsAccessibility statement

Loading footer...