3 Replies Latest reply on Oct 15, 2015 7:30 PM by Shekhar_Dhiman

    Issues seeing experiments on HTTPS sites

    Løjmann Level 3

      Hi,

      We have multiple clients who are running their full site over HTTPS, and we often experience that after setting up a A/B test it won't be visible on the live site.

      We are using Target Standard and when setting up the experiments, we are telling target to use the URL via HTTPS (https://customersite.xyz and not http://customersite.xyz). We can setup the experiment in the editor and here we do not see any issues. Changes are applied to the page (in the editor) directly. However, when activating the activity nothing happens on the live site. we have tried to wait for hours (even days) and nothing happens. When running experiemtns on other sites using HTTP, we do not experience this issue.

      Does anyone else experience the same issues, and do anyone have a suggestion on how to solve this?

      I will suspect this to be an issue with Adobe Target itself and not related to the specific customer (as we see it across clients). Could it be, that the mbox.js file in some cases tried to fetch HTTP content, and therefore the browser block the content? We are using mbox.js version 57 and still experiencing the issue.

      /Løjmann

      • 0. Re: Issues seeing experiments on HTTPS sites
        Shekhar_Dhiman Adobe Employee

        Thank you for confirming this and updating it on this thread.

        Cheers!

          • 1. Re: Issues seeing experiments on HTTPS sites
            Løjmann Level 3

            Just got a confirmation from the Target team saying this is a product bug and it is scoped for being fixed on September 30th.

            /Løjmann

            • 2. Re: Issues seeing experiments on HTTPS sites
              Shekhar_Dhiman Adobe Employee

              Hi there,

              Thanks for reaching out to Adobe Community.

              There could be multiple factors causing this. You may want to try the below steps to troubleshoot:

              1. To use mboxDebug, append an mboxDebug parameter to the end of your URL. The following table contains information about mbox-related URL parameters. 

                                             
              URL ParametersPurpose

              mboxDebug=1

              Debugger

              Adding this parameter to any URL with mboxes defined opens a pop-up window with valuable debugging details. Cookie information, PCid and Session ID values are written out, and all of the mbox URLs are visible. Click on a mbox URL to show the response for that mbox. More details are available inmbox_debug.pdf.

              mboxDebug=x-cookie

              Modify the cookie

              mboxDisable=1

              Disable mboxes on the page

              mboxDebug=x-profile

              View profiles set.

              mboxDebug=x-time

              Show response time for each mbox request

              mboxOverride.browserIp=Insert IP address

              Test geotargeting

              Test geotargeting with this URL parameter. Type an IP address as the value for this attribute, and Test&Target's geotargeting evaluates that IP address to match against any geotargeting or segmentation set in a campaign.

              2. Mbox.js sends a cookie called "em-disabled" to the visitor if target.js fails to load during delivery. This cookie prevents offers created using the Visual Experience Composer from rendering on the site. Visitors with this cookie neither see the test content nor get counted in those activity reports. All other offer content (from campaigns in Target Classic for example) continues to load. The cookie has a lifetime of 30 min from the time of load failure.

              Also try other steps mentioned in the Troubleshooting Doc.

              Thanks!