One Purchase, Two Conversions in Google Ads
We trace a purchase through Google Ads, distinguish repeated events from separate conversion actions, and check which source the campaign uses.
We use the advertising report to decide whether our spend is paying off and whether we can raise the budget. For that, we need purchases to be counted correctly. If one purchase and its value are counted twice, the ads look more worthwhile, even though the shop receives no extra money.
We risk spending more on ads because the reported result is overstated. That is why I would first check which purchases sit behind the figures and whether any are repeated.
Let’s take one order worth €60 and see how it reaches the advertising report. In the shop, we have one order number and one payment. But two sources can report the purchase to Google Ads: the tag on the website and an import from Google Analytics.
That is fine in itself. We can use one source for bidding and keep the other to compare figures. What we need to establish is whether the campaign treats two reports of the same purchase as two separate purchases.
One order, two reporting paths
€60
The diagram gives us €120 because we have assumed that both actions receive the full €60 value. A real report may not show an exact doubling. That is why I would start by checking one order, rather than trying to find a twofold difference in the totals.
Let’s find out who reported the purchase
Together with the specialist, we’ll go through checkout and see what the site sends after payment: the order number, value, currency and where each message goes. We’ll then match that to the conversion actions in Google Ads, including purchases from GA4.
Names such as “Purchase” and “New purchase” will not tell us much: they may represent different settings. We’ll take the order number from the shop and the events themselves — the standard campaign report does not give us a list of every order number. Our article on purchase tracking explains the overall setup in more detail.
After this check, we will be able to distinguish two situations.
Similar results, different causes
We’ll check the event and ID
One order → one stable ID.
Another order → another ID.
We’ll check the campaign’s goals
Which actions are used for optimisation?
The same ID does not merge different actions into one.In the first, the customer might have opened the “Thank you for your order” page again, causing the tag to send the purchase a second time. It is still the same order, so the number should stay the same. For purchases following an ad click, Google Ads filters out a repeat with the same transaction_id within one action. The next genuine order needs a different number, or some sales will be lost from the records. For conversions following an impression without a click — view-through conversions — adding an ID does not remove repeats. This limit is stated in Google’s help documentation.
In the second situation, we have two separate actions: the website purchase and the purchase from GA4. Both sources can send the correct number, but Google Ads will not use it to merge different actions. Switching from “Every” to “One” will not fix this either: it changes how purchases are counted after an ad interaction and can hide a second genuine order.
Let’s choose which purchase action to use for bidding
Suppose we have confirmed that both sources describe the same order. We’ll then choose the one that correctly reports purchases and their values for optimisation. In our example, that is the website tag. In another shop, the GA4 import may be more reliable.
One source for bidding, another for observation
Selected standard goal
Both actions can count the same purchase for optimisation.
The same selected goal
In this example, the tag is used for bidding and the import is kept for observation.
Within a standard goal, a primary action is used for bidding if the campaign has selected that goal. But I would always check whether the campaign has a custom goal. A secondary action included in it is also used for bidding when the campaign uses that goal. So after changing the action to “Secondary”, we’ll check the settings of every affected campaign. This Google Ads rule is easy to miss.
After making the change, we’ll go through an order again. Once the data has been processed, we’ll open the report by conversion action and check the value for each one. The second source may remain in “All conversions” — we kept it for observation, after all. We will no longer add the two sources together as two shop orders.
Let’s check what changed in the report
We’ll record the date of the fix. For the comparison, we’ll use matching time zones and columns by conversion time. Otherwise, a purchase following yesterday’s click could be recorded under yesterday in Google Ads and under today in the shop. We’ll also account for purchases in the shop that Google Ads does not attribute to advertising. Other reasons for discrepancies are described in the help documentation on imports from Analytics.
If conversion value in the report falls after the fix, I would first look at paid orders. The shop may be selling just as much — we have simply stopped counting one purchase twice. We’ll then review target ROAS using the corrected data, rather than automatically dividing it by two.
Google Ads Conversion Tracking an Online Store Can Trust
Get purchase, revenue and ROAS numbers you can rely on: make the paid order your only primary conversion, sent with its real amount and a unique order ID.
Ecommerce Attribution: Google Ads vs GA4 vs Your Shop
Find out which sales number to use for bidding, channel budgets and profit, and why Google Ads dates a sale by the click and your shop by the order.
How to set up conversions in Google Ads with Google Tag Manager
A simple and quick manual for setting up conversions.
Enhanced Conversions — a step-by-step setup for Google Ads and GA4
Form data is already collected on your site but never reaches Google Ads and GA4? Step by step — where to click, what you'll see, how to verify. Setup through Google Tag Manager.
Google Tag Gateway vs Server-Side Tagging: What Each Fixes
See what Google tag gateway and server-side tagging each recover for a store, which pays off at your size, and why a wrong purchase goal gets past both.
Google Tag Gateway via Cloudflare — a detailed guide
How to switch Google Tag Gateway on via Cloudflare in 10–15 minutes and recover 11–25% of lost conversions in Google Ads and GA4. Step by step, in English.