Your Google Tag configuration will soon no longer be supported

  • Resolved xxxLesy

    (@xxxlesy)


    1 month ago

    I’m using the GTM integration for Consent Mode v2 (with GTM id in 1 site and GA4 id in the other 2). Then I have 

    <script>gtag('consent', 'update', { 'ad_storage': 'granted', 'analytics_storage': 'granted'});</script>

    in analytics category head on accept.

    Just got an email from Google for these sites:

    We noticed that some or all of your website pages deploy Google tag GT-xxxxxxxx, G-xxxxxxxxxx, G-xxxxxxxxxx via a Google Tag Manager snippet (gtm.js). This configuration will soon no longer be supported.

    What’s changing?

    To ensure consistency across all websites using the Google tag, we are standardizing our tagging snippet behavior. Starting on October 02, 2026, all gtm.js snippets will initialize on container load, regardless of any gtag(‘config’) commands.
    To continue using the gtag configuration code, you must ensure all pages on your site use the gtag/js code snippet.

    Next steps
    If you don’t take any action, this update may alter how your tags behave. Please update your tag deployment to use gtag/js instead of gtm.js, by following these instructions.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Jane

    (@janeaustin)

    1 month ago

    Hi @xxxlesy

    Thanks for reporting this.

    We will look into it and provide an update soon.

    Hope this helps. 

    Plugin Support Jane

    (@janeaustin)

    1 week, 3 days ago

    Hi @xxxlesy

    Thanks for your patience. We’ve looked into this. Google’s notice is about Google tag IDs (those starting with G-, GT- or AW-) being loaded through the Google Tag Manager loader. The Consent Mode v2 integration is built for GTM container IDs (GTM-XXXXXX), so a GA4 ID entered there ends up loaded in the way Google is phasing out. Container IDs starting with GTM- are not affected.

    Please check the ID on your “GTM” site too. Google’s email lists a GT- ID, and GT- IDs are easy to mistake for GTM- container IDs.

    We’re preparing an update so the integration loads any non-GTM ID with the standard gtag.js snippet, keeping the Consent Mode defaults in place. Once you update, no settings change is needed. If you’d like to act before then, you can create a GTM container, add your GA4 tag inside it and enter the GTM- ID in the integration instead.

    Also, the integration already sends the consent update itself when a visitor accepts. You can probably remove the custom gtag(‘consent’, ‘update’) script from the analytics category. As written, it also grants ad_storage when a visitor only accepts analytics.

    Please let us know if you have any questions.

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.