Roughly 70% of "zero conversion" Google Ads accounts we audit in 2026 have a tag that never fires on the real thank-you page — not a Google reporting bug, not a budget issue, just a broken measurement chain that has been silently feeding nothing to Smart Bidding. When sales are landing in your store but the Conversions column reads a flat zero, the problem is almost never Google losing your data — it is a link in the tracking chain that snapped.
This guide walks the five places that zero out a conversion count, ordered from the fastest to confirm to the deepest, so you find the break in minutes instead of guessing. To check your account against the most common measurement failures automatically, run our free 5-axis Google Ads audit.
Updated 2026-05-06 with current conversion action, gtag, GA4 import and Consent Mode v2 behavior observed across US, UK and European accounts.
- Conversion action and tag firing explain the large majority of zeroed accounts and confirm in minutes. 2. A 'No recent conversions' status means no live source is feeding the action. 3. One source per action — native tag OR GA4 import, never neither, never both. 4. 'Consent Mode' v2 can withhold the ping entirely when ad-storage is denied. 5. 'Enhanced Conversions' with a broken field mapping can reject the whole request.
Is the conversion action set up and receiving data?
Start here because it is the fastest check and the most common cause. Open Goals then Conversions and read the status column for the action you expect to fire.
No recent conversions — The action exists but nothing has reached it in the recent window. This is the classic zero: a created action with no live source. It points downstream to the tag or import, not to the action itself.
Inactive or Unverified — The tag was never detected on your site. Google has not seen a single ping, so the action cannot record anything.
Wrong category or secondary — An action set to Secondary is still tracked but is excluded from the main Conversions column by design. If your sales action is secondary, the column reads zero even while the action records. Set the primary purchase or lead action to Primary.
Confirm the action has a sensible count setting, a value, and an attribution window (a 30-day click window is the default for most actions). A misframed window will not zero you out, but a missing source will. Our conversion tracking guide walks the full setup.
Is the tag firing (gtag/GTM) on the right trigger?
If the action exists but reads zero, the next question is whether the tag actually fires where the sale completes.
The Google tag (gtag.js) — Simple to deploy but easy to omit from one page template. A common failure: the global tag sits on every page except the dynamically rendered thank-you page, so the exact moment that matters has no tag at all.
Google Tag Manager — Centralizes tags but adds a trigger layer. The tag is present, but the trigger is wrong: it listens for a page path that the confirmation page does not match, or for a dataLayer event the checkout never pushes. The tag never fires even though it is configured.
The thank-you page — Verify the conversion fires on the real confirmation URL your customers actually reach, not a test placeholder. Single-page apps that change the URL without a full page load are a frequent culprit, because the trigger waits for a navigation that never happens.
The decisive test is a real purchase watched in 'Tag Assistant' preview, covered in section 7. If you run a complex checkout, our server-side GTM guide explains where firing can break on the way to the server container.
Is a GA4 import or duplicate action breaking counts?
Many zeroed accounts have two competing sources for one action — or, more often, zero live sources after a half-finished migration.
The half-migrated zero — You deleted the native Google Ads tag expecting a GA4 import to take over, but the import was never linked, the GA4 key event was not marked for import, or the Google Ads link broke. The action now has no source and reads zero.
The duplicate-then-dedupe trap — Less common but real: two sources feed the same event, Google deduplicates aggressively, and the column collapses rather than doubles. Pick exactly one source per action.
The unlinked property — If the GA4 property is not linked to the Google Ads account, no key event can import at all. Confirm the link is live in the GA4 admin and in the Google Ads linked-accounts panel.
The rule is simple: one live source per action, and you can see it. An imported action should read Recording conversions; a native tag should fire in 'Tag Assistant'. Our GA4 conversion import guide covers the link end to end.
Is 'Consent Mode' suppressing conversions?
Consent Mode v2 is now the most underestimated cause of zeroed counts, especially on European traffic where a consent banner gates every tag.
Default-denied that never updates — Best practice sets consent to denied by default, then updates it to granted after the user accepts. If the update call never fires — a banner bug, a missing callback — every tag stays in denied state and sends no usable ping. Counts fall toward zero.
Modeled instead of counted — When ad-storage is denied, Google may model the conversion rather than count it directly, and modeling needs enough traffic to kick in. A low-volume account can sit at zero observed conversions while waiting for a model that never reaches threshold.
The signals that must be granted — Confirm that after acceptance the 'ad_user_data' and 'ad_personalization' signals move to granted, not just 'ad_storage'. v2 requires both for ad measurement, and a banner that only flips ad-storage leaves the conversion signal incomplete.
Watch the consent state change live in 'Tag Assistant' as you accept the banner — if the state never updates, you have found the cause.
Are 'Enhanced Conversions' misconfigured?
Enhanced Conversions improve measurement by sending hashed first-party data, but a broken mapping can reject the conversion request entirely.
Wrong field selectors — In the GTM-based setup you point the tag at page elements holding the email or phone. If a selector targets the wrong element, an empty field, or a value that changes between page loads, the request can fail validation.
Unhashed or double-hashed data — The data must be normalized and SHA-256 hashed exactly once. Sending raw email, or hashing data that the tag also hashes, produces a payload Google rejects.
Diagnostics flagged red — The Enhanced Conversions diagnostics panel inside Google Ads reports issues like 'No data received' or 'Unrecognized fields'. A red status there often coincides with a zeroed count.
The fastest isolation test: temporarily disable Enhanced Conversions and complete a test purchase. If the standard conversion now records, the mapping is the culprit and you can re-enable it field by field. Our Enhanced Conversions setup guide details the correct mapping.
The zero-conversions diagnostic table
Work this table top to bottom — it is ordered by how fast each cause is to confirm and how often it is the real problem.
A conversion action can read zero for hours while everything looks configured. The only proof that the chain works is a real test purchase watched live in 'Tag Assistant', with the tag firing green and a value recorded. Reporting delays of 3 to 24 hours mean a freshly fixed tag will still show zero today — verify the fire, then wait for the count, not the other way around.
Verify end to end with 'Tag Assistant'
The single most useful check in this whole guide is a live, end-to-end test that proves the signal travels from the page to the Conversions column.
Run a real test purchase — Open 'Tag Assistant', enter your site, and complete an actual checkout or lead form. Watch the conversion tag fire on the confirmation page with the right value and currency. A fired green tag is the proof the action setup, trigger, and consent state all line up.
Confirm the click link — Verify auto-tagging is on so the GCLID rides through to the conversion, and that no redirect on the path to the thank-you page strips it. A conversion with no linked click is recorded but unattributed, and can leave the campaign column reading zero. Use our GA4 URL tester to confirm your tagging parameters survive every hop.
Wait the reporting window — Google Ads takes 3 to 24 hours to process and display a conversion, credited back to the click date within the attribution window. Do not declare a fix failed until a full day has passed with the date range covering the click.
Then prevent the repeat. Re-test the conversion after every checkout deploy, every consent-banner change, and every tag-container publish — three edits that silently break more conversion chains than anything else. To find measurement gaps automatically across the account, run the SteerAds free 5-axis audit.
Sources
Official sources consulted for this guide:
-
support.google.com — set up conversion tracking for your website
-
support.google.com — troubleshoot conversion tracking
-
developers.google.com — Tag Manager and the Google tag platform
-
support.google.com — about Enhanced Conversions
FAQ
Why is Google Ads showing zero conversions?
Zero conversions despite real sales almost always traces to one of five mechanical failures: the conversion action was never set up or its status reads 'No recent conversions', the tag does not fire because it sits on the wrong trigger or page, a GA4 import was switched off or never linked, 'Consent Mode' is blocking the tag from sending pings, or 'Enhanced Conversions' broke the request with a bad field mapping. Work them in that order — action status and tag firing explain the large majority of zeroed accounts and take under ten minutes to confirm with 'Tag Assistant'.
How do I check if my conversion tag is firing?
Open 'Tag Assistant' from inside Google Ads or tagassistant.google.com, enter your site URL, and complete a real test purchase or lead submission. On the thank-you page the conversion tag should appear as 'fired' with a green status and a recorded conversion value. If it does not fire, the trigger is wrong, the tag is missing from that page template, or a consent state is blocking it. 'Tag Assistant' shows the exact event and any blocked requests, which pinpoints the break in under five minutes without waiting for reporting delays.
Does 'Consent Mode' hide my Google Ads conversions?
It can. With 'Consent Mode' v2, if a visitor denies ad-storage consent the conversion ping is either withheld or sent without identifiers, so Google models the conversion instead of counting it directly. If your consent banner defaults everything to denied and never updates the state after acceptance, the tag never sends a usable signal and counts can fall to zero. Verify that 'update' consent calls fire after the user accepts, and that 'ad_user_data' and 'ad_personalization' are granted, not stuck on denied from the default state.
Will a GA4 import and the Google Ads tag double or cancel my counts?
Either can happen if both are misconfigured. If you import a GA4 conversion and also keep the native Google Ads tag for the same event, you can double-count. The opposite — zero — happens when you delete the native tag expecting the GA4 import to take over, but the import was never linked, the GA4 key event is not marked for import, or the Google Ads link is broken. Pick one source per action, confirm the import shows 'Recording conversions', and never leave an action with no live source feeding it.
How long before conversions appear in Google Ads after a click?
Conversions are not instant. Google Ads can take 3 to 24 hours to process and display a conversion, and the count is credited back to the click date, not the conversion date, within your attribution window — by default a 30-day click window for most actions. A purchase today may surface on yesterday's row tomorrow. Before concluding tracking is broken, wait a full day and confirm the date range covers the original click. A true zero after 24 hours with a fired tag points to setup, not delay.
Why does 'Tag Assistant' say the tag fires but Google Ads still shows zero?
A firing tag that records no conversion usually means the signal arrives but is rejected or unattributed. Common causes: the conversion has no linked click because GCLID was stripped by a redirect or a missing auto-tagging setting, the action is set to 'Secondary' so it is reported but excluded from the 'Conversions' column, the value or currency is malformed, or the import source is duplicated and deduplicated to zero. Check that auto-tagging is on, the action is 'Primary', and the GCLID survives every redirect on the path to the thank-you page.
Should I use the Google tag (gtag.js) or Google Tag Manager for conversions?
Both work; the failure modes differ. The Google tag (gtag.js) is simpler but easy to omit from a page template, so the thank-you page silently lacks it. Google Tag Manager centralizes tags but adds a trigger layer where a mismatched trigger — wrong page path, missing event, or a blocking consent template — stops the tag firing. For most accounts, GTM with a clear conversion-linker and a precise trigger is more robust, but only if you verify the trigger in preview mode before trusting the data.