If Google Ads shows zero conversions, do not start by reinstalling every tag. First identify where the signal stopped: did the customer action happen, did the tracking event fire, and could Google Ads associate that event with an eligible ad interaction? Those are separate checks.
Quick answer: read the exact conversion-action status and its details, then test the relevant data path. A verified tag can still show “No recent conversions” when there has been no recently attributed conversion. Conversely, a CRM lead can exist while the website event, campaign goal, or import path is broken. Google’s troubleshooting flow uses Tag Assistant for unverified, inactive, or attention-needed tags, and Google notes that a verified action can still show no recent conversions until conversions arrive (Google Ads: troubleshoot conversion actions with Tag Assistant).
Separate the three signals behind “not recording”
A form, call, or sale can be real in the business system but absent from an ad report for more than one reason. Trace the same action through three layers before changing the setup.
| Layer | Question | Evidence to check |
|---|---|---|
| Business action | Did the visitor actually submit, qualify, call, or buy? | Form success state, call record, order, or CRM record. |
| Measurement event | Did the intended tag or import send the correct event once? | Tag Assistant, GTM Preview, GA4 DebugView, or the upload diagnostics for the source. |
| Ad attribution and reporting | Was the event eligible to be attributed to an ad and included in the report being viewed? | Conversion action settings, campaign goal, attribution window, date range, and the “Conversions” versus “All conversions” column. |
Tag verification is not the same as proving that an ad generated the action. Tag Assistant can confirm that the conversion action fired in a test journey; Google says a verified action can then show “no recent conversions” until Google Ads receives conversions. Do not treat a diagnostic test as an attributed sale or lead in your performance analysis.
Read the status in the right place
Google Ads has more than one status surface. The overview status, the conversion action’s tracking status, and Google Tag Diagnostics do not use identical labels. Some overview statuses are still rolling out, so follow the details shown in your account instead of assuming every account has the same wording.
| Status or symptom | What it can mean | First move |
|---|---|---|
| Unverified | The associated tag has not yet fired or has not yet been verified. A new setup can need time for its first signal. | Launch the action’s Troubleshoot flow and trigger the intended event from the landing page through to success. |
| Tag inactive / Needs attention | Google’s tracking-status panel has an issue to investigate; the exact alert determines whether recording stopped or a configuration needs attention. | Open the status details, then use Tag Assistant and inspect the tag, trigger, conversion ID, and label. |
| Awaiting conversions / No recent conversions | There may be no recent ad-attributed conversions, even if the tag is correctly installed. A new action, paused campaign, or low traffic can also explain the absence. | Confirm the tag can fire, then check eligible traffic, campaign status, primary goal, date range, and conversion delay. |
| Active / Recording, but the campaign shows zero | The tag may be working while the campaign uses another goal, the action is secondary, the report column hides it, or no eligible ad interaction is being credited. | Inspect campaign goals and compare “Conversions” with “All conversions” for the same dates. |
| Misconfigured | The overview may indicate conversions stopped because of a setup error or broken tag. | Open “View details” or “View all issues”; repair the specific reported cause instead of changing unrelated tags. |
Google describes “Awaiting conversions” as no conversions recorded in the last seven days and notes that a recent setup, paused campaigns, or low website traffic can explain it. “Needs attention” does not necessarily mean all recording has stopped. Check the live status definition and its attached alert before treating either label as a tag failure (Google Ads: troubleshoot conversion tracking status).
Run a website-tag test from the landing page
For a Google Ads website conversion, start at a normal landing page and follow the same steps a visitor takes. Google recommends connecting Tag Assistant from the conversion summary and navigating through the site, rather than opening only the final conversion URL. If you use Google Tag Manager, enable its preview/debug session when Tag Assistant prompts you.
- Reach the real success state. Submit a test form or complete the intended action. For a single-page form, fire on confirmed success, not merely on a button click.
- Check the correct action. Verify the Google Ads conversion ID and label match the action being tested, and that the expected event fires once.
- Check the trigger and route. Confirm the tag fires on the current thank-you page or success event, including after domain changes, redirects, or a new form implementation.
- Check supporting tags. If you use GTM, review the Google tag and Conversion Linker setup as well as the Ads conversion tag and its trigger.
- Review consent behavior. Test the approved consent paths. A consent or tag-blocking configuration can change which signals are sent; do not disable privacy controls to make a diagnostic turn green.
- Inspect the result. Finish the Tag Assistant session and read its troubleshooting output. Google says verified actions can appear as “no recent conversions” until conversions are received.
Google Tag Diagnostics can flag additional issues, including a missing Conversion Linker in some GTM setups, untagged landing pages, a tag that stopped sending data, a redirect that loses click information, or a Content Security Policy that blocks tag resources. Open the diagnostic itself and address only the issue that matches your setup (Google Ads: Tag Diagnostics).
Follow the conversion source, not just the tag
The repair path depends on where the conversion action gets its data. Website tags, imported Analytics events, offline CRM uploads, and phone calls do not share one debugging procedure.
- Google Ads website tag: inspect the event in Tag Assistant, then verify the ID, label, page coverage, trigger, and Conversion Linker. Also confirm redirects preserve the click context required by the implementation.
- GA4-imported action: check that the correct Analytics property is linked, the intended event is marked as a key event, and the matching event was imported into the right Ads account. Google notes that linking properties or marking an event can take 24–48 hours to propagate to import options. Use DebugView for event receipt, then inspect the Ads import and action status separately.
- Offline CRM conversion: distinguish “sent” from “accepted.” Review the upload or API diagnostics for rejected rows, event time, action mapping, identifier fields, duplicates, and value/currency formatting. Google’s conversion-measurement guidance notes that offline processing can take time; do not repeat uploads blindly before checking their status.
- Phone conversion: identify whether the goal is a call from an ad, a call after a website visit, or only a click on a phone number. For eligible call measurement, check call reporting and the minimum call-length threshold. A tap on a phone link is not evidence that a call connected or qualified.
If the CRM has the lead but Ads does not, map the journey from the ad interaction to the landing session, form, CRM record, and conversion source. Preserve the click identifier and source context where your approved measurement setup supports it. For offline imports, compare accepted and rejected records using the offline conversion import QA workflow.
Check whether the campaign is meant to use the action
A conversion can be measured but not guide the campaign’s bidding. Google distinguishes primary actions used for bidding from secondary actions kept for observation. A secondary action can be visible in “All conversions” while excluded from the main “Conversions” column in the ordinary goal setup. Campaign-specific goals and custom goals can change which actions matter for a campaign.
Check the action’s primary/secondary setting, the account-default goal, and any campaign-specific goal. If the action appears in one report but not another, compare the columns, filters, and campaign goal before editing the tag. See the campaign-specific versus account-default goal audit and the guide to separating tracking coverage from conversion performance.
A focused diagnostic sequence
- Write down the exact symptom. Which action, campaign, report column, date range, source, and status show zero or an alert?
- Confirm the business event. Check whether the form, call, order, or CRM stage actually occurred and whether it meets the conversion definition.
- Use the status details. Open the alert in the conversion summary. Separate tracking status from campaign reporting and tag-quality diagnostics.
- Test the correct path. Use Tag Assistant for website tags, DebugView for an Analytics event, the upload diagnostics for offline events, or call details for phone actions.
- Check goal inclusion and attribution. Verify primary/secondary use, campaign goals, date range, attribution window, and the column being read.
- Change one cause at a time. Record the setting before repair, test the changed path, and allow the platform’s status and reports to refresh.
- Reconcile to the business source. Compare recorded ad conversions with CRM outcomes using the same conversion definition and time basis. Do not force different systems to show identical totals.
A recent conversion can also appear after the click-date report period you first checked, especially when qualification or sales cycles are long. Read the date basis and conversion delay before changing bids; the conversion-lag guide explains how late-arriving results can distort recent CPA.
Avoid these misleading fixes
- Reinstalling a tag before checking whether it is already firing, which can create duplicate conversions.
- Firing an event on the form’s submit-button click even when validation or server submission fails.
- Clicking your own live ad to test attribution. Use the supported debugging flow to inspect the tag path instead.
- Changing campaign goals and event code at the same time, making the cause of a later change unclear.
- Marking every event as primary to make a report populate; bidding should use the action that represents the intended business outcome.
- Calling a “No recent conversions” state proof of a broken tag without checking its details, traffic, and date range.
Frequently asked questions
Why does Tag Assistant verify the tag but Google Ads still show zero conversions?
Tag Assistant verifies that the configured event can be detected in the test journey. It does not prove that a real conversion was attributed to an eligible ad interaction in the report period. Google notes that a verified action may show “No recent conversions” until it receives conversions.
Does “No recent conversions” always mean the tag is broken?
No. It can reflect low traffic, paused campaigns, a new action, or the absence of recent ad-attributed outcomes. Open the status details and test the tag before making code changes.
Should a test form submission appear as a Google Ads conversion?
A test submission can help verify the event and tag, but it is not automatically an ad-attributed conversion. Use Tag Assistant or the source-specific diagnostics to test implementation; do not rely on a test event to represent campaign performance.
Sources and further reading
- Google Ads Help: Use Tag Assistant to troubleshoot unverified or inactive conversion actions
- Google Ads Help: Troubleshoot conversion tracking status
- Google Ads Help: Troubleshoot tag issues with Tag Diagnostics
- Google Ads Help: About conversion measurement
- PPC Panos: How to audit conversion tags in Google Ads
How did this article land?
Choose one reaction. You can change it anytime.