Google Ads Conversion Tracking Not Working? Fix It (2026)

Bottom line first: when Google Ads shows "clicks but no conversions" or numbers that don't match, nine times out of ten one of six links in the chain is broken — not your ads or landing page suddenly going bad. Conversion tracking is a series circuit; loosen any link and the whole thing reads nothing. This is a work-it-in-order checklist, from "is the tag actually installed and firing" through attribution windows — no skipping steps.

For the full systematic setup (why tracking decides everything, the four-layer architecture), see Google Ads conversion tracking and GA4 setup. This piece is purely "it's broken — how do I fix it."

The seller's classic scenario: "clicks come in, but the dashboard reports zero conversions"

This is the most common error picture: ads are spending, clicks climbing, but the Google Ads conversions column stays at 0 or far below your real backend orders. Don't blame the product yet — walk the order below, and you'll likely find the cause in steps 1–3.

One key precondition to remember: a conversion is only recorded if there's an "ad click" before the "conversion action." Opening your purchase-confirmation page yourself to test does not count (no gclid). To test, click one of your own ads first (carrying the gclid), then complete the conversion.

Step 1: is the tag actually installed and firing?

The most common — and most skipped — step. Don't assume "installed equals running."

• Use Google Tag Assistant on your purchase-confirmation page (arriving via a real/simulated ad click) and confirm the Google Ads conversion tag fires once and only once, with the right conversion ID, label and value.
• The tag firing on the wrong page is common too — e.g. bound to all pages or the add-to-cart button instead of the purchase page.
• A recent site redesign / theme swap / new checkout flow easily drops the tag. Match the "day conversions stopped" in your campaign report against your GTM version history to see what was published that day.

If the tag doesn't fire at all here, stop reading further and fix this first.

Step 2: is the GA4 link / import broken?

If you import GA4's purchase event into Google Ads as a conversion (rather than using the native Google Ads tag), confirm:

• The GA4-to-Google-Ads account link still exists (it can break on permission changes).
• The GA4 purchase event carries value and currency — without an amount, Target ROAS is blind, and PMax will judge the campaign worthless and throttle it (directly related to PMax not spending budget).
• The imported conversion's status in Google Ads is "recording conversions," not "unverified / no recent conversions."
• GA4 updated in April 2026, changing how it passes hashed user data back for enhanced conversions. If your setup predates the update, it may now "throw no error but report wrong data" and need re-verifying (as of mid-2026 — confirm in the GA4 dashboard).

Step 3: are enhanced conversions silently failing?

Enhanced conversions recover conversions lost to cookie loss / cross-device, but they're the link most likely to break silently without an error.

• Check the enhanced conversions diagnostic status in your Google Ads conversion actions for "no data received" or configuration warnings.
• They depend on hashed first-party data (email/phone) being passed correctly, and on consent mode allowing it through (see Step 4). Miss either and enhanced conversions silently zero out.

Step 4: is Consent Mode v2 blocking data at the door?

This is 2026's most hidden killer, especially for EU (EEA) / UK traffic. Consent Mode v2 manages several consent states; the most common mistake:

• Many map only the "Marketing" category in the consent platform to ad_storage, omitting ad_user_data and ad_personalization — the two states added in v2.
• The result: enhanced conversions, even basic conversion modeling, silently fail — no error, but data never passes. You think it's running; it isn't.

Fix: confirm both new states are wired correctly together, and test the data flow under both "reject cookies" and "accept cookies." For exact syntax and per-CMP integration, rely on Google's official docs (the mechanics are still evolving as of mid-2026).

Step 5: duplicate counting and dedup (numbers match but doubled)

If your problem is "conversions doubled / inflated" rather than "no conversions," it's usually duplicate counting:

• The same conversion tag installed twice (once in GTM, once in page code). Use Tag Assistant to see whether it fires twice.
• The conversion Count setting is wrong — an ecommerce purchase should count "Every" (every order counts), while things like "form submit / signup" should count "One." Reversed, this inflates or deflates your data.
• Cross-account / cross-pixel duplication — a GA4-imported purchase and a native Google Ads tag both recording the same order is double-counting. Keep only one conversion action counted in the "Conversions" column per event; set the rest to observation-only.

Step 6: attribution windows and processing delay (probably not broken)

If you reach this step and numbers still don't match, don't change anything yet — it may not be broken at all:

• Processing delay — conversions aren't real-time; wait 24–72 hours after completion before trusting the report.
• Different attribution windows — Google Ads' default click-through window is commonly 30 days, view-through 1 day; comparing that to your backend's "same-day orders" naturally won't match.
• Cross-channel attribution differences — GA4 and Google Ads use different models, so numbers won't be identical, and that's normal. Use GA4 to cross-check across channels rather than demanding the two match to the unit.

A work-it-in-order table

After the fix: remember it feeds the whole account

Once tracking is accurate again, everything downstream flows: smart bidding learns accurately, PMax stops throttling itself for lack of signal, and you can see which search terms truly convert (serving Search ads and keyword strategy). Tracking is the foundation; only with it solid can anything above be optimized — exactly what the complete Google Ads guide for ecommerce keeps stressing.

Bottom line

"Conversion tracking not working" isn't black magic — it's a six-link chain: tag firing → GA4 link/import → enhanced conversions → Consent Mode v2 → dedup → attribution window. Work it in order and nine times out of ten you'll locate it in the first three steps. The two deadliest silent killers are "the tag dropped during a site redesign" and "consent mode missing ad_user_data / ad_personalization." Verify all exact syntax, numbers, and 2026 GA4 / consent-mode changes in the Google Ads / GA4 dashboards and official docs.

Frequently asked questions

Why do I get lots of clicks but the dashboard reports zero conversions? Work it in order: first confirm with Tag Assistant that the conversion tag actually fires on the purchase-confirmation page (and that you tested by first clicking an ad carrying a gclid); then check the GA4 link and enhanced-conversions diagnostics. Nine times out of ten it's "tag not firing" or "tag dropped during a site redesign."

Google Ads conversions don't match my backend orders — is that normal? Some gap is normal — different attribution windows, a 24–72 hour processing delay, and different GA4 vs Google Ads models. But an order-of-magnitude gap means real data leakage; triage with steps 1–5.

Conversions suddenly dropped to zero from a certain day — where do I look? Check changes around that day: what was published in GTM version history, whether the site was redesigned/re-themed, whether consent-mode config changed. The "date conversions stopped" in your campaign report is your best clue.

Do I need Consent Mode v2 even for US-only? Not mandatory, but configuring it correctly is recommended — it makes tracking more robust; for EU/UK traffic it's a hard requirement, and missing ad_user_data / ad_personalization silently breaks enhanced conversions.

My conversions doubled — how do I fix it? Usually duplicate counting: the same tag installed twice, GA4-import and native tag both counting, or a wrong purchase count setting. Use Tag Assistant to check for double firing and ensure only one conversion action per event counts toward the "Conversions" column.