Rows of colorful shipping containers stacked side by side, seen from above.

Conversion tracking

Google is folding the Google tag into Tag Manager containers. What changes for my ad conversion tracking?

By The Tofu team ·

Nothing changes on its own. Google is turning Google tags into full Tag Manager containers, and since October 12, 2026, Tag Manager can "optimize" yours. That moves Google tag settings to a new Settings tab and sends data to Google Ads without loading gtag.js. Google says "no changes will be made automatically," and your event tags and triggers stay. The risk comes when you accept the prompt, or if your site relies on gtag('config') code next to a Tag Manager snippet: since October 8, 2026, those snippets ignore it.

As of October 2026.

What changed

BeforeNow
Sites with only the Google tag (gtag.js)Google tag settings onlyBeing upgraded to Tag Manager containers, with triggers, debugging and version control. Google says what the tag does on your pages doesn't change
How a Tag Manager container sends data to Google Ads and GA4Loads extra JavaScript (gtag.js)After you optimize, destination tags send data directly, which Google says is faster
Where Google tag settings liveIn the Google tag screensA new Settings tab in Tag Manager, after you optimize
Links between the container and your Google Ads or GA4 accountsNot created automaticallyCreated automatically when you optimize, with "Read" access by default
New installation snippetsIncluded a gtag('config') commandAll the same, with no config command; Google recommends setting initialization with the init trigger
A Tag Manager snippet (gtm.js) with gtag('config') code on the pageRecognized the config commandsInitializes on container load "regardless of any gtag('config') commands" (since October 8, 2026)
Containers loaded through unsupported pathsFell back to Google-only tagsThe ID decides (since July 9, 2026): GTM- IDs run every tag type; G- or AW- IDs run only Google's tags and variables
Setting up a conversion without codeNo such optionVisual tagging, in beta, for Google Ads purchase conversions only

Google first published this plan on May 20, 2026, according to PPC Land, which quoted the same help article that now carries an August 20, 2026 date. The changes reached Tag Manager in steps from July to October 2026, with container optimization released on October 12 (see the dates below).

Who it affects

  • Sites with only a Google tag. If your site has a G- or AW- tag pasted in and no Tag Manager, you gain Tag Manager features, and nothing on the page changes. One limit matters for B2B: Google says containers with G- or AW- IDs can send data "exclusively to Google services." To manage the LinkedIn Insight Tag or Meta pixel in Tag Manager, you need a GTM- container.
  • Tag Manager users with Google tags inside. You'll see an "Optimize your Tag Manager container" banner. Accepting it consolidates your Google tags into destination tags and a Settings tab. Google says your event tags and triggers are kept.
  • Sites that pair a GTM snippet with gtag('config') code. Google calls loading a G-, AW- or DC- ID through the GTM snippet with config commands an "unsupported implementation" and says it emailed affected users. Since October 8, Google says these snippets start up without waiting for those commands, so settings passed in them may not apply.
  • Containers with wildcard custom event triggers. Config commands now show up in the data layer as gtag.config events, and Google warns these may make such triggers fire.
  • Agencies and consultants. Optimizing creates account links and sets who can see the container from Google Ads and GA4.
  • Lead gen advertisers hoping for no-code form tracking. Visual tagging covers only purchase conversions for now. It needs an order confirmation page and an authorized credit card to place a test order, so it doesn't help with demo request or contact forms yet.

Who can ignore it for now: if you use a GTM- container with Google's standard snippet, have no gtag('config') code on your pages, have no wildcard custom event triggers, and don't accept the banner, nothing changes.

What to do now

  1. Check what your site loads. In Chrome Developer Tools, open the Network tab, reload the page, and see whether requests go to googletagmanager.com/gtag/js or /gtm.js, and with which ID. Google Tag Assistant also lists the tags it finds.
  2. Fix an unsupported setup. If a GTM snippet sits next to gtag('config') code, Google's fix is either to use the standard Google tag (gtag.js) snippet, or to keep the GTM snippet with your GTM- ID and set up the Google tag inside Tag Manager.
  3. Check wildcard custom event triggers and make sure tags on them don't now fire on gtag.config events.
  4. Before you accept the optimization, click Preview changes. After Add to workspace, test in Preview mode, then click Submit to publish. Google says adding a destination tag automatically sends a page view, so check that each page sends one page view, not two. You can undo the changes or roll back to an earlier version.
  5. Keep legacy config support on a migrated Google tag until you're ready. Containers that were Google tags show a "Support gtag('config') initialization events" checkbox on the Initialization trigger; it only affects containers loaded through the gtag/js snippet. Unchecking it means in-page settings such as user_id, currency or linker settings (for cross-domain tracking) stop applying. Copy them into the Tag Manager UI first.
  6. Watch conversions after you publish. Google calls turning off legacy support "a measurement-affecting change" and says to compare page view and conversion volumes. Check Google Ads conversions for a few days; if they drift from GA4, see why Google Ads and GA4 show different conversions.
  7. Review access. Change permissions in the External Account Links section of the container's admin settings. Google notes permissions aren't versioned, so rolling back a version doesn't undo them.
  8. Don't add a second purchase conversion with visual tagging. If the container already measures purchases, Google warns that continuing may double count it.

Dates to watch

DateWhat happens
May 20, 2026Google first announces the merger and the visual tagging beta, according to PPC Land
July 1, 2026A streamlined Tag Manager Overview page is released
July 9, 2026The container ID, not the loading path, decides which tags a container can run
August 20, 2026The date Google's "Updates to Google tag and Google Tag Manager" article now carries
October 8, 2026gtm.js snippets start up on container load, regardless of gtag('config') commands
October 12, 2026Release note for container optimization: containers send data directly to Google destinations
Through 2026Visual tagging expands to "additional use cases throughout the year"; no dates given
No date givenGoogle says it will "soon" update gtag.js to include all of Tag Manager's capabilities

Where Tofu fits

Tofu Ads Agent (our product) includes a conversion tracking audit in its Google Search work and can set up conversion events on LinkedIn and Google for a page visit or a click. It doesn't run Tag Manager's optimization, edit your container or use visual tagging; you do those in Tag Manager. For other ways to test your setup, see tools that check whether conversion tracking works. If you'd rather have an AI assistant make the container changes, see the Google Tag Manager MCP server.

Sources

Ask Tofu next

Pick a question and Tofu Ads Agent answers it in chat.

Related answers

More on

Let an agent build your next campaign.

Tofu Ads Agent reads your CRM, plans the funnel, builds the audience and creative, and stages full campaigns across LinkedIn, Google and Meta for your approval.

Try it free Get a demo