Skip to content

TroubleshootingGoogle Ads

Google Ads Conversions Doubled After a Tracking Change: Diagnosis

Google Ads conversions doubled after a tracking change. Diagnose duplicate actions, every-vs-one counting, missing transaction IDs, and import overlap.

Published
Reviewed

Diagnosis

  1. Platform Google Ads
  2. Usual cause One purchase is counted by two paths, such as a GA4 import next to a direct Google Ads tag.
  3. Causes, ranked 5
  4. How to diagnose it 9
Go to the checks

First answer free, within one working day. Describe your case

Sounds familiar?

The symptom

Symptom report Google Ads

The change was supposed to be an improvement — a new tag, a different app, a cleaner checkout. Instead the Conversions column now reads roughly double what it did before, or roughly double the number of orders Shopify shows for the same period.

Nobody changed the campaigns or the prices. What changed is how many times the same purchase is being reported to Google Ads.

A steady count that doubles at the moment of a change: two overlapping routes feeding the same target
Tick what you see

Tick the lines that match your store.

Describe my case

The short version

Direct answer

Doubled conversions usually mean one purchase is now counted by two paths, not that you sold twice as much. Google Ads removes duplicate data only inside a single conversion action — between that action’s tag and its additional data source — and never across two different conversion actions. Two purchase actions both feed the Conversions column.

The counting setting and the transaction ID are separate defenses, and the change may have removed both. A conversion action counts either every conversion after an ad interaction or one per ad click, and a unique transaction_id stops the same order being counted again when someone reloads the confirmation page. Neither one deduplicates a second conversion action, so the fastest diagnosis is to find how many actions are counting the purchase before touching any setting.

Where to look

Causes, ranked

These setups account for most doubled counts, ranked by how often each one turns up in an account that was recently changed.

Google Ads conversions doubled5 causes

  1. Two conversion actions counting the same purchase

    The common pairs are an imported GA4 purchase sitting next to a direct Google Ads conversion tag, or the Google & YouTube app and a GTM tag both sending purchase. Each action counts on its own; Google Ads does not deduplicate across them.

  2. A legacy tag left running beside the new pixel

    The change added a path but never removed the old one. Additional Scripts, a theme script, or an old pixel still fires for the same order while the new tag also fires.

  3. The count setting left on every-conversion where one per click is what you want

    Every conversion is the default for website and imported conversion actions, and it is the right choice for purchases when a transaction ID is present. Without one, a reloaded confirmation page or a repeat purchase is counted again.

  4. A missing or mismatched transaction_id on one path

    If one path sends the order ID and the other sends nothing, a different prefix, or extra spaces, the values do not match. Google Ads can only suppress a repeat of the same transaction inside one conversion action, and only when the IDs match exactly.

  5. Enhanced Conversions or an offline upload layered over the online tag

    Additional data sources deduplicate against the tag only within the conversion action they are attached to. Uploaded conversions that land in a second action, or carry a different transaction ID, are added on top instead of replacing the tag’s record.

9 steps

How to diagnose it

Work from the account outward: identify every action that counts a purchase, then check the mechanisms that are supposed to stop double counting, then reconcile against Shopify orders.

  1. In Google Ads → Goals → Conversions → Summary (also reachable under Tools → Conversions), read the conversion actions table. List every action whose name implies a purchase, an order, or a checkout.
  2. In the same table, check the Source column and the status for each of those actions. Two purchase actions with different sources — one a Google Ads tag, one Analytics or Import — are the first thing to rule out.
  3. Check whether each action is primary or secondary (the setting that replaced Include in conversions). Only primary actions feed the Conversions column, while the All conversions column counts both, so note which column you are comparing.
  4. Open each purchase action and check its Count setting: every conversion or one per click. Then check whether that action’s tag actually sends a transaction ID, because counting every conversion without one is what lets a reload count twice.
  5. Open the action’s Diagnostics tab. Look for tag status, whether conversions are recording, and any duplicate transaction-ID error, which is how Google Ads reports a suppressed repeat.
  6. Load the order confirmation page in Tag Assistant (tagassistant.google.com), complete a test order, and watch which tags fire. If the Google Ads conversion tag fires and a GA4 or Google & YouTube purchase is also sent for the same order, and that purchase is imported as a conversion, that is the two-path case.
  7. In GA4 → Admin → Product links → Google Ads links, check which key events are imported as conversions, then open GA4’s DebugView for a test order to confirm the property itself sees one purchase, not two.
  8. In Shopify Admin → Settings → Customer events, list the registered pixels, and search the theme (Online Store → Themes → Edit code) and the checkout settings for any leftover conversion script. Confirm the old path was removed rather than just replaced.
  9. Reconcile a closed period: export orders (Shopify Admin → Orders → Export) and compare the order count and order IDs — not revenue — with the Google Ads conversion count and with the transaction IDs you saw in Tag Assistant.

