Expand my Community achievements bar.

Join Cristinel Anastasoaie, Timothy Furlow, and Brent Kostak, WEDNESDAY, 2/28/24 @8am PT for the next Adobe Target Community Q&A Coffee Break on topics from the recent High Performance Recommendations Webinar PT 2 of the ongoing Target Personalization Maturity Webinar Series
SOLVED

Adobe Target Experiment - Failing to load experience

Avatar

Level 2

Currently we have an Adobe Target Experiment active on our site for an A/B experience. It seems to fail to load the experience on the initial load of the website (we have cleared all cookies/cache/history). However, when we refresh the page, Adobe Target successfully loads the experiment in either A or B experience. 

 

Any suggestions as to what could be causing this to happen? Why does Adobe Target experience only begin to load after a refresh? 

 

 

1 Accepted Solution

Avatar

Correct answer by
Employee Advisor

Hi @WesPhg 

 

There could be multiple reasons this issue is occurring,

First of all, check how Adobe Target has been implemented on your page.

If it is SPA and if Target is implemented on page load through launch and you are trying to reach the page after few steps target won't get triggered on page load since page load doesn't happen in SPA.

To debug it further keep your debugger on, right click on page > click inspect > go to network tab > filter by mbox/delivery depending on AT extension version.

Check whether you are seeing target calls getting triggered on reaching out to the page.

If target is getting triggered check whether you are qualifying for activity, if yes check which experience you are falling into.

 

If all these look fine, lastly check whether your modifications are working fine on first load of page. Check whether there are any console errors.

 

Hope this helps.

View solution in original post

1 Reply

Avatar

Correct answer by
Employee Advisor

Hi @WesPhg 

 

There could be multiple reasons this issue is occurring,

First of all, check how Adobe Target has been implemented on your page.

If it is SPA and if Target is implemented on page load through launch and you are trying to reach the page after few steps target won't get triggered on page load since page load doesn't happen in SPA.

To debug it further keep your debugger on, right click on page > click inspect > go to network tab > filter by mbox/delivery depending on AT extension version.

Check whether you are seeing target calls getting triggered on reaching out to the page.

If target is getting triggered check whether you are qualifying for activity, if yes check which experience you are falling into.

 

If all these look fine, lastly check whether your modifications are working fine on first load of page. Check whether there are any console errors.

 

Hope this helps.