Skip to main content
SoufianeLa
Level 2
September 13, 2024
Solved

Adobe Target not Working

I am working on builing couple of components using Adobe Target, but it is acting weird, especially, with JS code. All changes I am doing, I can see them in Target, but not when I am using QA links. 

 

Any thoughts?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Matthew_Ravlich_ACG
    Matthew_Ravlich_ACGAccepted solution
    Community Advisor
    September 13, 2024

    Hi @soufianela,

    Sorry to hear you are having issues. This could be due to several reasons, but here are the ones I believe to be the most common:

    1. Caching Issues: Sometimes, browsers cache the old page version, preventing new changes from appearing.
      Solution: Clear your browser cache or use an incognito/private browsing window.
    2. JavaScript Errors: If your JS code contains an error, it might work in the Target editor but fail on the actual page.
      Solution: Open the browser’s developer console to check for JavaScript errors. Ensure your code is error-free and compatible with the site’s existing scripts.
    3. Order of Scripts Loading: Your JS code might execute before the necessary elements are available in the DOM.
      Solution: Wrap your JS code in a DOMContentLoaded or window.onload event listener to ensure it runs at the right time.
    4. Adobe Target Libraries Not Loading: Sometimes, target libraries can be blocked on your browser. It can sometimes relate to geo-location or consent settings.
      Solution: Ensure that the Adobe Target libraries are correctly implemented on your environment and are not being blocked.

     

    I hope that helps!

     

    Matthew Ravlich | ACG Digital



    View in thread

    2 replies

    Matthew_Ravlich_ACG
    Community Advisor
    Matthew_Ravlich_ACGCommunity AdvisorAccepted solution
    Community Advisor
    September 13, 2024

    Hi @soufianela,

    Sorry to hear you are having issues. This could be due to several reasons, but here are the ones I believe to be the most common:

    1. Caching Issues: Sometimes, browsers cache the old page version, preventing new changes from appearing.
      Solution: Clear your browser cache or use an incognito/private browsing window.
    2. JavaScript Errors: If your JS code contains an error, it might work in the Target editor but fail on the actual page.
      Solution: Open the browser’s developer console to check for JavaScript errors. Ensure your code is error-free and compatible with the site’s existing scripts.
    3. Order of Scripts Loading: Your JS code might execute before the necessary elements are available in the DOM.
      Solution: Wrap your JS code in a DOMContentLoaded or window.onload event listener to ensure it runs at the right time.
    4. Adobe Target Libraries Not Loading: Sometimes, target libraries can be blocked on your browser. It can sometimes relate to geo-location or consent settings.
      Solution: Ensure that the Adobe Target libraries are correctly implemented on your environment and are not being blocked.

     

    I hope that helps!

     

    Matthew Ravlich | ACG Digital



    Translate
      RiteshY18
      Community Advisor
      RiteshY18Community Advisor
      Community Advisor
      September 19, 2024

      @soufianela  consider using Adobe Experience debugger chrome extension and debug  for network call and console error in regards to Target 

      Translate
        Terms & ConditionsAccessibility statement

        Loading footer...