Google Ads conversions not recording
Leads or sales are coming in, but the Google Ads conversion action shows zero conversions, or its status in Goals > Summary reads Misconfigured, Needs attention or Awaiting conversions.
Steps checked against the platforms' documentation on November 20, 2026.
Quick answer
Usually the conversion tag isn't firing on the real conversion, or fires with the wrong conversion ID or label. Hover over the action's status in Goals > Summary to read the alert, then run the action through Tag Assistant with a real test conversion. If the tag fires correctly, check the action is Primary and that you are reading the right column and date range.
1. The conversion tag is not firing on the actual conversion
The tag lives on a thank-you page that the form no longer redirects to, the GTM trigger watches a click instead of a successful submission, or the site was rebuilt and the snippet was dropped. Google's Misconfigured status means recording has stopped because of a setup error or a broken tag.
How to check
- 1In
Goals>Summary, hover over the action's status, read the alert and selectTroubleshootto openTag Assistant. Enter the landing page or home page URL, not the thank-you page, and selectConnect. - 2If the site uses Google Tag Manager, select
Debug live versionfirst, then complete a real form submission or test purchase. - 3Confirm the Google Ads conversion event appears at the moment of conversion. If it never appears, select
I thought I already triggered itto see Tag Assistant's failure reasons. - 4Check the
Tag coveragesummary in Tag Assistant for pages that are missing the Google tag entirely.
How to fix
- 1Make sure the Google tag (or GTM container) loads on every page, including the thank-you page and any page on a separate booking or checkout domain.
- 2In GTM, change the trigger to fire on the success state: a thank-you page view, a form success
dataLayerevent, or a confirmed purchase event, not the submit button click. - 3Publish, repeat the Tag Assistant test and confirm the status updates. Allow 24–48 hours for new or changed tags to show data.
2. The conversion ID or label in the tag doesn't match the conversion action
The conversion ID is unique to the Google Ads account and the conversion label is unique to each conversion action. Tags copied from another container or pointing at a removed action fire normally while sending conversions nowhere useful.
How to check
- 1In Google Ads, open
Goals>Summary, select the conversion action and open its tag setup. ChooseUse Google Tag Managerto see the exactConversion IDandConversion label. - 2In GTM Preview, select the
Google Ads Conversion Trackingtag that fired and compare both values character by character. - 3In Tag Assistant, open the conversion hit and confirm the ID/label pair it sent matches the action you are looking at in the UI.
How to fix
- 1Replace the ID and label with the values from the correct action, stored as GTM constants if reused.
- 2Pause tags still pointing at removed actions or another account, then re-test with Tag Assistant.
3. Consent settings are blocking or limiting the tag
With basic consent mode, Google tags are blocked until the visitor interacts with the banner, and no data is sent if they decline. A banner that never updates consent to granted, or a CMP that loads after the conversion tag, can make conversions look like they stopped.
How to check
- 1In Tag Assistant or GTM Preview, open the
Consentview for the conversion event and see whetherad_storageandad_user_datawere granted or denied when the tag fired. - 2In Google Ads, go to
Tools>Data Manager, open the Google tag withManage, and check whetherSet consent mode overrideis forcing denied defaults for some regions.
How to fix
- 1Make sure the consent default is set before any Google tag loads, and that the CMP sends a consent update when the visitor accepts.
- 2Decide deliberately between basic and advanced consent mode with the client's legal contact. Advanced mode lets tags load with denied defaults so Google can use an advertiser-specific model for conversion modeling.
- 3Re-test both the accept and decline paths.
4. The conversion action is set to Secondary or sits in a goal that isn't used
Only primary actions are reported in the Conversions column and used for bidding. Secondary actions are for observation and show only in All conversions. Conversions created from the Google Analytics interface are secondary by default, so a newly imported GA4 key event often looks like it isn't recording.
How to check
- 1Add the
All conversionscolumn next toConversionsin the campaign report for the same date range. If conversions appear inAll conversionsonly, the action is recording but not primary. - 2Go to
Goals>Summary, find the goal that contains the action and selectEdit goal. - 3Look at the
Conversion action optimizationsection to see whether the action isPrimaryorSecondary (observe only). - 4Check the campaign's goal settings to confirm it uses the goal (or account-default goals) that includes this action.
How to fix
- 1Set the action to
Primaryif it should drive bidding, and save. - 2Keep only one primary action per real-world conversion, or you create double counting instead.
5. You are looking at the wrong date range: conversion lag and the conversion window
Standard Google Ads reporting attributes conversions to the date of the ad interaction, not the date the conversion happened. Conversions after the click-through conversion window (30 days by default, up to 90 depending on source) are never recorded.
How to check
- 1Hover over the conversion action in
Goals>Summaryto see its conversion window and counting setting. - 2Compare
ConversionswithConversions (by conv. time)for the same period to see whether conversions exist but are dated to earlier clicks. - 3Check how long your client's leads take to convert. If many close after the window, they will never appear.
How to fix
- 1Use
Conversions (by conv. time)when matching against CRM dates. - 2Lengthen the click-through window if the sales cycle needs it. The change only applies going forward and doesn't recover conversions already missed.
- 3For long cycles that close offline, add an offline conversion import rather than relying on the website tag.
6. The click identifier is lost on the way to the conversion page
If the visitor moves to another domain for booking or checkout, or a redirect strips URL parameters, the conversion tag fires without the ad click information and Google can't attribute it.
How to check
- 1Click a test ad or add a test
gclidparameter to the landing page URL and follow the journey to the thank-you page. Watch whether the parameter or the first-party cookie survives each redirect. - 2In GTM, confirm a
Conversion Linkertag fires on all pages, including the second domain. - 3In
Tools>Data Manager> Google tagManage, checkConfigure your domainslists every domain in the journey.
How to fix
- 1Add every domain in the conversion path to
Configure your domainsso the linker carries the click across. - 2Install the same Google tag or GTM container on the third-party domain if the vendor allows it, or move the conversion to a page you control.
- 3Fix redirects that drop query parameters, then repeat the test journey.
Stop it happening again
- Test every primary conversion action in Tag Assistant after any site release, form change or CMP update, not just at launch.
- Fire conversion tags on the success state (thank-you view or success event), never on a button click.
- Keep a simple tag map per client: conversion action, ID, label, trigger, and which tag fires it.
- Check the
Goals>Summarystatus column weekly and act onNeeds attentionbefore it becomesMisconfigured. - Keep exactly one primary action per real-world conversion and document why each secondary exists.