Signal and fix

Decision table

Match the signal you found to the fix that removes the duplicate. The rows follow the causes above, so work down them until the Conversions column settles.

CauseSignal you’ll seeFix
Two purchase conversion actionsThe Conversions column runs near double the order count; two purchase actions with different sources are both primaryChoose one action as the source of truth, set the other to secondary or pause it, and leave it long enough to confirm the count settles
Legacy tag still liveThe old action keeps recording after the change; a script still exists in the theme or Additional ScriptsRemove the legacy tag so a single purchase path remains
Count setting on every conversionThe action counts every conversion and its tag sends no transaction ID; repeat page loads add conversionsSend a unique transaction_id, or switch to one per click if a single conversion per click is the goal
Missing or mismatched transaction_idDiagnostics shows duplicate transaction-ID errors, or uploads never match the tag’s eventsPass the same order ID on every path and match the format exactly, including prefixes and spaces
Enhanced Conversions or an offline upload on a second actionUploaded conversions appear on top of tag conversions; deduplication never firesAttach the upload to the same conversion action as the tag and key it with the same transaction_id, or stop the overlapping upload

A note from Daniilbefore you decide

Should you fix it yourself or bring in help?

Reading the conversion actions table, checking the Source and Count columns, and comparing order counts is something most merchants can do in the Google Ads interface without touching code.

What usually needs a developer is removing a legacy tag cleanly, threading one consistent transaction_id through every path that reports the purchase, and deciding which of two overlapping actions to keep without losing history that bidding relies on.

If the count stays doubled after you have confirmed a single active action and matching transaction IDs, the duplication is being created upstream — in the GA4 import, the app, or the upload job — and that is Google Ads conversion tracking work rather than a settings change.

— Daniil

Next

If the self-check does not settle it.

The checks above find the cause in most stores. When two or more overlap, an order-level reconciliation is faster than another afternoon spent comparing dashboards.

Tracking Health Check

Price
USD 395
Access
Read-only
Timeline
verdict two working days after the kickoff

What the reconciliation shows for this symptom.

A Health Check reconciles this symptom order by order against your Shopify orders, so the cause is a fact from your own data, not a guess from a dashboard. Real numbers for this symptom are not published yet — ask for the sample report.

Request a Health Check · USD 395

Follow the order. Then compare the evidence.

  1. Real orderOrder ID, amount, currency
  2. Browser / server eventsConsent, event ID, delivery
  3. GA4 / advertising platformsReceived events and reporting
  4. Reconcile the recordsMatch IDs, time windows and definitions
A completed order and a reported conversion are different records. Check the path and compare like-for-like before treating a difference as missing data.

Questions

Questions this symptom raises

Does Google Ads deduplicate two conversion actions that count the same purchase?

No. Deduplication happens inside one conversion action — between that action's own tag and any additional data source attached to it. Two separate conversion actions each count their own events, so if both are primary actions, a single purchase feeds the Conversions column twice.

Why did my conversions double instead of changing slightly?

A doubling usually means the change added a second path rather than replacing the old one: a new tag while a legacy script still fires, or an imported GA4 purchase action alongside a direct Google Ads tag. It can also be one action counting every occurrence — including a reloaded confirmation page — once its transaction ID stopped being sent.

Is the every-conversion counting setting wrong for purchases?

Not by itself. For purchases, Google recommends counting every conversion so repeat customers are recorded, and pairing that with a unique transaction ID so the same order is not counted twice. The setting becomes a problem when the transaction ID is missing, because a reload or a repeat visit to the confirmation page then adds another conversion.

Can I just delete the extra conversion action?

Check what depends on it first. Conversion history, bid strategy targets, and reports can all reference an action, so pausing it or moving it to secondary is usually safer than deleting. Confirm the Conversions column settles before removing anything permanently.

Read more, or check a neighbouring symptom.

All symptoms

The sibling problem — counts that do not match because of attribution and counting rules rather than a duplicate — is covered in Google Ads conversions not matching GA4. How to reconcile an ad platform’s number against Shopify orders is in order reconciliation.

For the Shopify-side double path that can feed the GA4 import, see the Google & YouTube app versus a custom pixel. The same duplicate-count diagnosis on the Meta side is Meta CAPI deduplication.

Daniil Maximkin

Hi, I’m Daniil.

I work with you from defining the problem to implementation and handover. You talk to the person who does the work. I work in English and Russian.

My story My work

Tried it and still stuck?

Describe your task

The first answer is free, within one working day. Or write directly: next@taskfordaniel.com