Google Ads conversion tracking not working? Diagnose it properly.

Start with the conversion, not Google Ads

When Google Ads reports fewer conversions than expected, the first step is to confirm whether the underlying conversions actually happened.

For purchases, check your payment processor or order system. For leads, check the system that records completed form submissions, booked calls, or another meaningful conversion.

Those are completely different problems. If the conversion did not happen, you may have a traffic, landing page, or checkout problem. If it happened but tracking is missing, investigate the measurement path.

Why Google Ads conversions can look wrong

A discrepancy inside Google Ads does not automatically mean the tracking tag is broken.

Possible causes include:

• the conversion tag never fired
• the tag fired with incorrect data
• the conversion action is configured incorrectly
• Google received the conversion later than expected
• the conversion was not attributed to a Google Ads interaction
• consent configuration affected tracking behavior
• a website or checkout deployment changed the trigger
• duplicate tags created multiple conversion events

The fastest way to troubleshoot is to follow one real conversion through the full path.

Step 1: Run one controlled test conversion

Complete the same flow a real customer would use.

For a purchase, record the order or transaction ID, value, currency, and completion time. For a lead, record the submission time and whatever non-sensitive identifier your system uses internally.

This gives you a known conversion to compare against your tracking implementation.

Step 2: Confirm the Google Ads conversion tag fires

Use your website debugging tools and Google's tag diagnostics to determine whether the expected conversion action fires when the test conversion completes.

If page views and other tags still work but the conversion tag does not, the issue may be isolated to the conversion-specific trigger.

Check for:

• a missing or changed thank-you page
• incorrect Google Tag Manager trigger conditions
• tracking code removed during a website update
• JavaScript errors
• the conversion firing before the transaction completes
• the conversion firing on the wrong action
• consent settings preventing the tag from running

Step 3: Check the conversion value and currency

A conversion tag firing successfully does not mean the conversion data is accurate.

For ecommerce tracking, compare the transaction value and currency sent by the event with the real transaction.

Incorrect values can distort conversion value reporting and any downstream performance metrics that rely on it.

Step 4: Check transaction IDs

Transaction identifiers help distinguish individual purchases and can also help prevent duplicate conversion counting.

Compare the identifier on the real transaction with the identifier associated with the tracking event.

Missing, reused, or inconsistent transaction IDs can make it harder to determine whether one real conversion was tracked correctly.

Step 5: Compare actual conversions with tracking events

Do not rely only on Google Ads' aggregate conversion total.

Compare real conversions against the underlying events your website generated during the same period.

Those five unmatched transactions may indicate that the expected conversion event was not generated or delivered correctly.

Step 6: Check for duplicate conversions

Google Ads can also appear to over-report when the same real conversion generates multiple tracking events.

Common duplicate causes include:

• a thank-you page firing again after refresh
• multiple tags attached to the same conversion
• duplicate Google Tag Manager triggers
• overlapping ecommerce integrations
• retry behavior without consistent identifiers

If you suspect this, compare the number of unique real transactions with the transaction IDs attached to your tracking events.

Our guide to detecting duplicate purchase events covers this process in more detail.

Step 7: Check consent and privacy configuration

Consent settings can affect whether advertising and analytics tags execute and what data they can send.

If conversion tracking changed after you introduced or modified a consent banner, consent management platform, or Google Consent Mode setup, include that change in your investigation.

Test the conversion flow under the appropriate consent state and confirm whether the expected conversion event is generated.

What if the tag fires but Google Ads still shows no conversion?

If the underlying event appears to fire correctly, the problem may be further downstream.

Check the conversion action configuration, diagnostics, reporting delay, attribution behavior, and whether the conversion is actually eligible to be attributed to the Google Ads traffic you are examining.

A real purchase recorded by your backend and a conversion attributed by Google Ads are not necessarily the same number.

Google Ads conversions versus actual purchases

Your payment system records purchases regardless of where the customer came from.

Google Ads reports conversions according to its advertising attribution and reporting logic.

A customer who arrived through organic search, email, direct traffic, Meta, or another source may complete a real purchase without that purchase being attributed to Google Ads.

This is why a raw comparison between all purchases and Google Ads conversions cannot, by itself, prove that tracking is broken.

Why transaction-level comparison is stronger

Aggregate totals can hide tracking errors.

Your system could miss four purchases while accidentally duplicating four others. The total number of conversion events would still equal the total number of actual purchases.

The totals match, but eight transactions are represented incorrectly.

Matching individual conversions against individual tracking events gives you a clearer view of tracking integrity.

How SignalLeak detects broken conversion tracking

SignalLeak monitors the relationship between actual conversions and the tracking events produced by your website.

It watches for mismatches such as real conversions with no matching event, duplicate events, incorrect values, currency problems, and transaction ID issues.

This gives you a layer of monitoring underneath your ad platform reporting.

Instead of waiting until a Google Ads number looks suspicious, you can detect when the underlying tracking data stops matching the conversions that actually happened.

Frequently asked questions

Why is Google Ads not tracking my conversions?

Common causes include a conversion tag that no longer fires, incorrect triggers, website or checkout changes, bad conversion values, consent configuration, conversion-action setup issues, and reporting or attribution differences. Follow one real conversion from completion through the tracking event to find where the data disappears.

Why does my Google Ads conversion tag say inactive or unverified?

The tag may not have been detected recently, may not be firing on the expected conversion flow, or the conversion action may not yet have received valid activity. Test the actual conversion flow and review the tag and conversion-action diagnostics.

Why are Google Ads conversions lower than my actual sales?

Not every sale is attributable to Google Ads. Customers may come from other channels, and attribution settings or reporting timing can also create differences. Missing conversion events can contribute too, so inspect the underlying tracking events.

Can Google Ads conversion tracking break suddenly?

Yes. Website deployments, checkout changes, tag manager edits, consent changes, integration updates, or JavaScript errors can break a setup that worked previously.

How often should Google Ads conversion tracking be checked?

Ideally, continuously. Manual tests are useful, but they only prove the tracking worked at the time you tested it.

Related conversion tracking guides

Read our guide to detecting broken conversion tracking, troubleshoot missing Meta Purchase events, or learn how to find duplicate purchase events.