"Blinking" behavior when running XT test | Community
Skip to main content
July 29, 2020
Solved

"Blinking" behavior when running XT test

  • July 29, 2020
  • 3 replies
  • 2185 views

We are experience a "blinking" behavior when we run Experience Targeting test in our webpage. Is it due to the server call to identify whether the visitor qualify for a segment? Any difference if we create the segment via AA / AT / AAM? How can we avoid this? 

 

Thanks!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ryanr7

Hi @beckycky,

Hard to know what might be causing the blinking behavior with out more details. Can you share a link to the page with the activity running? Audiences/segment differences between AA/AT/AAM shouldn't impact a blink during page load. Is the blinking unique to this activity?

-Ryan 

3 replies

ryanr7Adobe EmployeeAccepted solution
Adobe Employee
July 29, 2020

Hi @beckycky,

Hard to know what might be causing the blinking behavior with out more details. Can you share a link to the page with the activity running? Audiences/segment differences between AA/AT/AAM shouldn't impact a blink during page load. Is the blinking unique to this activity?

-Ryan 

BeckyckyAuthor
July 30, 2020
Can I leave you private message regarding the link & how to see the blinking behavior? Seems like it only happens to qualified clients so need to perform extra step before you see that blinking bahavior.
PratheepArunRaj
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 30, 2020

Dear Beky,

'Blinking Behaviour' or 'Page Blank' will happen to all the customers who have their Header and Footer components embedded within their body. In Target, you would have enabled 'Body Hiding' inside target for the purpose to avoid flickering. So, Target will hide your entire body for a fraction of seconds before the response is received from the target leading to 'Blinking Behaviour' or 'Page Blank'. We have faced the same issue before years and went on with deep learning and exercises to avoid this, but the result is nill. Then we placed the Header and Footer Components out of Body. Then, on the page load, Header and Footer will load without hiding giving the experience to the customers that the page started loading already avoiding the 'Blinking Behaviour' or 'Page Blank'. Or you can ignore the entire 'Body Hiding' instead use the container you want to hide, this is also possible in Target.

body {opacity: 0 !important}

Change it to your container or ID.

#MyContainerID {opacity: 0 !important}

Thank You, Arun.

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
PratheepArunRaj
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
August 13, 2020

Hello Becky,

Have written a separate post on the Page Blank Issue or Blinking Issue. It should have the details you are looking for!

Link: https://terrynwinter.com/adobe-target-how-to-avoid-page-blank-and-flickering-issues/

Check and let me know if that is useful.

Thank You, Arun.

Thank You, Pratheep Arun Raj B (Arun) | Xerago | Terryn Winter Analytics
Adobe Employee
August 26, 2020

@beckycky Can you please confirm if Targe thas been deployed Synchronously or Asynchrosuly? If its an async implementation, then please ensure that the flicker control code is added in the source code before Target is implemented.

 

Regards,

Karan Dhawan