Announcement

Collapse
No announcement yet.

Google Optimize & Cloudflare

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Google Optimize & Cloudflare

    Does anyone know how to get Google Optimize to play nicely with Cloudflare? I am having an issue setting up an A/B test in Optimize for our Miva Basket page I believe because of Cloudflare being in place.

    #2
    Not that this helps but as Google loves to do, Optimize is being killed off: https://support.google.com/optimize/...12979939?hl=en

    What issues are you running into? I'd not expect to have issues on a basket page because those would be served with a cookie, and cookies prevent Cloudflare from caching the content unless there have been some very abnormal settings configured to override that behavior, but then all kinds of very bad things would likely be happening.
    David Hubbard
    CIO
    Miva
    [email protected]
    http://www.miva.com

    Comment


      #3
      Unfortunately, I read about that as well. I was hoping to be able to run this experiment before they did away with it. Although I am open to an alternative that isn't too expensive.

      The issue is I put in the URL to the Basket page to experiment on and setup the Variant page. When I click "Edit" to try to modify the Variant page, I get an error after a few seconds:

      "The Optimize editor failed to load. Ensure that you allow third-party cookies from optimize.google.com and www.google-analytics.com, check your network connection and your CSP policy (https://support.google.com/optimize/answer/7388531), and try again."

      I was researching around and thought that Cloudflare might be the culprit. I could definitely be wrong on that.

      I just need to test the Basket page with a popup vs without a popup. On another post someone mentioned just modifying the CSS on the Variant page but with the Editor in Optimize not working, I haven't been able to do that.

      Comment


        #4
        Ah, that's probably not Cloudflare. I suspect that could actually be CSP policy, but could also easily be both built-in default tracking protection in your browser, or add-on tracking / cookie blockers if you have any. If you send in a ticket and reference this thread with the site in question, we can check the headers for you. For the cookies, I'd try disabling all tracking protection on the site in question and see if that helps. In Firefox, for example, using a private browser automatically disables plugins, so you'd only need to also disable the built in tracking protection via the shield to the left of the URL; that's my primary so not sure if others behave similarly or make it easier/harder to disable the built-in protection on a given site.
        David Hubbard
        CIO
        Miva
        [email protected]
        http://www.miva.com

        Comment

        Working...
        X