If your conversion tag fires clean in Google Tag Manager’s Preview mode, shows a green checkmark, and everything looks perfect, but Google Ads still reports zero (or almost zero) conversions from real traffic, the tag itself usually isn’t the problem. Preview mode tests whether a tag fires. It does not test whether Google Ads can actually attribute that fire to a click. Those are two different things, and the gap between them is where most “working in preview, dead in production” cases live.
The short answer: this almost always comes down to one of four causes, in order of likelihood: a missing or misconfigured Conversion Linker tag, a consent mode setup that’s silently blocking ads storage for real visitors, a tag sequencing or timing issue that only shows up under real page load conditions, or conversion thresholding hiding small volumes of real conversions from your reports. Here’s how to work through each one.
When someone clicks your ad, Google Ads appends a click identifier (the gclid parameter) to your landing page URL. The Conversion Linker tag’s job is to read that parameter and store it in a first-party cookie (commonly _gcl_aw) on your domain. When a conversion happens later, whether that’s the same session or three days later, your conversion tag reads that stored click ID back out and hands it to Google Ads so the conversion can be matched to the original ad click.
In GTM preview, you’re often testing on a single page load where the gclid is fresh in the URL, so the conversion tag can sometimes fire “successfully” even without Conversion Linker doing its job properly, especially if you’re testing the thank-you page directly rather than clicking through from an actual ad. In production, real users land on your homepage or a product page first, click around, and convert several steps and sometimes several days later. Without Conversion Linker firing on every page of that journey, the click ID is never captured or persists for a shorter window, and the conversion has nothing to attach to.
To check this: open GTM, confirm a Conversion Linker tag exists, confirm its trigger is set to All Pages (not just the confirmation page), and confirm it’s actually published, not just saved as a draft version. Then check your browser’s cookies on the live site for _gcl_aw after clicking a real (or test) ad link. If that cookie isn’t there, this is your problem.
If you’re running Google’s Consent Mode (required for advertisers with EEA/UK traffic, and increasingly used everywhere as a best practice), your conversion tags only fire at full strength when a visitor grants ad_storage and ad_user_data consent. When you test in GTM preview, it’s easy to have consent defaults set permissively in your own testing environment, or to simply click “accept” on your own cookie banner without thinking about it. Real visitors, especially in regions with strict privacy defaults, often decline or ignore the banner, which means Google Ads receives conversion pings with denied consent signals.
Denied consent doesn’t necessarily mean zero data. Google Ads uses conversion modeling to estimate conversions from consent-denied traffic, but modeled conversions are aggregated, delayed, and only kick in once you have enough data volume. If your account is smaller, you may see a real drop in reported conversions that looks like tracking is broken when it’s actually consent mode working as designed. Check your consent banner’s default state, confirm your gtag('consent', 'default', ...) configuration in GTM matches what you intend, and look at the Diagnostics tab in Google Ads under conversion actions for a specific note about consent-related conversion modeling.
GTM preview mode loads your container in a fairly controlled environment. Real pages carry other scripts: chat widgets, page builders, A/B testing tools, slow-loading fonts, and third-party plugins that can all interfere with when and whether your dataLayer events actually push. A common failure pattern: a form-submission conversion trigger depends on a dataLayer event that a form plugin pushes inconsistently, or a page redirects to the thank-you page before the tag has a chance to send its request (a “tag fires but the page unloads first” problem).
Use GTM’s Tag Sequencing feature to force Conversion Linker (or Google tag base configuration) to load before the conversion tag, and where a redirect is involved, use a trigger delay or event callback rather than a plain page-load or click trigger to give the request time to actually send before the browser navigates away. If you’re troubleshooting a form conversion specifically, check your form plugin’s actual dataLayer push in the browser console on the live site, not just in preview, since plugin updates can silently change event names or timing.
Google Ads applies data thresholds to conversion action reporting for privacy reasons, particularly at the keyword, ad group, or demographic breakdown level. If your total conversion volume for a given segment is low, Google Ads can withhold or delay showing that data in the interface even though the conversion was recorded and is being used for bidding. This shows up as “my conversions dashboard looks empty” when the tracking itself is fine. Check the Conversions summary at the account or campaign level (a higher-volume view) rather than a narrowly filtered segment before concluding anything is broken.
_gcl_aw.googleads.g.doubleclick.net or google.com/pagead when the conversion event fires, and confirm the gclid parameter is present in that request.The single most common root cause across all of this is a missing or misfiring Conversion Linker tag. If you only check one thing first, check that.
If you’ve worked through all four of these and conversions are still not showing up where they should, it’s worth having someone look at the actual GTM container and conversion setup directly rather than guessing further, since the exact fix depends on which of these (or a combination) is happening in your specific account.