Why Google Ads Shows Zero Conversions When Leads Are Coming In

A prospect submits a form. Sales receives the email. The CRM shows a new contact. Google Ads still shows zero conversions.

That mismatch is frustrating, but it is not a diagnosis. A real lead and an advertising-platform conversion are related records created by different systems. They can disagree because a tag failed, because the wrong action is being counted, because attribution rules assign credit somewhere else, or simply because one report has not finished processing.

The right response is not to reinstall every tag or declare the campaign broken. It is to trace one representative journey from the ad click to the business outcome and identify where the evidence stops.

Start With the Business Event

Before opening Google Tag Manager, define what actually happened.

For a lead-generation business, useful evidence might include:

1. a form was successfully accepted by the website;
2. the lead notification reached the intended inbox or system;
3. the CRM created or updated the correct contact;
4. the lead came from a browser session that can be tied to an ad interaction; and
5. the intended Google Ads conversion action was eligible to receive credit.

Those are separate checks. A notification email proves that the form reached something. It does not prove that a browser event fired, that Google Ads received it, or that the lead qualified for attribution to an ad click.

This distinction matters in both directions. A Google Ads conversion can fire even when a form later fails to create a usable CRM record. A CRM lead can exist even when the browser-side conversion event never ran.

A Zero Does Not Prove the Tag Is Broken

Google's own conversion-tracking guidance notes that reporting can take time to update and that attribution can create differences between platforms. Google Ads generally assigns a conversion to the date of the eligible ad interaction, while another system may organize the same activity by the date the form was submitted or processed.

Before changing implementation, check:

• the exact date range and time zone in each system;
• whether the report uses Conversions, All conversions, or another column;
• whether the conversion action is primary or secondary;
• whether the action is included in the campaign's active goals;
• whether the lead came from an eligible Google Ads interaction;
• whether consent, browser restrictions, or cross-device behavior limited observable attribution; and
• whether the normal reporting delay has elapsed.

The practical rule is simple: treat zero as a symptom that needs evidence, not as proof of a specific failure.

Tags Can Stop Firing After a Page or Template Change

A tracking setup often depends on a page element, route, CSS selector, data-layer event, or thank-you-page URL. A website change can preserve the customer experience while quietly breaking that dependency.

Common examples include:

• a redesigned form uses a new element ID;
• a thank-you page becomes an inline success message;
• a single-page application changes routes without a traditional page load;
• a button is replaced while the old click trigger remains in Google Tag Manager;
• a form moves into an iframe or third-party scheduler;
• a theme update removes a data-layer push; or
• a new template never receives the sitewide tag.

Google recommends using Tag Assistant and its tag diagnostics to verify that the intended tag appears and fires on the current journey. That check should follow a representative path, not merely confirm that a Google tag exists somewhere in the source.

A Button Click Is Not a Successful Lead

Click tracking is attractive because it is easy to configure. It is also easy to overstate.

A click on Submit can occur when:

• required fields are missing;
• native browser validation blocks the form;
• the server rejects the request;
• spam protection interrupts the submission;
• the network request fails;
• the visitor clicks twice; or
• the form displays an error.

If the business outcome is a completed inquiry, the strongest browser-side event normally follows confirmed success—not merely intent to submit. That may mean listening for a validated success callback, a reliable confirmation state, or a server-confirmed event, depending on the website and consent architecture.

Clicks can still be useful diagnostic events. They simply should not be mislabeled as completed leads.

Duplicate Firing Can Hide Behind Apparently Healthy Totals

The opposite of zero is not automatically accuracy. A conversion can fire twice because:

• both hardcoded tracking and Google Tag Manager respond to the same action;
• a success event is pushed twice;
• page-history changes retrigger a tag;
• a thank-you page reload counts again;
• separate Google Ads and imported GA4 actions both sit in the primary conversion column; or
• a legacy tag remains after a new implementation launches.

Google's sitewide-tagging guidance specifically recommends checking for legacy and duplicate tags. A useful QA pass records the event name, conversion action, trigger, firing count, and downstream record for one test journey. “The tag fired” is incomplete if it fired twice.

The Event May Be Going to the Wrong Google Ads Conversion Action

Google Ads conversion tags pair a conversion ID with a conversion label. A correctly firing tag can still populate the wrong action when:

