Not able to see personalized content for any activity | Community
Skip to main content
V
varun790
Level 2
February 28, 2023
Solved

Not able to see personalized content for any activity

  • February 28, 2023
  • 1 reply
  • 1634 views

Hi,

I am new to Adobe Target. I have done the direct integration of AEM with Adobe Target with out using launch, I have used IMS config.

  • Then we created few activities and used audiences like Users from India, Chrome Users etc. and made the changes in webpages respective to audience.
  • After activating the Activities when we check using Activity QA URL we don't see the changes according to the audience.
  • We see mbox call in network tab and its not failing, no console errors. AtJs is loading.
  • Are we missing something here? due to which we are able to see personalized content.
    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 Perrin_Ennen

    Hi @varun790 I would suggest you to set up a very simple XT test - which e.g. in HTML Offer only contains the following.

     

    <script>console.log('Adobe Target Test')</script>

     

    Here you can see in the Developer Console in the browser if the log is executed or not. If not, there is probably something wrong with the implementation.

    1 reply

    Perrin_Ennen
    Community Advisor
    Perrin_EnnenCommunity Advisor
    Community Advisor
    February 28, 2023

    Hi @varun790,

    It helps to test the QA link in an incognito window. Here also agree to the consent accordingly. It is also important that no extension is on here such as ad blocker etc.

     

    For the QA Link all other activities are disabled by default. This can be adjusted via the parameters accordingly (at_preview_listed_activities_only=true or at_preview_listed_activities_only=false).

     

    In the network tab you can see if requests have been made. To do this, search for "delivery" in at.js 2.x or "mbox" in at.js 1.x.

     

    If Adobe Target Premium is used. The at_property must also be specified accordingly.

     

    I am looking forward to your reply. Maybe some of it will help.

      V
      varun790Author
      Level 2
      February 28, 2023

      Thank you @perrin_ennen for you reply ..but none of these worked for me.

      Incognito is disabled in my Org browser ..that's the only one I could not check . I did try hard reload and all.

       

      I did find delivery and mbox both the calls.

       

      I can not install experience platform debugger extension also as blocked by org.

      Anything else I can check?

        Perrin_Ennen
        Community Advisor
        Perrin_EnnenCommunity AdvisorAccepted solution
        Community Advisor
        March 2, 2023

        Hi @varun790 I would suggest you to set up a very simple XT test - which e.g. in HTML Offer only contains the following.

         

        <script>console.log('Adobe Target Test')</script>

         

        Here you can see in the Developer Console in the browser if the log is executed or not. If not, there is probably something wrong with the implementation.

          Terms & ConditionsAccessibility statement

          Loading footer...