gtm.js snippets to stop honoring gtag('config') commands from October 2, 2026; sites must use gtag.js
- Date
- Aug 27, 2026
- Effective
- Oct 2, 2026
- Regions
- Global
- Primary source
- Tag Manager Help
Google notified container owners that Google Tag Manager (gtm.js) snippets will no longer recognize or wait for gtag('config') commands; from October 2, 2026 all gtm.js snippets initialize on container load regardless of any config command. Sites that load a GTM snippet but rely on gtag('config') to pass parameters or configure Google Ads or GA4 tags must switch to the gtag.js snippet or use the new gtm init trigger.
Google's help page 'Set up your Google tag installation correctly for gtag.js' explains which installations are supported. The October 2, 2026 date appeared in Google's email to affected container owners; the help page itself says only that the change is coming soon. New deployment snippets no longer include the gtag config command, and the gtm init trigger can be set to wait for a config command to preserve legacy setups.
Sources
- open_in_newSet up your Google tag installation correctly for gtag.jsTag Manager Help · Aug 27, 2026
- open_in_newGoogle Tag Manager Snippets Will Stop Honoring gtag('config') CommandsPPC News Feed · Aug 27, 2026
- open_in_newNew Version for Google Change? (Google email quoted with October 02, 2026 date)WordPress.org support forum · Aug 20, 2026