Our team reviewed a retail campaign for watches and jewelry in Ukraine. For retail of watches and jewelry in the Ukrainian market, the campaign optimized for both purchases and phone calls. Purchase events exceeded unique transaction identifiers by about 10%.
How to set up the tracking itself is already laid out in the guide to Google Ads conversion tracking setup. This page is the other side of that topic: what the gap looks like in a live store, and why it touches bids even though the review has no spend figures.
I have run ads since 2006, and I see this gap often. An owner reads events as orders. The ad account reads a different column and learns from the actions that landed in it.
What we checked
The team looked at three things: purchase events, unique transaction identifiers, and the fact that the campaign optimized for both purchases and phone calls. We do not name the store.
This matters to an owner because those actions are what a strategy can treat as success. The wider picture of advertising for this kind of store is in a separate piece on online watch store advertising. What stays here is a narrow cut: the purchase, the call, and the identifier.
What these names mean
A transaction ID is a unique number for one purchase, often the order confirmation number. A return visit to the confirmation page can fire the tag again and create a second conversion for the same order. If two conversions of the same conversion action share one transaction ID, Google Ads treats the second as a duplicate and does not count it. The help page on transaction IDs describes this mechanism.
The same ID on different orders pulls the count down: Google Ads may keep only the first instance of that number. For purchases, the help page recommends a transaction ID, not the Count setting on One. One glues different purchases from a single click into a single conversion.
These identifiers do not appear in account reports. The help page says a transaction ID will not be reported in Google Ads. You compare events with unique numbers from the orders the store already creates, not by sorting a column. A value with the prefix GG_ should be read as an empty ID: the tag did not send your number, and Google filled in a temporary one.
Primary and secondary actions sit beside that. A primary action is reported in the Conversions column and used for bidding when the goal it belongs to is used for bidding. A secondary action is for observation in the All conversions column and is not used for bidding. The exception on the same page: an action inside a custom goal is used for bidding even when it is secondary. The full description is in the help page on primary and secondary conversion actions. Marking an action for the wrong column is a setup mistake of its own, covered in the piece on a misconfigured conversion in Google Ads.
How we checked
The team counted purchase events and, separately, unique transaction identifiers. Then it compared the two counts. It also looked at which actions the campaign optimized for. Those actions were purchases and phone calls at the same time.
The review has no spend totals, no click counts, and no date window. The comparison is not the gap between two columns in the account, because transaction IDs are not shown in the reports. What is public is the relation between the two counts.
What we found
For retail of watches and jewelry in the Ukrainian market, the campaign optimized for both purchases and phone calls. Purchase events exceeded unique transaction identifiers by about 10%.
Why it matters
When bids are optimized for conversions, by an automated strategy or by hand, the strategy uses the data in the Conversions column. The help page on conversion tracking data says that column is what those bid strategies use. It includes the primary actions of the goal the campaign applies. An account-default goal spreads that choice to campaigns that do not have a campaign-specific goal.
In this store the campaign optimized for both purchases and phone calls. A call and a purchase are different actions. A repeated purchase ID does not remove the call from the column. The algorithm can use both actions as signals of success. For the store owner, success is a watch or a piece of jewelry that was sold. A call can be a question about size, stock, or someone else’s item.
The gap between events and unique identifiers touches bids from the other side. The gap shows up when some numbers repeat, or when some events have no number of their own. The review recorded the gap and did not split it into those causes. If you read events as orders, the purchase picture is wider than the set of distinct identifiers. If a duplicate with the same number was already dropped, the bidding column can sit closer to the unique numbers, while the event stream stays inflated. If an event had no ID of its own, a reload of the confirmation page can leave an extra conversion in the column the bids learn from.
Neither reading names a sum of wasted spend. That figure is not in the review. The bid target here is a mix of counted actions, not the cash register. Before you move bids because the Conversions column looks large, see which actions entered it.
What to check in your account
Check the same screens in the interface. The labels are the ones in the help pages. Count is described on the page about conversion counting options. The account-default goal and the campaign goal are described on the page about account-default conversion goals.
- In the Goals menu, open Conversions, then Summary.
- Find the purchase action and the call action. Click Edit goal. In Conversion action optimization, see whether it is Primary or Secondary (observe only).
- Check whether the goal is an account-default goal or this campaign has a campaign-specific goal. Bids use the primary actions of the goal applied to the campaign. An action inside a custom goal is used for bidding even when it is secondary.
- Open the purchase action, click Edit settings, then click Count. Every counts each conversion after an interaction. One counts one conversion per click. For purchases, the help page keeps the transaction ID, rather than switching Count to One.
- On the order confirmation page, check the transaction_id parameter in the conversion tag, in Tag Assistant or in the event snippet. It should change with each order. The same number on two conversions of the same action is a duplicate, and the second is not counted. The same number on different orders pulls the count down. Read a GG_ prefix as an empty identifier.
- Compare the Conversions column for the purchase action with the unique order numbers from your own orders for the same period. Keep calls out of that comparison: a call is a different action.
If you want the same checks as a sequence you can follow on your own, the step-by-step version is in my book on Google Ads for business owners.
My e-book “19 Google Ads Secrets”: how to get the most out of Google Ads without draining your budget, drawn from real campaigns and tests.
See the book →When this does not apply
This finding is not about your account if purchase events match unique transaction identifiers. The gap described here is absent in that case.
The point about mixed goals is not about your account if calls are secondary, are not part of a custom goal, and the campaign optimizes for purchases only.
This is an audit finding, not a result after a change, and events and identifiers do not confirm sales without reconciliation with orders.
Questions and answers
What a transaction ID is and why it matters
It is the number of one purchase, sent with the conversion by the tag. The same number on a repeat of the same action stops the copy from being counted. Different purchases need different numbers, or the count drops. Google Ads reports do not show this number, so the check uses the order numbers the store already has.
What it means to optimize for purchases and calls at once
Both actions are set so the campaign optimizes for them together. If both are primary and the goal is used for bidding, both enter the Conversions column. The strategy treats a purchase and a call as success. The call stays a call. It does not become a sold item merely because it shares that column.
How to reconcile purchase events with orders
Compare the count of purchase events with the count of unique order numbers. You cannot open those numbers one by one in the account: reports do not show the transaction ID. In your order records: a reloaded confirmation page, a number that never reached the tag, or one number on two orders. Keep calls on a separate list.