On 8 October 2026, Google changed how Google Tag Manager and the gtag('config') command work together. If your site runs both at once, or your GTM container uses a trigger for all events, some tags may fire an extra time. The result: duplicated or inaccurate conversions in Google Ads and Google Analytics.
What changed
According to the Google Tag Manager release notes, the GTM container (gtm.js) now initializes as soon as it loads, whether or not a gtag('config') command is on the page. Until now, the container could wait for a config call placed elsewhere on the page.
The second change matters more for tracking. Config commands now appear in the dataLayer as a separate gtag.config event. Google warns directly that containers using wildcard custom event triggers may fire tags because of it.
Who is affected
Two types of sites are hit:
- A GTM snippet combined with gtag('config') using a G-, AW- or DC- ID, without loading gtag.js. Google calls this setup unsupported and warns that tag behavior may change unexpectedly. Owners of affected containers received an email.
- Containers with a custom event trigger using the regex .* (with regex matching enabled). According to Google's help page, such a trigger fires on every event, so now also on gtag.config. This applies even to sites with a correct gtag.js installation.
PPC Land lists conversion, remarketing, logging and custom HTML tags as examples. Measurement expert Simo Ahava adds that .* triggers get one extra firing on every page where config runs.
What it means for your business
If a conversion tag fires twice, Google Ads sees more conversions than you actually got. Automated bidding then learns from wrong data and spends your budget based on inflated numbers. GA4 events and remarketing lists can be inflated the same way.
The unsupported mix of GTM and a standalone gtag('config') is common. It happens when one vendor installs GTM and another later adds Google Ads or Analytics code straight into the site template.
What to do now
- 1Check your site's source code for both a gtm.js snippet and a gtag('config', 'G-…') or 'AW-…' line.
- 2If you find both, choose one of the two paths Google recommends: keep only the gtag.js snippet right after the opening head tag on every page, or keep GTM and set up the Google tag inside the container.
- 3In GTM, search for custom event triggers set to .* and add a condition that excludes the gtag.config event.
- 4Verify the result in Tag Assistant ("Google tags found") or in the Network tab of Chrome DevTools.
- 5Compare conversion counts in Google Ads and GA4 before and after 8 October. A sudden jump without campaign changes is a sign to act.
Not sure whether this affects your site? See our PPC services and let us check your conversion tracking. For a bigger fix, a technical website audit is worth it too.
Sources

Written by
Peter GáboríkProject Manager – AI, Automation & SEO
Project manager and founder of Weboptim. Builds growth strategies around SEO, automation and AI; in online marketing since 2017.
Related service
Tips that save time – once a month
One e-mail a month: a new guide, the automation of the month and one number from practice. No spam.



