Support » Plugin: ExactMetrics - Google Analytics Dashboard for WordPress (Website Stats Plugin) » new GTAG.js Analytics code (replaces Analytics.js code)

  • Resolved fluiditystudio

    (@fluiditystudio)


    Google is sending out emails about updating to their Global Site tag for tracking and everything else. Below is an example.

    <!-- Global site tag (gtag.js) - Google Analytics -->
    <script async src="https://www.googletagmanager.com/gtag/js?id=UA-YOUR-NUMBER-1"></script>
    <script>
      window.dataLayer = window.dataLayer || [];
      function gtag(){dataLayer.push(arguments);}
      gtag('js', new Date());
    
      gtag('config', 'UA-YOUR-NUMBER-1');
    </script>

    Will you be updating your plugin to use this gtag.js any time soon?

Viewing 12 replies - 1 through 12 (of 12 total)
  • I have the same question. Thanks.

    Same also

    dmac

    (@darrenmcentee)

    Hi, any update on this?

    Boris

    (@ispacecrusader)

    I would also like to know when we can expect the update for this.

    moi aussie

    Plugin Author chriscct7

    (@chriscct7)

    Hi folks,
    Our team works extremely closely with Google’s tagging team (we meet with them every few weeks) so that we’re synchronized on product rollouts, work on new features for Google Analytics, and some other initiatives.

    First and foremost, no action is required from any of our users. ExactMetrics handles all tracking implementation and we automatically keep it up to date with new Google guidance, WordPress changes, plugin changes, and so forth.

    The email(s) (depending on which sequence of the split tested email campaign you got) from Google’s Marketing team regarding gtag.js we’re aware of. We work directly with their product developers and product leadership to operate with insights we gain from being a technology partner with them, and make sure you all have the absolute best experience possible.

    Let’s first talk about gtag.js. gtag.js, when used in an analytics context, is simply a wrapper for analytics.js (loading gtag.js literally will load analytics.js). There are no new analytics features that are gained from changing over, however there are currently some disadvantages we’re working with them on resolving.

    Currently Google has some features they haven’t yet ported over, and some bugs we’ve reported that we’re working with them to identify and fix before we migrate our users over.

    Additionally, Google has no upgrade path for analytics.js events to gtag.js events. So if you’re a user who implemented events and didn’t use our APIs to do it or if you also run a plugin that implements those events, then those would break on changing over. As a plugin that prides itself on ease-of-use for our users, we hold ourselves to a high standard with regards to making sure we look after our user’s best interests, always, and we want to ensure our users tracking never breaks, particularly in the run up to the holiday season. And if Google doesn’t provide a solution for that (like in this case) that means we roll up our sleeves and build it ourselves, because I (and the rest of our team) take the experience of our users very seriously.

    To that end our development team is working with Google’s developers on many initiatives including a custom shim that will make sure any of those custom events just keep working, like magic.

    Our goal at ExactMetrics is to bring the best analytics tracking and reporting to our users, and we always follow that guidance, putting the best interest of our users first, always. We’re working incredibly closely with their team to make sure our users don’t lose features, and have an absolutely seamless upgrade experience.

    Like when we served as a day 1 launch provider for many of their new analytics & related features/services, we’re looking forward to moving you all over, but as a product priding itself on ensuring our users get the high level of experience they expect, we’ll have everyone moved over to gtag.js as soon as Google’s team is ready for us to move everyone over.

    Looking forward to helping you all continue to grow your sites faster than ever before,
    – Chris

    Boris

    (@ispacecrusader)

    @chriscct7 Thank you for your very elaborate and clear answer. Good to know that you are keeping a close eye on Google’s updates. I will wait patiently for the plugin update once Google has resolved the issues.

    And it happened exactly as expected! Google has rolled out Analytics 4 and the basic functionality of this plugin is simply not compatible anymore.

    The plugin can only connect to older, already existing GA properties, but cannot even see newly created GA4 properties in the GA account.

    Very weird to watch for a plugin whose developers claim to check with Google on a weekly basis …

    Even on the Exact Metrics website there is no clear documentation on how to tackle this problem or how to connect ExactMetrics with the new GA4.

    Wouldn’t surprise me if that would also be rolled out as a PRO feature.

    Plugin Author chriscct7

    (@chriscct7)

    @nandorras15 You’re confusing 2 similar but completely different launches. GA 4, or App + Web as it’s been previously called, has been available for all Google Analytics users for many months now, the only thing they did “today” was simply rename it to GA 4. It’s a marketing launch, not a product launch.

    The actual product of what’s now called GA 4 is something we’ve been working with their team on for almost a year now. It’s simply a repackaged & rebranded version of Firebase analytics, designed originally for mobile app analytics. For that reason, their team, even as of today, is still scrambling post launch to add a ton of the features needed to support web analytics. For example, the full eCommerce reporting is not availalble, nor is half of the developer APIs (measurement protocol just exited private beta and entered public beta for it a few hours ago).

    Our plan, as the same with most of the Google Analytics Technology Partners, is to launch support for v4 once Google has finished fixing the backlog of bugs we’ve reported and also rolled out the missing features.

    I’m not sure where you get this idea that somehow its going to get limited to Pro comes from, but 100% it’s definitely not the case for us, or for that matter any of the other Analytics Partners that I’ve talked to.

    @chriscct7 Thank you for the detailed response. It has uncovered and clarified a lot. However, the fact remains that when you create a new account in your Analytics Dashboard, Google pushes you towards this new App + Web / Firebase / GA4 functionality.

    And it seems that it is no longer possible to set up a GA account in the traditional way. And as long as that is not possible, ExactMetrics will not connect to your GA property. Or there must be a way to switch the account back to Universal Analytics and I still haven’t been able to find that option so far.

    Plugin Author chriscct7

    (@chriscct7)

    It is not possible to switch a property from Web to App + Web or vice versa, you just need to make a new Web one. If you’re having trouble with that, please feel free to reach out to ExactMetrics.com/lite-support and our team can absolutely help you with that — that’s what we’re here for 🙂

    -Chris

    Okay! I was able to find a solution myself. I couldn’t find the option to convert the property to a Universal Analytics account anywhere. So what I did is delete the account and create a new one.

    During step two during the account creation process you have the choice of advanced options. Here you have to make sure that “Create a Universal Analytics property” is enabled. I have attached a screenshot for reference.

    It doesn’t matter whether you have a GA4 & Universal Analytics account or just a Universal Analytics account. Both are recognized by ExactMetrics. You can also leave the enhanced measurement functionality on. This does not prevent ExactMetrics from finding your GA property!

    Screenshot: https://photos.app.goo.gl/Gh3juPhpSrTnL9xEA

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘new GTAG.js Analytics code (replaces Analytics.js code)’ is closed to new replies.