Google Ads Conversion Tracking Audit: Find Missing, Duplicate, and Misattributed Conversions
google-adsconversion-trackingattributionanalyticsppc-audit

Google Ads Conversion Tracking Audit: Find Missing, Duplicate, and Misattributed Conversions

AAdKeyword Editorial Team
2026-11-21
7 min read

Use this Google Ads conversion tracking audit to find missing, duplicate, or misattributed conversions before changing bids or budgets.

A Google Ads conversion tracking audit helps you determine whether reported conversions are complete, counted once, and assigned to the campaigns that influenced them. This checklist gives you a repeatable way to inspect conversion actions, tags, imported analytics goals, enhanced conversions, consent behavior, attribution settings, and test transactions before relying on the data for bidding or budget decisions.

Overview

Conversion data is the measurement layer behind Google Ads campaign optimization. If a purchase, lead, call, or signup is missing, duplicated, or assigned inconsistently, automated bidding and reporting can move in the wrong direction even when the ads and landing pages are working as intended.

A useful audit separates four questions:

  1. Is the conversion action configured correctly? Check the goal name, category, value, counting method, conversion window, and whether it is included in account-level goals.
  2. Does the tag fire at the right moment? Confirm that the Google tag, event snippet, Google Tag Manager trigger, or imported event runs only after the intended action is completed.
  3. Is the action used for optimization? Distinguish primary conversion actions used for bidding from secondary actions retained for observation.
  4. Does the reported result match the business record? Compare Google Ads with the CRM, order system, call platform, or analytics property while allowing for differences in attribution and reporting time.

Do not treat every discrepancy as a tracking error. Google Ads, analytics platforms, and CRMs may use different attribution models, time zones, conversion windows, deduplication rules, consent signals, and definitions of a completed action. The goal is to explain the difference and decide whether it is acceptable.

For broader account checks, pair this audit with the PPC Audit Checklist and review recent implementation changes in the Google Ads Change History Audit.

How to estimate

Use a simple reconciliation calculation rather than relying on a single dashboard total. Select a defined reporting period and record the same business event in each system.

Coverage rate = Google Ads conversions attributable to the event ÷ verified business conversions

Duplicate rate = suspected duplicate conversions ÷ total recorded conversions

Attribution share = conversions credited to Google Ads ÷ conversions recorded across the chosen comparison system

These are diagnostic ratios, not universal benchmarks. A coverage rate below your expected level may indicate a broken tag, an incomplete consent signal, a conversion-window difference, or a mismatch between the Google Ads action and the business event. A duplicate rate suggests that more than one implementation may be recording the same completion.

To make the comparison useful, use identical definitions. For example, compare completed paid orders with the Google Ads purchase action—not purchases initiated, payment attempts, or all website transactions. For lead generation, define whether a conversion means form submission, qualified lead, booked appointment, or closed opportunity. If you compare different stages, label the result accordingly instead of calling it a tracking gap.

A practical audit worksheet can contain these columns:

  • Business event and unique identifier
  • Google Ads conversion action
  • Source implementation: Google tag, GTM, imported analytics event, CRM import, or other method
  • Primary or secondary status
  • Counting method
  • Expected firing condition
  • Observed test result
  • Difference from the business system
  • Owner and next action

Inputs and assumptions

1. Conversion-action settings

Start in the account’s conversion management area and inventory every action that could influence reporting or bidding. Confirm the action name, source, category, value treatment, counting method, conversion window, and attribution setting. Naming should make the event’s meaning clear; “Lead” is less useful than “Qualified demo request” when multiple lead stages exist.

For purchases, counting every conversion may be appropriate because one customer can complete multiple orders. For many lead actions, counting one conversion per ad interaction may better represent a single prospect. The correct choice depends on the business event, so document the assumption instead of changing it to make totals look closer.

2. Primary and secondary goals

Review which actions are primary goals for campaign optimization and which are secondary observations. A thank-you-page view, brochure download, phone click, and qualified lead should not automatically carry equal optimization weight. If several actions describe the same funnel stage, decide whether they should be consolidated, separated, or kept as diagnostic events.

3. Tag and trigger behavior

Test the complete user journey in a controlled environment. For a form, submit valid details and confirm that the success state—not merely a button click—fires the event. For ecommerce, complete the order flow through the confirmation page or designated purchase event. Check whether a page refresh, back button, repeated submission, or single-page application route change can fire the same event again.

