google ads5 min readBy Phloz team

Google Ads says 'Unverified' or 'No recent conversions' — the fixes

A Google Ads conversion action stuck on Unverified, Inactive, or No recent conversions has a short list of causes — tag not firing, no conversion linker, auto-tagging off, or the wrong source double-counting. How to read the status and fix each.

TL;DR

When a Google Ads conversion action shows Unverified, Inactive, or No recent conversions, the status itself tells you which half of the problem you're in. Unverified / Inactive = Google has never recorded this conversion, so the problem is installation: the tag isn't firing, the Conversion Linker is missing, or auto-tagging is off so there's no gclid to attribute. No recent conversions = it worked before but has gone quiet, so the problem is the event: the conversion snippet stopped firing, the action got paused, or you're double-counting from two sources and cleaned one up. Below: how to read each status and the fix.


You set up a Google Ads conversion, the campaign is spending, and the conversion action sits there reading "Unverified" — or it tracked fine for months and suddenly flips to "No recent conversions." Either way the optimisation is now flying blind, because Smart Bidding can only optimise toward conversions it actually receives. The good news: Google Ads' own status labels are a decent diagnostic if you know what each one is really saying.

What the status labels mean

In Tools → Conversions, each action shows a status. The ones that matter:

  • Recording conversions — healthy.
  • No recent conversions — the tag was verified at some point but hasn't recorded a conversion in the last 7–30 days.
  • Unverified — Google has detected the tag but never received a conversion through it.
  • Inactive — no tag activity detected at all.
  • Tag inactive / needs attention — the conversion tag isn't firing on the site.

The split is simple: Inactive/Unverified is an installation problem; No recent conversions is an event problem. Diagnose accordingly.

Installation problems (Unverified / Inactive)

1. The conversion tag isn't firing

Whether you track via the Google tag (gtag), a GTM Google Ads Conversion Tracking tag, or GA4 imported conversions, something has to fire on the conversion page. Check: open the thank-you/confirmation page with Google Tag Assistant, or use the Diagnostics tab on the conversion action. If no Google Ads conversion hit fires, it isn't installed where you think. Fix: confirm the Google tag is on every page, and the conversion event (the action-specific snippet, or the GTM conversion tag) fires on the completion page — ideally on its own GTM trigger, not a guessed one.

2. The Conversion Linker is missing (the classic)

In GTM, the Conversion Linker tag is what stores the ad-click identifier (gclid) in a first-party cookie so a later conversion can be attributed to the click. Skip it and conversions fire but can't be attributed, which surfaces as Unverified or wildly under-counted conversions. Check: is there a Conversion Linker tag on All Pages in the container? Fix: add one — it's the single most common Google Ads tracking omission, and a GTM container audit will flag its absence.

3. Auto-tagging is off (no gclid at all)

Google Ads attributes conversions using the gclid appended to ad-click URLs by auto-tagging. If auto-tagging is off (or stripped by a redirect), there's no click ID to tie a conversion to. Check: Google Ads → Settings → Account settings → Auto-tagging should be on; and confirm gclid survives any redirect to your landing page. Fix: turn auto-tagging on; stop redirects from stripping the query string — the same param-loss that sends GA4 traffic to Unassigned breaks Google Ads attribution.

With Consent Mode and a default-deny, conversion pings are withheld or modeled until consent is granted. Check: accept your own banner and complete a test conversion. Fix: if intended, that's modeled conversions working as designed — just verify the consent default loads before the tag, and don't read "Unverified" as broken when it's a thin-data consent state.

Event problems (No recent conversions)

5. The conversion snippet stopped firing

A site redesign, a changed thank-you URL, a GTM trigger that no longer matches, or a removed snippet all silently stop the event. Check: complete a real conversion and watch Tag Assistant / the Diagnostics tab. Fix: repoint the trigger at the current completion page/event.

6. The action is paused, or its count setting is wrong

A conversion action can be paused, or set to the wrong count ("Every" vs "One") — for leads you usually want "One," for purchases "Every." Wrong count looks like missing or inflated conversions, not zero. Check: the action's status + count setting. Fix: set it to match the action type.

7. You changed sources and double-counted (then over-corrected)

A frequent self-inflicted one: tracking the same action with both a native Google Ads tag and a GA4 imported conversion double-counts — so someone removes one and accidentally kills the only working source. Pick one source per action: either the Google Ads tag or the GA4 import, not both. (The GA4-vs-Google-Ads conversion gap explains why the two will never match exactly even when correct.)

The five-minute diagnostic

  1. Read the status. Unverified/Inactive → installation. No recent conversions → event.
  2. Tag Assistant on the conversion page — does a Google Ads conversion hit fire?
  3. Conversion Linker on All Pages? (GTM) — add it if missing.
  4. Auto-tagging on + gclid surviving redirects?
  5. One source per action — Google Ads tag or GA4 import, never both.
  6. Count setting + paused state correct for the action type?

The pattern behind it

By now this rhymes with every other tracking post: a status label that reassures or alarms without telling you the actual cause, and a conversion path that fails silently the moment a URL or trigger changes. Google Ads won't error — it'll just spend against conversions it isn't receiving, and Smart Bidding will optimise toward the gap. The fix is the same everywhere: verify conversions on a schedule instead of trusting the dashboard, run the pre-launch QA pass before spend starts, and for high-value actions keep a server-side/offline backup so a broken browser tag isn't the only path.

That's the discipline Phloz is built around — every client's Google Ads conversions, GA4, GTM, and pixels modeled as nodes with a health state, so "is this client's Google Ads actually recording conversions?" is a thing you can see across the book, not re-check by hand each month. The tracking-infrastructure map is the surface; CRM for PPC agencies and pricing are the workflow. But start with the status label and the Conversion Linker — it's almost always the linker.