• an old label remains in the container;
• a copied tag belongs to another account;
• staging and production values were mixed;
• a GA4 key event was imported while the campaign optimizes toward a different action; or
• the desired action is secondary and absent from the primary Conversions column.

Verify the destination, not just the firing. The conversion action shown in Google Ads should match the business event, account, label, counting method, and optimization role the campaign is meant to use.

Google Ads and GA4 Can Count the Same Journey Differently

Google Ads and Google Analytics answer overlapping but different questions. Differences can arise from:

• attribution settings;
• eligible channels;
• lookback windows;
• counting methods;
• report columns;
• account time zones;
• the date used to place credit in a report;
• modeled or cross-device behavior; and
• whether an event is a GA4 key event, a Google Ads conversion, or both.

Google documents that time-zone differences and attribution settings can create reporting discrepancies. It also distinguishes GA4 key events from conversions used for advertising measurement and optimization.

The goal is not to force every interface to show the same number. The goal is to know what each number represents and ensure the primary optimization signal corresponds to a real business outcome.

A Bounded Diagnostic Workflow

Use one known, representative journey before changing the broader setup.

1. Confirm the lead exists

Record the submission time, page, form, and downstream destination. Confirm that the lead is not a duplicate, spam record, or test artifact being mistaken for a customer inquiry.

2. Confirm the acquisition context

Check whether the session actually came from Google Ads and whether the required click or attribution identifiers were available. Do not infer paid-search origin from the lead's subject line or the fact that ads were running.

3. Observe the browser journey without submitting a real lead

In an approved test environment, inspect validation, the form request, confirmation behavior, consent state, data-layer activity, and tag firing. Block or clearly segregate test submissions when possible.

4. Inspect the tag destination

Verify the Google Ads account, conversion action, ID, label, trigger, and firing count. Check whether the action is primary, secondary, or excluded from the campaign goal.

5. Compare platform definitions

Align time zones, date ranges, attribution views, counting methods, and report columns before comparing totals.

6. Check downstream persistence

Confirm that the website, notification system, CRM, and advertising platform each recorded the expected stage. Document the first break in the chain.

7. Change only the proven failure

Repair the narrow trigger, destination, duplication, or configuration issue. Then repeat the same controlled test and verify persistence after the save or publication step.

For a single isolated browser-side issue, Blackout's Conversion Tracking Rescue is designed as a bounded one-time repair. It is not a substitute for rebuilding an unclear measurement system.

When One Targeted Repair Is Reasonable

A focused repair is appropriate when the problem is narrow and observable—for example:

• one form's success event no longer fires;
• one Google Ads label is wrong;
• one duplicate browser tag can be safely removed;
• one template is missing the existing sitewide implementation; or
• one conversion action needs a clearly supported configuration correction.

The business should control the website and measurement accounts, and the fix should not require redesigning consent, CRM lifecycle stages, offline conversion imports, or the overall bidding strategy.

When the Problem Is Larger Than a Quick Fix

The work is broader when there is no agreed measurement plan, multiple forms and schedulers disagree, the CRM cannot connect leads to campaigns, consent behavior is unclear, or sales outcomes are missing from the feedback loop.

At that point, the useful questions become:

• Which actions should campaigns optimize toward?
• How are qualified opportunities distinguished from raw submissions?
• Which system owns the source-of-truth outcome?
• How do GA4, Google Ads, call tracking, CRM records, and offline imports reconcile?
• Which changes could alter bidding or historical comparability?

Blackout's Marketing Analytics & Attribution Consulting addresses that wider measurement architecture. If the measurement issue sits inside campaign structure, goals, search demand, and bidding decisions, Google Ads Management is the more appropriate starting point.

Fix the Evidence Chain, Not Just the Dashboard

Conversion tracking is not successful because a tag exists, a preview tool turns green, or one interface shows a number. It is successful when an agreed business event moves through the website and measurement systems with a documented definition, an appropriate destination, and repeatable evidence.

When leads exist and Google Ads shows zero, start with one journey. Separate implementation from attribution. Confirm the destination. Fix only the proven break. That is slower than guessing for five minutes and faster than spending a month optimizing campaigns against the wrong signal.

Authoritative references

• Google Ads: Troubleshoot your conversion tracking status
• Google Ads: Troubleshoot your sitewide tagging
• Google Analytics: Conversions vs. key events
• Google Analytics: Select attribution settings