Google Ads Conversions Silently Dropped: Google Tag + GTM Container for the Same Ads Account (2026)

Key takeaway

In November 2026 we installed two snippets on a landing page, as the Google Ads and Google Tag Manager setup flows asked us to: the Google tag that Google Ads hands out (now a gtm.js?id=GTM-… snippet) and our own GTM container. Both carried a Google tag for the same Google Ads account (AW-…). With both on the page, the Google Ads conversion tags inside the GTM container fired in GTM Preview but never sent a conversion request. Google Ads and GTM showed nothing wrong. Removing the standalone Google tag fixed it immediately.

If your Google Ads account shows zero conversions while leads are clearly coming in, check whether your page loads two containers that both configure the same AW- ID.

1. The setup that triggered it

This is what we did in November 2026 for a new single-page lead-generation site.

Step 1: Google Ads, new website conversion action

The flow asked us to install the Google tag. It now comes in the new single-block format and loads a GTM- ID:

<script async src="https://www.googletagmanager.com/gtm.js?id=GTM-AAAAAAA"></script>
<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('js', new Date());
</script>

That container contained only a Google tag with destination AW-1234567890. Skipping it left the setup flagged in red.

Step 2: Google Tag Manager

We chose the GTM method, created our own web container GTM-BBBBBBB, and installed its snippet as well (same new single-block format). GTM's install check did not recognize the first snippet as its own container. It is not one; only the prefix is shared. So both snippets were needed to get past the setup checks.

Step 3: Inside the GTM container

Inside GTM-BBBBBBB we had three Custom Event triggers (a form-submission event generate_lead plus two contact-click events) and three Google Ads Conversion Tracking tags with conversion ID 1234567890 and their own labels. GTM also created a Google tag for AW-1234567890 firing on Initialization – All Pages.

Final page head

<script async src="https://www.googletagmanager.com/gtm.js?id=GTM-AAAAAAA"></script> <!-- Google tag from Google Ads -->
<script>…gtag('js', new Date());</script>
<script async src="https://www.googletagmanager.com/gtm.js?id=GTM-BBBBBBB"></script> <!-- our GTM container -->
<script>…gtag('js', new Date());</script>

2. Symptoms

Every built-in check looked fine. Only the browser's network log showed the problem.

3. How we reproduced it

We served the same head on localhost, opened it with a test gclid (?gclid=TeSt_…), pushed the event manually and listed the requests sent to Google afterwards.

Page head _gcl_aw cookie Page-load requests for AW-1234567890 Conversion request after dataLayer.push({event:'generate_lead'})
Google tag snippet + GTM container (production setup) written sent (ccm/collect … en=page_view, rmkt/collect, viewthroughconversion … en=gtag.config) none (reproduced twice)
GTM container only written sent sent: googleadservices.com/pagead/conversion/1234567890/?…&label=<lead label>&gclaw=TeSt_…
Production page after removing the Google tag snippet written sent sent for all three events, each with its own label and gclaw

In the failing case GTM itself was fine: google_tag_manager['GTM-BBBBBBB'].dataLayer.get('event') returned generate_lead, so the container received and processed the event. The conversion hit was simply never transmitted.

Environment: Chromium-based browser, November 2026, Google tag runtime reported as gtm=45He6bb1… in the request parameters. Both containers were published with no pending changes.

Reproduce it on your own setup

  1. Make two test pages. Page A has the full head shown above: the Google tag snippet from Google Ads followed by your GTM container. Page B has your GTM container snippet only. The GTM container must contain a Google tag for the same AW- ID and a Google Ads Conversion Tracking tag on a Custom Event trigger.
  2. Serve the pages over HTTP on localhost. Cookies do not work on file://.
  3. Open each page with a fake click ID, for example ?gclid=TeSt_repro_a and ?gclid=TeSt_repro_b, and wait a few seconds for the containers to load.
  4. Run the console check below on each page and compare the results.

