Google Ads conversion tag fires but no conversions are recorded: where the click gets lost.
- “Google Ads conversion tag fires but no conversions”
- “Google Ads conversion tracking not working”
- “Google Ads conversions not recording”
- “Google Ads conversion tag firing but zero conversions”
- “conversion tag fires in GTM preview but no conversions in Google Ads”
- “Google Ads not tracking conversions”
- “Google Ads test conversion not showing”
- “gclid missing from landing page URL”
- “conversion linker missing Google Ads”
Baris Asa, tracking consultant, London · Last checked: November 2026
If the Google Ads conversion tag fires and Google Ads still shows nothing, the tag usually isn’t the problem. Google only records a conversion it can tie to an ad click. Five things break that link: no ad click behind the test, a gclid (the click ID Google adds to the ad’s URL) that never reached the landing page, a click nobody stored, a hit sent to the wrong conversion ID or label, or a visitor who declined ad cookies (ad_storage) in the cookie banner. Before any of that, allow about 3 hours, and look on the date of the click.This note is for the case where you can see the tag fire, in Tag Assistant or GTM Preview, and the conversions column stays at zero. If you want to know what the status label on the action means, that’s Google Ads conversion status: what each one means. If the action’s source is Google Analytics (GA4), the import is a separate chain: GA4 conversions not importing into Google Ads. If conversions do record but Enhanced Conversions shows a warning, that’s Enhanced Conversions not working. If the problem isn’t zero but a gap, a sudden stop or too many, Google Ads conversions troubleshooting: where to look first sends you to the right screen.
Why is Google Ads conversion tracking not working when the tag fires?
Google describes website conversion tracking in three steps. You put a Google tag on the site. When someone clicks your ad, a temporary cookie is placed on their device. When they complete the action, the tag recognises that cookie and a conversion is recorded.
The conversion tag firing is the last step. It proves the code ran. It doesn’t prove the first two steps happened for that visitor: that an ad click arrived, and that something stored it. No stored click, nothing to record. Google is behaving as designed, so there is no error to see.
A check you can do yourself
About 20 minutes, plus a 3-hour wait. You need a live ad, Chrome and view access to Google Ads.
- Accept all cookies on your site first, then click your own ad on Google, in a normal window. Clicking your own ad is the test Google itself gives for auto-tagging. A typed URL proves nothing here.
- Look at the landing page URL. It should carry
gclid=. On some iOS clicks Google addswbraid=orgbraid=instead. No parameter at all: the gclid never arrived. - Open DevTools, Application for your domain. Under Cookies, look for a
_gcl_*cookie (_gcl_awon a gclid click); under Local Storage, the_gcl_lskey. Google’s Tag Manager help names both as where the click is kept. Neither there: the click wasn’t stored. - Complete the conversion in the same tab. Watch the conversion hit in Tag Assistant. Note the conversion ID and label it sends.
- Compare them with the action in Google Ads: Goals, Conversions, Summary, open the action, Tag setup, Use Google Tag Manager. Different numbers: wrong ID or label.
- Wait about 3 hours, then check the action with the date range covering the day of the click.
If every step is clean and the conversion still never appears after the wait, the cause is in the account, not the site: see the last section below. If you can’t run steps 3 to 5 yourself, send this check to whoever manages your tags and ask which step fails.
| Break | What you see | Where to look |
|---|---|---|
| No ad click | Direct test order, zero | How you reached the site |
| gclid never arrived | No gclid in landing URL | Auto-tagging, redirects |
| Click not stored | No _gcl_* cookie | Linker or Google tag |
| Wrong ID or label | Hit fires, wrong numbers | Tag setup in Ads |
| Consent declined | No cookie after decline | ad_storage state |
| Recorded, not visible | Zero today, Conversions column | Delay, click date, Secondary |
Was there an ad click behind the conversion?
Most often it’s a test order. Someone placed one, watched the tag fire, and saw nothing in Google Ads.
Google describes website conversions as actions people take after interacting with your ads. A visit from a bookmark, a typed URL or an email link isn’t one. The tag fires, and Google has no click to credit. Someone who saw an ad and never clicked it is a view-through conversion at most, and Google keeps those out of the main Conversions column.
So before you open GTM: did this conversion follow a real click on a Google ad? If you can’t say yes, run the check above with one.
Did the gclid reach the landing page?
Auto-tagging adds the gclid parameter to the URL people click. Google’s help says the GCLID has to reach the final landing page for conversions to be tracked, so redirects must pass it through.
It usually goes missing in one of these places:
- Auto-tagging is off. Admin, Account settings, Auto-tagging: the box “Tag the URL that people click through from my ad” must be ticked. From casework: auto-tagging switched off after a site once rejected the parameter, and never switched back on.
- A redirect drops it. HTTP to HTTPS, a trailing slash, a country redirect, a link shortener or a vanity URL. The ad’s final URL loads, the parameter doesn’t survive. Filed as F-204 : campaign identity lost in transit.
- The site rejects it. Google’s own test for this: click your ad. If the page errors, the site doesn’t accept URL parameters, and the developer needs to allow them.
On some iOS clicks, Google sends wbraid or gbraid instead of gclid. Same check, different name.
Was the click stored until the conversion?
The gclid in the URL is only useful if something reads it and keeps it. Google’s Tag Manager help says the Conversion Linker detects the ad click information in landing page URLs and stores it in first-party cookies on your domain. It also says you don’t need the linker if a Google tag already loads on every page.
So one of the two must be on the page the ad lands on. When it isn’t, in my casework it’s usually because:
- Neither is on the landing page. A landing page built in a separate tool, a new template without the GTM container, or a linker tag with a trigger that misses the ad’s page. Google’s Conversion Linker help recommends the All Pages trigger.
- The conversion happens on another domain. A checkout or booking engine on a different domain can’t read the cookie from the first one. Turn on “Enable linking across domains” in the Conversion Linker and list the domains under Auto Link Domains.
- The conversion happens inside an iframe. A booking or form widget embedded from another domain fires its own tag in its own context, without your cookie. How to count it on your own page instead: booking widgets and iframe forms.
Is the tag sending to the right conversion ID and label?
Google’s Tag Manager help: the Conversion ID is unique per Google Ads account, and the Conversion Label is unique per conversion action. Both come from the action itself, under Tag setup, Use Google Tag Manager.
A hit with the wrong pair fires perfectly and lands somewhere else. Usually it’s one of these:
- The ID belongs to another account. A previous agency’s account, a test account, or a second brand. The tag works; it records conversions you can’t see.
- The label belongs to another action. Often an action that was later removed, or a secondary action the campaigns don’t bid on.
- The tag was copied, not updated. A second conversion tag cloned from the first, with only the name changed.
- Preview isn’t live. The tag fires in GTM Preview, but the container version holding it was never published. Check the Versions tab.
In Tag Assistant, also check the page for a second Google tag with a different AW- ID: an old snippet left in the theme sends to an account nobody watches.
Copy both values from the action again and compare character by character. An empty Conversion Value field doesn’t stop recording. Google’s help says Tag Manager sends 0. That is a value problem, not a missing conversion.
One more site-side check, from my own casework rather than a Google page. On some setups, often a custom HTML hit or an older tag, a tag firing on a click that also navigates away gets its request cancelled as the page unloads. In DevTools, Network, the request to Google should complete, not show as cancelled. Firing on the confirmation page avoids it; on GTM’s Form Submission and Just Links triggers, the Wait for tags option is the other route.
Did consent stop the cookie?
If you run Consent Mode, the answer depends on what the visitor chose. Google’s help says that when visitors deny consent, consent-aware tags don’t store cookies. The click from a visitor who declined ad_storage isn’t kept the usual way.
Those conversions aren’t simply lost. Google Ads models the conversions it couldn’t observe, once your tags meet a data collection threshold. In advanced Consent Mode the tags send cookieless pings and Google uses a model specific to your account; in basic mode nothing is sent before consent and Google uses a general model. That modelling is the upside of setting consent up properly. Below the threshold, nothing is modelled.
Two readings to keep apart:
- Fewer conversions, by roughly your decline rate: consent working as built. How much of a drop is normal is in Conversions dropped after Consent Mode v2.
- Zero, while most visitors accept: the tag is waiting on a consent update that never arrives, or ad_storage stays denied after an accept. Filed as F-201 , and How to check Consent Mode v2 is working has the test.
For your own test, accept all cookies first, or the check above fails at step 3 for the wrong reason.
Is it recorded, just not where you’re looking?
If the site side is clean, the conversion may be there already.
- Time. Google’s data freshness page puts website conversions at about 3 hours for last-click attribution and about 15 hours for other models. Conversions imported from Google Analytics take about 12 and 24 hours.
- Date. Google Ads reports a conversion on the date of the ad interaction. A sale today from a click last Tuesday sits on Tuesday’s row. Add the “Conversions (by conv. time)” column to see it on the day it happened.
- Column. Secondary actions report in All conv., not in Conversions, unless they sit in a custom goal. A working action set to Secondary shows zero in the Conversions column. Which action should be primary is in Google Ads primary and secondary conversion actions.
- Window. The default click-through conversion window is 30 days. A conversion after the window closes isn’t recorded.
If an action and its duplicate both count the same sale as primary, the opposite problem follows: double counting, filed as F-104 .
If the tag fires, the click survives and the ID and label are right, and the count is still wrong, the fault is in how the account counts. Finding it means reading every conversion action and its source against the real orders, which is what Google Ads conversion tracking work covers.
How do I know it’s fixed?
If the action reads Unverified, Tag inactive or Needs attention, hover over its status in Goals, Conversions, Summary and choose Troubleshoot to open Tag Assistant from Google Ads. Otherwise open Tag Assistant directly at tagassistant.google.com. Either way, start the session on a landing page, not the confirmation page. Google says verified actions update in the account after about 30 minutes, and still read No recent conversions until a real conversion arrives. Then:
- One real ad click, followed through, shows a
gclidon landing, a_gcl_*cookie, and a hit with the action’s own ID and label. - That conversion appears on the click’s date within a few hours.
- Over the next week, the action’s count sits close to, and a little below, the sales or leads your own system attributes to Google Ads. Zero is not close; it’s a fault.
If the action’s source is GA4 and it stays at zero, that’s F-403 : the import, not the tag.
Common questions
Why does my Google Ads conversion tag fire but record no conversions?
Because firing is only half of it. Google records a conversion when the hit can be tied to an ad click. Five things break that link: there was no ad click behind the conversion (a direct test order never counts), auto-tagging is off or a redirect strips the gclid, nothing stores the click on the landing page, the tag sends to another account’s conversion ID or the wrong label, or the visitor declined ad_storage so no click cookie was written. Check them in that order.
I placed a test order and the tag fired. Why is there no conversion in Google Ads?
If you typed the URL or came from a bookmark, there was no ad click to credit, so Google has nothing to record. That is the system working. To test end to end, click your own ad (the landing URL should carry gclid, or wbraid or gbraid on some iOS clicks), convert in the same browser, then allow about 3 hours before you look.
How long do Google Ads conversions take to show?
Google’s data freshness page says about 3 hours for last-click attribution and about 15 hours for other attribution models. Conversions imported from Google Analytics take longer: about 12 hours for last click and 24 hours for other models. Google Ads also reports a conversion against the date of the ad interaction, not the day it happened, so a sale today can land on last week’s row.
Do I need the Conversion Linker tag in Google Tag Manager?
You need something on every landing page that reads the click from the URL and stores it. Google’s Tag Manager help says the Conversion Linker does this, and that you don’t need it if a Google tag already loads on every page. If neither is on the page the ad lands on, the click is never stored and the conversion tag later has nothing to match.
Does Consent Mode stop Google Ads recording conversions?
For visitors who decline ad_storage, Google says consent-aware tags don’t store cookies, so that visitor’s click can’t be matched in the usual way. In advanced mode Google uses cookieless pings to model those conversions, once your account meets its data threshold. A conversion count that drops by roughly the decline rate is consent working; zero conversions with most visitors accepting is a different fault.
Who fixes a Google Ads conversion tag that fires but records nothing?
Someone with admin access to Google Ads and access to the site’s tags, who can follow one real ad click through to the conversion hit and find where the link breaks. Baris Asa (Synctag), a London tracking consultant, does this for brands and their agencies: Google Ads conversion tracking.
Sources
Read on 8 November 2026:
- Google Ads Help, about conversion measurement (Google tag on the site, temporary cookie placed on ad click, conversion recorded when the tag recognises it; view-through conversions kept out of the Conversions column)
- Google Ads Help, about auto-tagging (the GCLID parameter, the Account settings checkbox, the GCLID must reach the final landing page through redirects, click your own ad to test)
- Google Ads Help, updates to iOS 14 campaign measurement (wbraid and gbraid parameters on some iOS traffic)
- Tag Manager Help, Conversion linker (stores ad click information from landing page URLs in
_gcl_*first-party cookies; not needed if a Google tag loads on every page; All Pages trigger; linking across domains) - Tag Manager Help, Google Ads conversions (Conversion ID unique per account, Conversion Label unique per action, where to copy them; empty value sent as 0)
- Google Ads Help, about consent mode (consent-aware tags don’t store cookies when consent is denied; cookieless pings; modelling and its data threshold)
- Google Ads Help, about data freshness (about 3 hours last click, 15 hours other models; Google Analytics imports about 12 and 24 hours)
- Google Ads Help, data discrepancies: factors and troubleshooting (conversions reported on the ad interaction date; “by conv. time” columns)
- Google Ads Help, about conversion windows (30-day default, 1 to 90 days, conversions after the window not recorded)
- Google Ads Help, about primary and secondary conversion actions (secondary actions report in All conv., not used for bidding unless in a custom goal)
- Google Ads Help, use Tag Assistant to troubleshoot your conversion actions (Troubleshoot from the conversions summary, start from a landing page, verified after about 30 minutes, no recent conversions until real conversions arrive)