Google Adssearch · pmax · shopping AnalyticsGA4 · GTM Meta Ads Free audit Cases Blog

Blog

Ads Show 40 Sales, but You Have 25 Orders: Where Duplicate Purchases Come From

Why your account shows more sales than your CRM: a refreshed thank-you page, the transaction ID, two conversion actions and the Count setting.

A store receives 25 orders in a week. The Google Ads account shows 40 purchases for the same week. A pleasant number, until you remember that money arrived for twenty-five. The figures here are an example, but the situation is familiar to many online store owners: the contractor’s report looks better than reality, and nobody explains the gap.

Such a gap can be honest, or it can be the result of duplicates, when the system recorded one purchase twice. Below we go through two causes of duplicates, show how to spot them yourself in five minutes, and explain where the normal range ends. We checked the names of menu items and settings against the Google Ads and Google Analytics help in November 2026. The interface changes from time to time, so the buttons in your account may sit elsewhere.

First: which gap counts as normal

Not every difference between the account and the CRM is an error. Google’s Ads help on comparing with outside systems says it plainly: discrepancies, often up to 20%, are expected because different systems attribute a conversion to a channel differently. There is also a delay: data in the account can take up to 24–48 hours to arrive, so comparing yesterday is too early.

There is a subtlety the help does not spell out, and we add it ourselves. A CRM collects orders from every source: search, social media, direct visits, returning customers. Advertising claims only part of them. So in a normal situation the CRM holds at least as many orders as the ads show purchases. If the account shows more than the orders you received in total, the question is no longer about attribution. That is the first alarm signal, and it points to duplicates. One exception: cancelled and returned orders that you have already removed from the CRM while the ads kept their purchase. Rule that out before hunting for a tag error.

Cause 1. A customer returned to the thank-you page

The code that tracks a purchase, which Google calls the conversion tag, usually sits on the “Thank you for your order” page. A person paid, saw the page and closed the tab. Then they opened it from browser history, hit refresh, or followed a link in the confirmation email. The page loaded again, the tag fired a second time, and the same order was counted once more. The Google Ads help describes it much the same way: if a customer returns to the conversion page or refreshes it, the same tag can fire again.

Google itself provides the remedy: the transaction ID, a unique order number sent together with the purchase. If two conversions arrive with the same number, Google Ads treats the second as a duplicate and does not count it. The requirements from the help are simple:

  • the number is unique for each order, no longer than 64 characters and free of personal data;
  • it is generated by the store’s server or e-commerce platform and reaches the page dynamically, not typed in once by hand;
  • in Google Tag Manager you create a data layer variable for it and put that variable into the transaction ID field of the Google Ads tag.

There is also a sign that the number is not being passed. If the identifier carries a “GG_” prefix, the help says this means no custom ID was assigned on the page. Treat that case as an empty ID and fix the data being passed.

And in Google Analytics 4

GA4 can also remove duplicates by transaction_id, and its help contains two warnings few people read.

  1. An empty value is dangerous. If the site sends transaction_id as an empty string, GA4 deduplicates every purchase carrying that value, so different orders collapse into one.
  2. One ID for different orders causes undercounting. The help states that this way you could significantly undercount your key events.

So the problem runs both ways: with no ID there are too many purchases, with a wrong ID too many vanish. That is why “set it and forget it” does not work here: check the ID.

How to check it yourself

This is our practical method, not a procedure from the help. Place a test order (or ask your site developer), reach the thank-you page and refresh it three times. A day or two later, look at how many purchases were added in the account. One means the ID works. Four means the tag counts every page load. Afterwards delete the test order from the CRM so it does not spoil the report.

Cause 2. Two conversion actions count one purchase

The second source of duplicates hides not on the site but in the account settings. A purchase can be registered by two routes at once: your own Google Ads tag on the thank-you page, and an import of that same purchase from Google Analytics. In the account these are two different conversion actions, while the order is one.

What the help says. Every conversion action has a status. “Primary” actions feed the Conversions column and are used for bidding, “secondary” ones show only in the All conversions column. For actions imported from Analytics, Google Ads, according to the help, sets the secondary status precisely to avoid counting the same event twice for bidding. We found no direct warning about the specific pair “Google Ads tag plus Analytics import, both primary” in the help. The conclusion is ours, drawn from two of its statements: if you manually make both actions primary, one purchase lands in Conversions twice, and the bidding strategy learns from doubled data.

It takes a minute to check:

  1. In Google Ads click the “Goals” icon, then “Conversions” and “Summary”.
  2. Look at the list of conversion actions and the “Action optimization” column.
  3. Find two actions that describe the purchase: one from the tag, one imported from Analytics. If both say “Primary”, they most likely duplicate each other.
  4. Keep one as primary and switch the other to “Secondary (observe only)”. Which one to keep depends on your tracking. The change affects every goal and campaign where the action is used, so make it deliberately and note the date.

Note: after the switch the numbers in your reports will drop, and the bidding strategy may behave differently for a few days. That is a fair price for honest data, but warn your contractor and do not judge the result after a single day.

The Count setting: what it solves and what it does not

Each conversion action has a Count field with two options: “Every” and “One”. You find it in the same place: “Goals” → “Conversions” → “Summary”, then the action, “Edit settings”.

  • “Every” counts all conversions after a click. The help recommends it for sales: every purchase has value.
  • “One” counts at most one conversion per click. It suits leads, where a unique contact matters.

A typical mistake is to think that “One” fixes duplicates. For a store it hurts: a customer who placed two separate orders in one visit stays in the report as one. Duplicates from a page refresh are solved by the transaction ID, not by this field. The Count field only sets the counting rule once duplicates are gone.

How to compare ads with your CRM over one week

  1. Take a full week that ended at least two days ago, so you avoid the delay.
  2. In Google Ads open the campaigns for that period and write down the number of purchases from the Conversions column. For comparing with your own systems, the help suggests columns that count by conversion date rather than click date.
  3. In the CRM count the orders for the same dates, and separately those that came from ads, if the system records the source.
  4. Compare. The account is 10–20% above the CRM: looks like normal, especially if the CRM has other channels. The account is twice as high: look for duplicates by the two causes above. The account is higher than all orders in the CRM: this is almost certainly duplicates or cancellations.

In our practice, for stores whose tracking was “set up once by a developer friend”, the first two checks in this section find the problem more often than elaborate theories. That is experience, not statistics.

Summary

A duplicate purchase appears in two ways: the tag fired on a refreshed thank-you page, or two conversion actions with “Primary” status recorded one purchase. The transaction ID cures the first, a status change under “Goals” → “Conversions” → “Summary” the second. The Count field does not rescue you here. And to avoid arguing about numbers, compare the account with your CRM once a week: up to 20% of difference Google considers normal, twice as much is already a signal.

We covered similar stories about why the figures in ads and in your books disagree in our piece on Meta leads that do not match the CRM and “Paid via LiqPay — and the Sale Was Credited to LiqPay, Not to Your Ads”. A checklist of what tracking should treat as a result is in “What Your Ads Count as a Lead”. How we build campaigns for stores is in the Performance Max section.

Want a free audit of your Google Ads account? Send us a request — we will check whether your tracking counts one purchase twice.

All articles

Contacts

Let's talk?

Telegram — @exponenta_office_bot Phone — +38 099 314 89 83 Email — [email protected] Mon–Fri 10:00–19:00
Message us on Telegram

The fastest way: the bot logs your request instantly and passes it to the team.

or leave a request

By submitting the form, you agree to the privacy policy.
Telegram