Use the relevant browser tag diagnostics, Google Tag Manager preview mode, or analytics debugging tools to inspect the event name, transaction ID, value, currency, and consent status. If the site uses both a directly installed Google tag and Google Tag Manager, document which implementation is authoritative. Two valid tags can still record one business action twice.

4. Imported analytics conversions and enhanced conversions

Identify whether an action is imported from an analytics property, recorded natively in Google Ads, or both. Importing an analytics event while also deploying a Google Ads event for the same completion is a common duplication risk. Keep one optimization source for the event unless there is a clearly documented reason to use separate actions.

Enhanced conversions can improve the information available for matching eligible first-party customer data, but they require an appropriate implementation, accurate user-provided data handling, and correct consent behavior. Treat them as an additional measurement configuration to validate—not as a replacement for testing the underlying conversion event.

Record what happens when a visitor declines analytics or advertising consent. Consent settings can change whether tags fire, what data is available, and how modeled or attributed results appear. Compare periods with similar consent conditions where possible.

Also record the attribution model, conversion window, reporting time zone, and date dimension used in the comparison. Google Ads may credit a conversion to an earlier ad interaction, while a CRM may assign it to the most recent lead source or to the eventual sales date. Those are different questions, not necessarily conflicting records.

Worked examples

Example 1: Missing lead conversions

A business system records 120 completed demo requests for a month, while Google Ads reports 96 conversions for the matching event. The initial coverage rate is 96 ÷ 120 = 80%.

The audit finds that the form confirmation is handled by a single-page application route. The tag fires on a standard page-load trigger, so it misses users whose URL changes without a full reload. After the trigger is tied to the confirmed success event, the team retests valid submissions, duplicate submissions, and failed forms. The coverage rate should then be recalculated for a fresh period; it should not be assumed that the historical gap has been retroactively corrected.

Example 2: Duplicate purchase conversions

An order system records 50 orders, but Google Ads reports 68 purchase conversions. Investigation shows that the purchase event is imported from analytics and also sent by a Google Tag Manager tag. The apparent duplicate rate, using the business order count as the reference, is (68 − 50) ÷ 68, or approximately 26% of recorded conversions.

The fix is to select one purchase implementation for the intended reporting purpose, verify that the transaction ID is passed consistently, and test a new order in a controlled environment. Historical conversions should remain documented as affected rather than silently rewritten.

Example 3: Correct totals, wrong campaign interpretation

Totals match the CRM, but one campaign appears to generate far more leads than expected. The audit reveals that a low-value form interaction is marked as a primary conversion while qualified leads are secondary. The tag works correctly; the optimization goal is wrong. Reclassifying the actions after confirming the business definition can improve campaign decision-making without changing the underlying event collection.

For search-query and keyword implications after the data is repaired, use the Google Ads Search Terms Report Guide. Reliable conversion data makes decisions about keywords, negatives, bids, and budgets more defensible.

Troubleshooting decision table

SymptomLikely areas to inspectFirst action
No conversions recordedTag placement, trigger conditions, consent state, event nameRun a complete test journey and inspect the event in a debugging tool.
Conversions suddenly doubledNew tag, imported analytics action, repeated confirmation firingCompare change history with tag deployments and transaction IDs.
Google Ads is lower than the CRMAttribution window, consent, date fields, event definitionReconcile the same event and date basis before changing tags.
Campaign totals look implausiblePrimary goals, campaign goal selection, cross-campaign attributionCheck which actions are eligible for optimization and reporting.

When to recalculate

Run the full conversion tracking QA checklist after every tracking implementation, website release, checkout change, form redesign, analytics migration, tag-manager edit, or consent-management update. Repeat it before changing bid strategies, budgets, target CPA, target ROAS, or campaign goals. An automated bidding system can only optimize toward the signals it receives, so measurement validation should precede major optimization changes.

For routine governance, perform a focused review monthly during reporting: compare Google Ads conversions with the CRM, order system, or analytics platform; investigate material changes; and record the explanation. Perform a deeper audit at least quarterly and whenever platform navigation, conversion-action settings, attribution options, or enhanced-conversion requirements change.

Keep a dated audit log containing the tested URL or journey, event name, conversion action, observed payload, consent state, test transaction or lead ID, and resolution. Recalculate coverage, duplicate rate, and attribution share whenever the comparison period, event definition, implementation, or reporting settings change. This turns conversion tracking from a one-time setup task into a repeatable measurement control—and gives you a safer foundation for campaign structure, keyword management, and bid decisions.

Related Topics

#google-ads#conversion-tracking#attribution#analytics#ppc-audit
A

AdKeyword Editorial Team

SEO and PPC Editor

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.