Isn’t working with Google Optimize

  • Resolved inspired888

    (@inspired888)


    2 years, 5 months ago

    Hi there,

    A bit of background: As a web developer for past 25+ years, I’ve set up GA and GTM on a lot of WordPress sites. I’ve also successfully set up Google Optimize on multiple sites. However … I normally do it manually, adding in the various js codes, etc.

    On a site I’m working on now, I thought I’d give Site Kit a try, as I figured my client might enjoy having some basic GA stats and data showing up on a dashboard in WordPress.

    The site already had GTM set up on it, and GA set up via GTM.

    After successfully connecting GSC, GA, Page Insights, GO, and GTM, on this site (via Site Kit, which recognised GTM and GA where already in place, so it opted to not add in the JS codes again, etc.), Optimize is giving me errors when I try to start a A/B split test.

    It’s showing me this: https://ibb.co/9Hsj8CB

    – Analytics pageview not detected
    This page isn’t sending pageview hits to Google Analytics property (UA-XXXXXXXXX-1) configured for this experiment. You won’t be able to measure usage of your site or monitor performance of Optimize experiments. Make sure that your Analytics tracking code (either analytics.js or gtag.js ) is set up correctly.

    – Analytics configuration mismatch
    All Analytics tracking code on the page must have the same tracker configuration settings. This is important a) if you use Google Tag Manager to fire Analytics hits and hard-coded Analytics + Optimize to deploy Optimize, or b) if you deploy both Analytics and Optimize tags via Tag Manager . If you deploy Optimize via a Tag Manager tag, the best practice is to use the shared Google Analytics Settings variable in Tag Manager, which ensures that your tracker settings match between tags.

    The following tracker configuration properties don’t have the same configurations: allowLinker,cookieDomain.

    – Anti-flicker snippet not found
    You haven’t installed the anti-flicker snippet and your visitors may experience page flicker, where they briefly see the original page before your experiment loads. This can skew your experiment results and confuse visitors.

    When I test the page, I see GA and GTM and GO tags all firing fine. So I am not sure why GO analyser is coming back with these errors.

    Any suggestions would be appreciated.

    Thanks,

    Jonathan

    • This topic was modified 2 years, 5 months ago by inspired888.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi @inspired888,

    Thanks for reaching out, and providing a thorough explanation of what’s occurring. When you perform an Optimizer check what may be occurring is you are logged into your site at the same time. If you have the default configurations applied within Site Kit’s Analytics settings, to not count logged in traffic, then this Optimize check will fail, as an Analytics check won’t fire from Optimize. I suspect this is the cause for the “Analytics pageview not detected” error you’re encountering.

    To resolve this, can you log out of your site, and then perform another check for the Analytics snippet. Alternatively you can login to Optimize from a Chrome browser incognito window, before then performing a check once more.

    With regards the “Anti-flicker snippet not found” warning can you check and ensure that this particular setting is applied within your Site Kit Optimize settings, as per the below:

    Let me know how you get on with performing another check after performing the above two suggestions. In the meantime I’ll look into the other Analytics warning you shared. So I can suitably troubleshoot this please share your Site Health information privately using this form.

    Thread Starter inspired888

    (@inspired888)

    Hi James,
    Thanks for the assistance.

    I have tested via another browser (not logged into WP), and it did get rid of the “Analytics pageview not detected” issue.

    The Anti-flicker code is already activated in Site Kit.

    Clean-Shot-2022-10-12-at-10-05-47

    I still get the Anti-flicker issue, and the “Analytics configuration mismatch” issue.

    I should add, that I’ve also now tried removing the GTM code I had previously added to the page, and set Site Kit to insert it. That hasn’t helped the situation.

    • This reply was modified 2 years, 5 months ago by inspired888.
    Thread Starter inspired888

    (@inspired888)

    I’ve submitted the requested data.

    Plugin Support James Osborne

    (@jamesosborne)

    Many thanks for the update. Good to know that you no longer encounter the “Analytics pageview not detected” error. If this was the only error, with the others being warnings, this may allow you to proceed with Optimize experiment set up.

    I still get the Anti-flicker issue, and the “Analytics configuration mismatch” issue.

    From reviewing your site manually and with the tagassistant.google.com service it looks like you may be using Tag Manager to insert your Universal Type Analytics snippet.

    What I suspect may be happening is Optimize is looking at the Google Analytics 4 snippet, as opposed to your Universal Type Analytics snippet, which isn’t printed directly in your sites source code.

    In order to try and resolve this please remove the Universal Type Analytics tag from your connected Google Tag Manager container from tagmanager.google.com, before publishing this latest change. After doing this please revisit your Site Kit Google Analytics settings, and ensure that the your Google Analytics 4 snippet has been placed via Site Kit, rather than the module depending on your Google Tag Manager Analytics placement. I’m happy to check your site once performed.

    Once you’ve followed the suggestion above, please perform an optimize check once more. The above check differs to you removing the Tag Manager snippet manually, which you’ve already done, before allowing Site Kit to insert this for you.

    Let me know how you get on, and whether you then “Analytics configuration mismatch” warning. We can also look into the anti ficker snippet after we resolve the above error.

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Isn’t working with Google Optimize’ is closed to new replies.