Expand my Community achievements bar.

Applications for the 2024 Adobe Target Community Mentorship Program are open! Click to the right to learn more about participating as either an Aspirant, to professionally level up with a new Certification, or as a Mentor, to share your Adobe Target expertise and inspire through your leadership! Submit your application today.
SOLVED

SPA implementation - initial page load - flicker

Avatar

Level 2

I have the following rule in Launch for initial page load for a SPA.

 

Load Target library  > set parameters > Fire page load request > trigger view

 

I am getting flicker on the experience... I presume this is because the VEC is targeting content based on the view but I have that initial page load request being sent first prior to the trigger view.

 

In the Target documentation - https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementati...

 

Step 3: Execute Target request

Step 4: Call trigger view()

 

Because the Target request you initiated in Step 3 could return experiences for both Page Load execution as well as Views, ensure that triggerView() is called after the Target request is returned and finishes applying the offers to cache. You must execute this step only once per view.

 

Is this suggesting I don't call triggerView() on page load until the Target request is complete? If so, what success event should I be looking for to know the offers are in the cache?

 

Would this not still cause flicker?  For example:

 

1. Target request sent 

2. Target returns no experience and page renders

3. triggerView() sent 

4. Page updates with cached experience?

 

Thanks 

 

 

 

 

 

 

 

1 Accepted Solution

Avatar

Correct answer by
Level 4
1 Reply

Avatar

Correct answer by
Level 4

I was able to fix this by setting the "bodyHidingEnabled" config option to false

 

https://experienceleague.adobe.com/docs/target/using/implement-target/client-side/at-js-implementati...