Preview Links Injecting Modifications Twice | Community
Skip to main content
M
MelissaMa7
Level 2
June 8, 2025
Solved

Preview Links Injecting Modifications Twice

  • June 8, 2025
  • 1 reply
  • 609 views

I have an activity where I have inserted HTML using Insert After or Insert Before on an element. Whenever I use the preview links to load the activity, it is like it fires twice and anything I have inserted after or before another element shows twice. Is there any way to get the preview link to only fire changes once?

Best answer by NarenKotipalli

@melissama7  I've reviewed the URL you provided and observed only a single call, with the experience rendering correctly on my end. However, I was able to replicate the double-loading issue you described when repeatedly changing cookie consent (accept → reject → accept). This happens because the page isn't reloading after the consent modifications. To resolve this, I suggest implementing a page reload after the second consent change.

1 reply

NarenKotipalli
NarenKotipalli
Level 3
June 9, 2025

@melissama7This issue may occur if the Adobe Target page load request is firing twice on the page or if the modifications were duplicated during the activity setup. If possible, please share the preview URL or the Target call response object so we can better understand the issue and provide a more accurate solution.

M
MelissaMa7Author
Level 2
June 9, 2025

Yes, it seems like the page load request is firing twice. Here is the preview link: Cat® Filters & Fluids. We have Adobe Target set to fire after you accept cookies. I will say I am facing another issue too where I have to accept cookies, reject them, and then accept them again for the experience to show. After doing that it shows but inserts all my changes twice.

NarenKotipalli
NarenKotipalliAccepted solution
Level 3
June 9, 2025

@melissama7  I've reviewed the URL you provided and observed only a single call, with the experience rendering correctly on my end. However, I was able to replicate the double-loading issue you described when repeatedly changing cookie consent (accept → reject → accept). This happens because the page isn't reloading after the consent modifications. To resolve this, I suggest implementing a page reload after the second consent change.

    Terms & ConditionsAccessibility statement

    Loading footer...