Skip to content
Google Ads

Google Ads counting conversions twice

Google Ads reports noticeably more conversions than the CRM or shop shows, or one test lead produces two or more conversions on the same action or across two actions.

Steps checked against the platforms' documentation on November 20, 2026.

Quick answer

The usual cause is two primary conversion actions measuring the same thing, typically a Google Ads tag action and an imported GA4 key event. The next most common is a tag that fires again on thank-you page reloads with no transaction_id and counting set to Every. Compare Conversions by Conversion action against the CRM, then test one submission in GTM Preview and count the hits.

1. Two primary actions measure the same conversion

Agencies often inherit an account with a Google Ads tag action for a lead form plus an imported GA4 key event for the same form, both set to Primary. Every primary action in the goal feeds the Conversions column and bidding, so each lead is counted twice. Google's help for GA imports advises importing a conversion only once and using Secondary for duplicates.

How to check

  1. 1In a campaign report, segment by Conversions > Conversion action for the last 30 days.
  2. 2Look for pairs that track the same event, for example Lead form submit (Google Ads tag) and generate_lead (Google Analytics), with near-identical counts.
  3. 3Go to Goals > Summary, open the goal with Edit goal and see which of them are Primary under Conversion action optimization.

How to fix

  1. 1Choose one source of truth per conversion. For bidding, most practitioners keep the Google Ads tag action, which supports enhanced conversions directly.
  2. 2Set the other action to Secondary (observe only) so it still reports in All conversions without inflating Conversions.
  3. 3Note the change date in the client report. The change doesn't rewrite past data, and bidding may need one to two conversion cycles to adapt.

2. The tag fires again on thank-you page reloads or revisits

If the conversion tag fires on every view of the thank-you or order confirmation page, a refresh, back button, or bookmarked confirmation link records a new conversion each time.

How to check

  1. 1Open GTM Preview, complete one test conversion, then reload the thank-you page.
  2. 2Count how many times the Google Ads Conversion Tracking tag shows under Tags Fired.
  3. 3In Goals > Summary, open the action's settings and check the Repeat rate figure for a hint of repeated conversions per click.

How to fix

  1. 1Fire the tag on a one-time success event pushed to the dataLayer by the form or checkout, not on the page view.
  2. 2If you must use the page view, add a unique transaction_id so repeat hits are dropped (see the transaction ID cause below).
  3. 3For lead actions, set Count to One so repeats from the same click are not counted.

3. Counting is set to Every for a lead action

With Every, Google Ads counts each conversion after an ad interaction. That suits purchases. For leads, Google recommends One, which counts only one conversion per ad click, so a person submitting twice or a tag misfire is not counted twice.

How to check

  1. 1Hover over the action in Goals > Summary to see its Count setting.
  2. 2Compare the action's conversion count with unique leads in the CRM for the same clicks and period.

How to fix

  1. 1Open the action, select Edit settings, then Count, and choose One for lead, call and sign-up actions. Keep Every for purchases.
  2. 2Save. The change only applies to future conversion reporting, so annotate the date for the client.

4. GTM trigger fires twice for one submission

Common setups that double-fire: a form submission trigger plus a thank-you page trigger on the same tag, an All Forms trigger on a form plugin that also pushes its own success event, or the tag published in two containers or hard-coded alongside GTM.

How to check

  1. 1In GTM Preview, submit the form once and walk through each event in the left-hand timeline. Note every event where the Google Ads conversion tag fired.
  2. 2Open the tag and review its Triggering section for more than one trigger.
  3. 3Use Tag Assistant to list all tags on the page and look for the same conversion ID and label coming from both GTM and a hard-coded gtag snippet or a CMS plugin.

How to fix

  1. 1Keep one trigger per conversion tag, tied to the success event.
  2. 2Under the tag's Advanced Settings, set Tag firing options to Once per event or, for a page-based success state, Once per page.
  3. 3Remove the duplicate hard-coded snippet or plugin integration, publish, and re-test with one submission.

5. Purchases are sent without a unique transaction ID

Google Ads drops the second conversion for the same action when it carries the same transaction ID. Without one, every repeat purchase hit counts. Google recommends a transaction ID for purchases, and it must be dynamic, not a fixed value.

How to check

  1. 1In GTM Preview, open the conversion tag's details and look at Transaction ID. It should be the order number, not empty, undefined or a static string.
  2. 2In Tag Assistant, check the hit's transaction_id parameter. In Chrome DevTools, filter for googleadservices.com/pagead/conversion and look for the oid value in the payload.
  3. 3Place two test orders and confirm the ID changes.

How to fix

  1. 1Push the order ID to the dataLayer on the confirmation page and map it to Transaction ID with a Data Layer Variable, or pass transaction_id in the gtag conversion event.
  2. 2Keep IDs under 64 characters and free of personal data.
  3. 3If you also import offline conversions for the same action, send the same value as the Order ID so sources line up.

Stop it happening again

  • Agree one source of truth per conversion with the client and keep every other measurement of it Secondary.
  • Use One for leads and Every with a transaction ID for purchases.
  • Fire conversion tags on success events with Once per event, and test reloads as part of QA.
  • Reconcile Google Ads conversions with CRM leads monthly, by conversion action, not just in total.
  • Before importing GA4 key events, check whether a Google Ads tag action already measures the same thing.

Questions

4 questions

Only partly. Within one conversion action, conversions with the same transaction ID are deduplicated, and One counting keeps one conversion per click. Two different actions measuring the same lead are not merged. Fix that by setting one of them to Secondary.

Pick one and make the other secondary. Many agencies keep the Google Ads tag action as primary because it supports enhanced conversions and transaction IDs directly, and use the GA4 key event for cross-channel analysis.

No. Google states that changes to count settings only apply to future conversion reporting. Annotate the change date in your client reporting.

No. Google notes transaction IDs do not resolve duplicate view-through conversions. They deduplicate repeat hits for the same action.

Got an account that doesn't add up?

Send us one account. We review it for free and send a short video of what's working and what isn't.