Google Ads Conversions Not Recording? Causes and Fixes

Quick fix: Check the conversion action's status and wait at least 3 hours after a test, because Google Ads data is not instant. If conversions are still missing, confirm the conversion tag fires on the thank-you page with the right ID and label, and make sure the gclid parameter survives every redirect between the ad click and your landing page.
You set up a conversion action, sales are coming in, and Google Ads shows zero. Or conversions recorded fine for months and then stopped. Either way, Smart Bidding is now optimizing blind, so this is worth fixing quickly.
Google Ads conversion tracking depends on a chain: the ad click adds a click ID, your site stores it, the conversion tag reads it, and Google matches the conversion back to the click. A break anywhere in that chain looks the same in your account. The steps below check each link, starting with the most common failures.
Step 1: Read the conversion action status
Go to Goals > Conversions > Summary and look at the status column. Google's status troubleshooting page describes these overview statuses:
| Status | What it means |
|---|---|
| Active | The conversion action is working as intended. |
| Needs attention | It still records conversions, but there are issues to fix. Hover over the status for next steps. |
| Misconfigured | Conversions have stopped recording because of a setup error or broken tag. |
| Awaiting conversions | No conversions in the last 7 days. Common reasons are an action created less than 48 hours ago, paused campaigns, or low traffic. |
| Removed | The action was deleted or archived and no longer tracks data. |
You may also see older or more detailed labels such as Unverified, which means Google has not yet confirmed the tag on your site, or No recent conversions, which means the tag was seen but nothing was recorded in the last 7 days. Open the conversion action and check its Diagnostics tab for the specific issue Google detected.
The status tells you where to look. "Awaiting conversions" on a new action usually means wait. "Misconfigured" means the tag or setup is broken, so go to step 3.
Step 2: Rule out reporting delays and date attribution
Google's data freshness page lists a delay of about 3 hours for Google Ads conversion tracking data with last-click attribution, and about 15 hours with other attribution models. Conversions imported from Google Analytics take longer, around 12 hours for last click and 24 hours for other models.
There is a second trap. The standard Conversions column credits a conversion to the date of the ad click, not the date of the sale. If someone clicked last week and bought today, today's report will not show it. Add the Conversions (by conv. time) column to see conversions on the day they actually happened, which is much easier to compare against your order system.
Also check that the conversion action is set as a primary action. Secondary actions are tracked for reporting in the All conv. column but do not appear in the main Conversions column, which can make a working action look empty.
Step 3: Confirm the conversion tag fires with the right ID and label
Complete a real or test conversion with your browser's developer tools open on the Network tab. On the thank-you page, look for a request to Google Ads conversion endpoints (filter for conversion or googleadservices). The request should contain your AW- conversion ID and the conversion label from the action's tag setup.
Common failures at this stage:
- Wrong label. The tag uses a label from an old or deleted conversion action.
- Wrong page. The trigger fires on a URL that changed, such as
/thank-youbecoming/order-confirmation. - The page never loads. Some checkouts and payment providers finish on their own domain or skip the confirmation page for certain payment methods.
- Tag inside an iframe. Google's sitewide tagging troubleshooting page recommends against placing tags in iframes, which is common with embedded forms and booking widgets.
If you use Google Tag Manager and the tag does not fire, debug the trigger in Preview mode. Our GTM Preview troubleshooting guide helps if Preview will not connect. The Pixel Helper extension is another quick way to see which tags fire on the confirmation page.
Step 4: Make sure the GCLID survives the journey
This is the most common reason tags fire but conversions still do not record. With auto-tagging on, Google adds a gclid parameter to your landing page URL. Your site must store that click information in first-party cookies so it can be read at conversion time.
Check each of these:
- Auto-tagging is on. Check it in your Google Ads account settings. Without it, no
gclidis added. - Redirects keep the parameter. Redirects from
httptohttps, from a bare domain towww, from country selectors, or through click trackers can drop query strings. Google specifically warns that server-side redirects stripping the GCLID break measurement. - The click is stored. In GTM setups, the conversion linker tag stores ad click information in first-party cookies named
_gcl_*, such as_gcl_aw. Google's conversion linker documentation recommends the All Pages trigger, and notes that a container loading a Google tag on every page does not also need a separate conversion linker tag. - Cookies are not deleted. Some sites clear cookies on login, logout, or checkout. The click data must still be present when the visitor converts.
- Cross-domain journeys are linked. If the visitor lands on one domain and converts on another, you need cross-domain measurement configured, or the click ID will not travel with them.
To test redirects, take your landing page URL, add ?gclid=test123, and open it. If the final URL in the address bar no longer contains the parameter, a redirect is dropping it. Then check under the Application tab of developer tools whether a _gcl_aw cookie was set for your domain.
Step 5: Check consent settings
If your site uses a consent banner with Google consent mode, the consent state directly affects conversion tracking:
ad_storagecontrols whether advertising cookies, including the click information, can be stored.ad_user_datacontrols whether user data can be sent to Google for advertising. Google's documentation describes it as required for measurement uses such as tag-based conversion tracking and enhanced conversions.
With basic consent mode, tags do not load until the visitor responds to the banner. With advanced consent mode, tags send cookieless pings when consent is denied, and Google may model some of the missing conversions. Either way, visitors who decline will not be measured the same way as visitors who accept, so some gap is normal.
What is not normal is zero conversions even from visitors who accept. That usually means the consent update never reaches Google tags. Our Consent Mode v2 verification guide walks through checking defaults and updates in Tag Assistant.
Step 6: Review enhanced conversions
Enhanced conversions add hashed first-party data, such as an email address, to your conversion tag to improve matching. They supplement your existing tag rather than replace it, so they cannot fix a tag that never fires.
If you turned them on and see warnings in Diagnostics, check that the email or phone value actually exists on the conversion page when the tag fires. A common mistake is reading the email from a form field on a page the visitor has already left. Per Google's guidance, when enhanced conversions data is sent you should see an em parameter with a hashed value in the conversion request.
Step 7: Look for legacy or duplicate tags
Old conversion snippets left in the theme can send conversions to deleted actions or cause double counting in active ones. Google's troubleshooting guidance recommends removing legacy tags from converting pages. Our guide to duplicate gtag.js and GTM tags shows how to find every copy.
How to verify the fix
- In Tag Assistant, connect to your site with a test URL containing
?gclid=test123, then complete a conversion. Confirm the Google tag loads on the landing page and the conversion event fires on the thank-you page. - Confirm the
_gcl_awcookie exists for your domain before the conversion happens. - Check the conversion action's Diagnostics tab over the next few days. It reflects real traffic, so give it time.
- After at least a day of real ad traffic, compare Conversions (by conv. time) against your orders or leads from ad-driven sessions.
A test with a made-up gclid will not create a real conversion in your account. It only proves that the parameter survives redirects and that the cookie and tag work. Real conversions come from real ad clicks.
FAQ
How long should I wait before deciding tracking is broken?
Wait at least 3 hours for last-click data and up to about 15 hours for other attribution models. A new conversion action can show "Awaiting conversions" for up to 48 hours. If real ad-driven sales happen and nothing appears after a full day, start debugging.
Why do Google Ads conversions not match my store orders?
Google Ads only counts conversions it can attribute to an ad interaction, credits them to the click date by default, and may exclude visitors who declined consent. Your store counts every order. Compare using the "by conv. time" column and expect a gap.
Do I need the conversion linker if I use the Google tag?
According to Google's Tag Manager documentation, a container that loads a Google tag on every page does not also need a conversion linker tag. If your setup does not load a Google tag on every page, add a conversion linker on all pages.
Can I test by clicking my own ad?
You can, but it costs money and adds noise to your data. Testing redirects with a manual gclid parameter and checking the tag in Tag Assistant usually finds the problem without spending on clicks.


