A/B Test Issue in Production | Community
Skip to main content
Luca_Lattarini
Luca_Lattarini
Level 9
November 1, 2023
Question

A/B Test Issue in Production

  • November 1, 2023
  • 2 replies
  • 1291 views

Hello guys,

 

I am running a simple A/B test with Experience A and Experience B.  During the test in UAT i had no issue but after publishing th A/B Test with html injection, I am not able to see the experience B with injected html.

Any idea? If I try to see the QA link I cannot see the Experience.

Thanks

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    2 replies

    K
    KMarchewa
    Level 3
    November 1, 2023

    It is is hard to say without seeing the code/Experience, but is it possible the DOM (page) structure changed? Also, I find that I often need to refresh the page once after initially loading the test using a QA link.

      alexbishop
      Adobe Employee
      alexbishopAdobe Employee
      Adobe Employee
      November 1, 2023

      Assuming you see the request being made to Target and a response being returned with offer content, the most likely cause is that the HTML structure of the page has changed and your CSS Selector no longer exists. You can check if this is the case as follows:

      i) If you're using the Visual Editor, you can check to see what the selector is by clicking the i icon:


      ii) Go to the page where your test should run, open Developer Tools, and enter

      document.querySelector('<copy element value from vec>') e.g. document.querySelector('HTML > BODY > DIV:nth-of-type(2) > DIV:nth-of-type(2)')


      If your CSS selector isn't valid then you will see a null value

      If that is the case then you need to update the CSS selector in the Target Visual Editor



        Luca_Lattarini
        Luca_LattariniAuthor
        Level 9
        November 2, 2023

        I dont have issue during the creation of the experience but when i try QA link i cannot see the experience

          Terms & ConditionsAccessibility statement

          Loading footer...