Ready-made versions of both test pages, with a button that runs the check, are in the repro folder of the GitHub repository. Replace the two placeholder IDs before use.

In our case page A reported NO conversion request sent and page B reported a conversion request with the lead label and gclaw=TeSt_repro_b.

Console check

Run this in DevTools on the page after it has fully loaded. Replace the event name with yours. It sends a real conversion hit. Open the page without a real gclid, or with a fake one, so the hit cannot be attributed to an ad click.

(() => {
  const t0 = performance.now();
  dataLayer.push({ event: 'generate_lead' });
  setTimeout(() => {
    const labels = performance.getEntriesByType('resource')
      .filter(r => r.startTime > t0 && r.name.includes('/pagead/conversion/'))
      .map(r => new URL(r.name).searchParams.get('label'));
    console.log(labels.length
      ? 'Conversion request sent, label(s): ' + labels.join(', ')
      : 'NO conversion request sent');
  }, 5000);
})();

Or filter the Network panel for pagead/conversion and trigger the event yourself.

4. Why the built-in checks missed it

5. Likely cause (our interpretation, not confirmed by Google)

Both containers configure a Google tag for the same destination, and both carried "ignoreDupeGtagConfigCalls": true for it in the published container JSON. Our reading: the container that loads first takes over AW-1234567890, and the conversion tags in the second container hand their event to a destination they do not control, so nothing is sent.

The timing fits the GTM release notes:

Google's Google tag management help page also warns that if the same Google tag is configured two or more times on a page, "it may cause duplicate data or mixed settings". It does not mention conversions being dropped, and none of the release notes mention this interaction.

6. What we did not test

7. The fix

Keep one owner per Google Ads account on the page.

After the fix, conversions are sent with the right label and gclaw. Conversions lost before the fix cannot be recovered: an offline upload needs either the gclid or user-provided data that a tag captured at submission time, and neither existed.

8. Takeaways

  1. Verify conversion tracking by the conversion request, not by GTM Preview, Ads diagnostics or the conversion status.
  2. With the 2026 snippets, a Google tag and a GTM container look the same (gtm.js?id=GTM-…). List every gtm.js ID on the page and check which AW- / G- destinations each one configures.
  3. Any page that loads two containers for the same AW- ID is a candidate for this problem.

9. Side note: enhanced conversions in this setup

On the GTM-only page we also tried sending user data purely from page code with gtag('set', 'user_data', { email: … }) before pushing the event. The conversion request switched to ec_mode=c, but em stayed tv.1~ec.e3 with no hash, so the data was not attached. With GTM, configure user-provided data in the container (CSS selectors or a code/data-layer variable) and verify that em carries a hash.

10. FAQ

Why does GTM Preview show my Google Ads conversion tag as Fired when no conversion is recorded?

Fired means GTM executed the tag. It does not mean a request left the browser. In our case the page loaded two containers that both configured a Google tag for the same AW- ID, and the conversion request was never sent. Check the Network panel for a request to pagead/conversion with your label.

Do I need both the Google tag snippet from Google Ads and my GTM container?

No. If you use GTM, install only your GTM container and keep the Google tag for the AW- ID inside it. Do not add the separate Google tag snippet from Google Ads, even if the setup flow flags it.

How do I check that a Google Ads conversion is really being sent?

Open the page with a fake gclid, trigger the conversion event, and look for a request to googleadservices.com/pagead/conversion/<conversion ID>/ that carries your conversion label and a gclaw parameter. The console check in this article does this automatically.

Can conversions lost to this conflict be recovered?

No. An offline upload needs either the gclid or user-provided data that a tag captured at submission time. In our case neither existed, so the conversions lost before the fix could not be restored.

Is the conflict between the Google tag and a GTM container confirmed by Google?

No. The cause described here is our interpretation of a controlled test in November 2026. Google's help page on Google tag management warns that configuring the same Google tag two or more times may cause duplicate data or mixed settings, but it does not mention conversions being dropped.

References

All IDs, labels and domains in this write-up are placeholders.