How to Fix Google Ads Conversion Tracking Problems
To fix Google Ads conversion tracking problems, preserve the current setup and identify whether the symptom is zero conversions, duplicate events, wrong values, a broken trigger, delayed imports, or a real change in demand. Test the full path from the action through Google Ads and the source system before changing bids or goals. A tracking report is a measurement system; a plausible number can still be wrong.
Use this guide with how to optimize Google Ads conversion tracking, how to set up conversion tracking, and Google’s Tag Assistant guidance.
Preserve the evidence before changing the setup
Record the action name, primary or secondary role, trigger, tag source, count rule, value, currency, identifier, consent behavior, recent releases, and date. Save examples of a missing, duplicate, or incorrect record. If a broken event is causing campaigns to optimize against bad data, contain the risk by changing the approved goal or pausing the unsafe path only after documenting the change.
Separate a measurement symptom from a demand symptom. “Google Ads shows zero” may mean a tag is broken, an import is delayed, the action is not primary, or no one completed the action. “Conversions increased” may mean a duplicate trigger or a newly included micro-action. The first job is to trace one expected event.
Fix zero conversions when the action should be firing
Start at the source action. Complete a controlled form, purchase, booking, call, or other defined outcome. Check whether the action succeeds in the website or business system. A broken form or declined checkout is not a Google Ads tag problem.
If the business action succeeds, inspect whether the tag foundation loads, the event trigger runs after completion, the correct conversion action is selected, and consent permits the expected behavior. Check page templates, domains, redirects, single-page routes, Tag Manager publishing, and recent releases. Google’s web conversion setup guide and Tag Assistant guidance are useful references for this investigation.
Confirm the action is included in the report or campaign goal being reviewed. A secondary action may record correctly without being used as the primary optimization signal. Do not make a page view primary merely to avoid a zero.
Fix an event that fires at the wrong time
A conversion should represent a completed business action. If it fires on a button click, page load, form start, checkout view, or route change before success, move the trigger to the validated completion state. Test invalid, abandoned, declined, and successful paths separately.
For forms, wait for a successful server or application response. For purchases, use the confirmed order state. For bookings, use the created appointment. For calls, distinguish a link click from a connected or qualified call when the business makes that distinction.
A thank-you page can be a practical trigger, but check refreshes, back-button visits, shared URLs, and redirects. A URL that can be loaded without a new completion should not automatically create a new sale or lead.
Fix duplicate conversions
Compare a Google Ads action with the source system over a fixed period. Look for duplicate tags, an Analytics import plus a Google tag, browser and server events representing the same order, confirmation-page reloads, retries, webhooks, and transaction identifiers that are missing or changing.
For purchases, use a stable transaction or order identifier where the supported implementation allows it. For leads, define whether a repeat submission is a new opportunity, a duplicate, or a follow-up. Do not simply delete duplicate rows without finding the path that created them.
If two integrations are both needed, document the purpose of each and how the same outcome is deduplicated. Test a new order or lead and then refresh, retry, or revisit the confirmation state. The expected result should be one business outcome under the chosen counting rule.
Fix wrong conversion values or currencies
If counts look correct but value reporting is wrong, trace the value from the source order, lead model, or CRM stage to the event and then to the Google Ads action. Check currency, decimal representation, tax, shipping, discounts, refunds, cancellations, and product or service changes.
For ecommerce, verify one test order against the source system and confirm that the transaction identifier matches. For leads, check that an estimated value has a documented meaning and is not treating an unqualified inquiry as a closed sale. For later-stage value, use a supported offline or CRM process instead of inventing a value at the first form.
Google’s offline conversion setup information can help when the important outcome happens after the website. Do not use a value field to make performance look healthier than it is.
Fix delayed or missing offline imports
For a CRM or offline conversion, inspect the source record, identifier, timestamp, action name, value, currency, upload or API status, and any validation or policy errors. Check timezone and the delay between the click, lead, qualification, and final outcome. A legitimate import can arrive later than the online action, so compare a period that allows for the sales cycle.
If one stage is missing, test the identifier mapping rather than changing the campaign goal. Confirm that the action still exists and is named correctly, that the source system has the record, and that the import process has an owner. Reconcile accepted, rejected, duplicate, and pending records.
Do not count the same lead as both an online conversion and an offline sale unless those are intentionally separate actions with separate roles.
Fix a mismatch between Google Ads and the source system
Platform and source-system totals may differ because of attribution, processing, privacy thresholds, timezone, counting, cancellation, or definition. The difference should be explainable. Compare one known record through the website, tag tools, Google Ads, analytics, and CRM instead of only comparing aggregate totals.
Create a reconciliation table for a fixed period:
- source records created;
- events sent;
- events accepted;
- Google Ads conversions reported;
- duplicates or canceled outcomes;
- qualified or closed outcomes;
- expected processing or attribution difference.
If the event is in the source system but not Google Ads, inspect tag, action, consent, and import status. If Google Ads has events the source lacks, inspect duplicate triggers, test traffic, page views, or wrong action mapping.
Fix a sudden conversion change
Build a timeline around the first abnormal day. Include website releases, checkout changes, tag or Tag Manager publications, analytics migrations, consent updates, primary/secondary role changes, action edits, domain redirects, CRM imports, budget changes, ad changes, and business events.
An abrupt increase may be a duplicate event, a trigger firing too early, a new primary action, or a missing transaction identifier. An abrupt decrease may be a broken tag, a consent change, an unavailable page, a delayed import, or an actual demand change. Test the event before changing bids.
If the tracking fix and a campaign change occur together, preserve the timeline and treat the period as a new baseline. Do not claim that a bid caused a movement that was actually a tag release.
Fix consent and data-handling behavior
Check whether the event is expected to fire in the user’s consent state and region. Compare accepted and denied test paths according to the approved privacy implementation. A lower observed count after a consent change may be a measurement behavior change rather than a demand collapse.
If using Enhanced Conversions or first-party data, follow Google’s Enhanced Conversions best practices and the business’s consent and data-handling requirements. Hashing does not make unapproved collection valid. Assign an owner to regional and release behavior.
Do not add customer data to repair a conversion gap without confirming the approved collection, disclosure, retention, and access process.
Use a structured repair sequence
For a normal troubleshooting pass:
- Preserve the action settings, symptom, and date.
- Complete one controlled business action.
- Verify the source-system outcome.
- Inspect the tag foundation, trigger, action, consent, and identifier.
- Check count, value, currency, duplicates, and primary/secondary role.
- Trace the record through reports or imports.
- Make one documented correction.
- Re-test success and failure paths.
- Set a review date and compare against the baseline.
If the issue is an unsafe primary signal, protect campaign decisions promptly and annotate the change. If the problem is only a reporting delay, do not rewrite the event. The smallest correction that restores a truthful signal is usually easier to verify than a complete rebuild.
Know when the issue is not tracking
A clean event does not guarantee demand, offer quality, page relevance, or sales acceptance. Once the action is firing once at the correct completion, with defensible values and a reconciled source record, investigate targeting, ads, landing pages, budget, bidding, and business operations separately.
For a full implementation review, use Google Ads conversion tracking best practices. For a controlled optimization pass, read how to optimize Google Ads conversion tracking. The adz.so product overview is an honest next step for supported workflows; it does not install tags, diagnose private account data automatically, or guarantee campaign results.