First, confirm conversions are really missing
Three reading errors produce false alarms. First, Google Ads reports conversions against the day of the click by default, so a conversion that happens today after a click last week is filed under last week; recent days fill in gradually, and imported conversions arrive later still. Second, a conversion action can be secondary and therefore absent from the main conversions column while still recording in "all conversions". Third, the date range may simply cover a period before the tag existed.
So begin in the conversions summary. Read each action's status, which the help centre documents as showing whether the tag has been detected and recording. Then add the conversions by conversion time column, and compare the business's own records for the same days: orders in the shop system, leads in the CRM. If those records show activity and Google Ads does not, the gap is real. If the numbers exist but differ from GA4, the Google Ads and GA4 reconciliation guide explains why; this page is for counts that are absent.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Action status shows unverified or inactive | Google tag diagnostics; page source or preview on the success page | Conversion tag missing, not firing or on the wrong page | Place the event snippet or tag on the true success step |
| Tag works in preview but not on the live site | Tag Manager workspace versus published version; trigger conditions | Trigger wrong or container version not published | Correct the trigger and publish the version |
| Conversions fell when a consent banner launched | Consent state in preview; consent mode defaults and updates | Consent denied or consent mode misconfigured | Wire the banner to consent mode correctly |
| Conversions in GA4 or the CRM, none in Google Ads | Auto-tagging setting; landing URL after redirects | Auto-tagging off or the click identifier stripped | Turn auto-tagging on; keep query parameters through redirects |
| Status stays unverified, or conversions fire but are not credited to ad clicks | Tag Manager preview on a landing page: does the conversion linker or a Google tag fire on all pages? | Conversion Linker missing or not firing on all pages | Add the conversion linker with an all-pages trigger and publish |
| Imported GA4 conversions never arrive | Account link; key event marking; import list | GA4 key event not marked, link missing, or import delay | Link the accounts, mark the event and import it, then allow for the delay |
| Tag fires and counts, but bidding columns stay empty | Conversion action settings: primary or secondary, goal, counting | Wrong action, counting or primary/secondary setting | Correct the action and goal assignment |
Fix, verify and prevent each cause
The tag is missing or misplaced
The most basic failure is that the conversion tag is not on the page where conversions happen, fires on the wrong step (the form page instead of the confirmation), or vanished in a site update. The help centre describes setting up the Google tag across the site and the event for the conversion itself; both have to be present.
Fix: complete a real test conversion while watching the tag with Tag Assistant or the Google tag diagnostics, and move or restore the event so it fires on the success state. The step-by-step installation lives in the conversion tracking setup tutorial, which this page does not repeat. Where the conversion is a lead form that GA4 also misses, the page on GA4 not tracking form submissions separates the form-specific causes, such as forms sent by script or embedded from another service.
Verify: the action status changes to recording and a test conversion appears within the expected delay.
Prevent: add the success page and its tag to the release checklist for every site change. When the change is a full relaunch or replatforming, the guide to Google Ads during a website migration plans the tags, thank-you addresses and click identifier checks before launch day.
Tag Manager not published or triggering wrongly
With GTMTag management system., a tag that fires perfectly in preview may never reach visitors if the container version was not published, and a trigger keyed to a URL or a click element breaks quietly when the site changes.
Fix: open preview, complete the conversion, and read which tags fired on which event; if the tag fires there, compare the workspace with the live version and publish. If it does not fire, correct the trigger condition. The procedure is in Tag Manager debugging and preview.
Verify: the tag fires in a test on the live site with preview closed, checked through the browser's network requests or Tag Assistant.
Prevent: name and describe every container version, and publish only after a preview test of the main conversions.
Consent blocking the tag
Where a consent banner is in place, consent mode governs whether Google tags may use cookies. If defaults are set to denied and the banner never sends the update after acceptance, tags behave as though nobody agreed, and observed conversions fall sharply.
Fix: check in preview that the default consent state is set before tags load and that accepting the banner sends an update; correct the banner integration if it does not. Configuration is covered in the consent mode guide.
Verify: preview shows the granted state after acceptance, and conversions recover for consenting visitors.
Prevent: test consent behaviour whenever the banner or its vendor changes.
Auto-tagging off or the click identifier lost
Google Ads connects a conversion to an ad click through the click identifier that auto-tagging appends to landing URLs. If auto-tagging is switched off, or a redirect, a link shortener or a server rule drops query parameters, the conversion may still fire but cannot be credited to the click.
Fix: confirm auto-tagging is on in account settings, click a live ad, and check that the identifier is still in the address bar on the landing page and survives any redirect chain.
Verify: conversions start appearing against campaigns again.
Prevent: include parameter preservation in every redirect or URL change, as the setup tutorial notes in its troubleshooting table.
The conversion linker is missing or not firing on all pages
With GTMTag management system., the click identifier in the landing page address has to be read and stored when the visitor arrives. The conversion linker tag does that, as does a Google tag that fires on every page. If the linker is missing, or its trigger covers only some pages, the identifier is lost before the visitor reaches the conversion step: the conversion tag can still fire, but it cannot be joined to the ad click, so the action may stay unverified or record nothing against campaigns.
Fix: in Tag Manager preview, load a landing page that has a click identifier in its address and check that the conversion linker, or a Google tag, fires on it. If it does not, add the conversion linker with an all-pages trigger and publish the version.
Verify: reach the site from an ad click, complete a test conversion, and confirm that the linker fires on the landing page and the conversion tag fires once on the conversion step. The action status then moves to recording.
Prevent: keep the linker's all-pages trigger on the container review list, and check it again whenever triggers or the container structure change.
The GA4 import is not wired
Importing conversions from GA4Google's event-based analytics platform. needs the accounts linked, the event marked as a key event in GA4, and the conversion imported into Google Ads. Imported conversions also arrive later than tag-based ones.
Fix: check each of the three conditions in order, then wait for the documented delay before judging. The link and import steps are in the GA4 and Google Ads integration guide.
Verify: the imported action's status changes and recent conversions appear after the delay.
Prevent: review the link after any change of GA4 property or account ownership.
The wrong action or setting
Sometimes the conversion records perfectly but in the wrong place: the action is secondary, so the conversions column used for bidding ignores it; it is assigned to a goal the campaign does not use; or the counting setting does not match the business event. Conversion figures and AttributionAssigning conversion credit to touchpoints. depend on these choices more than on the tag.
Fix: open the action, set the right primary role, goal and counting, and check the campaign uses that goal. The measurement hub explains primary and secondary actions.
Verify: the action's results appear in the conversions column for the campaigns that should use them.
Prevent: keep a short register of conversion actions with their purpose and settings.
If a bid strategy changed at the same time, also read the bid strategy change diagnosis, because changing conversion actions can itself trigger a learning period. Stronger matching through enhanced conversions improves recovery once the basic chain works, but it cannot repair a broken link in it.
Prevention: monitoring conversion status after every release
Conversion tracking breaks most often on the day something else ships: a site release, a new checkout, a consent banner, a container change. Prevention is a habit attached to those days. After each release, complete one test conversion for each primary action and watch the tag fire. The morning after, read the action statuses and compare yesterday's conversions with the business's own records. Set an alert in Google Ads or in a reporting tool for a primary action recording far fewer conversions than usual, so a silent break is caught within a day rather than at month end. When an outage does happen, the tracking outage response SOP shows how to protect automated bidding while the fix is made. A falling CVRShare of visits or clicks that convert. with steady orders is the classic sign that tracking, not the business, has changed. Which bidding changes to hold back during the outage, and how to read results once tracking is restored, is covered in the guide to bidding through sales and tracking outages.
An online retailer whose purchases stopped recording
An online homeware shop sees purchase conversions in Google Ads drop from about 35 a day to 4 on 14 March, while the shop system still shows around 50 orders a day. Change history in Google Ads is empty for that week. Tag Manager shows a new version published on 13 March that added a cookie banner. In preview, the consent default is denied and accepting the banner sends no update, so the purchase tag waits for consent that never arrives. Fixing the banner's consent mode integration restores conversions to around 33 a day from 16 March, and the shop annotates the two lost days in its reports.
Common mistakes
- Changing conversion settings in Google Ads before testing whether the tag fires. The real fault stays in place, and the extra changes make its cause harder to see.
- Declaring an outage from yesterday's column without allowing for reporting delay. Conversions are filed against the click date and imports arrive late, so a normal gap looks like a break and prompts needless changes.
- Fixing a trigger in Tag Manager and forgetting to publish. The tag works in preview, never reaches visitors and conversions stay missing.
- Running the GA4 import and the native tag as primary for the same event. One real conversion is counted twice, which inflates conversions, understates cost per conversion and teaches bidding from duplicates.
- Publishing the conversion tag without the conversion linker on every page. The conversion fires but cannot be joined to the ad click.
