Google Ads Conversion Tracking Counts the Tag, Not the Money
The tracking tag is installed, the goal is configured, and the conversion column starts filling in: 12 this week, 18 the next. Then the payment system is opened, the orders are counted, and the two numbers refuse to agree. One says eighteen. The other says five.
Every guide explains how to install conversion tracking. Almost none explains what the installed number is a record of. The gap between the two counts lives entirely in that unasked question.
Below: what the conversion count actually contains, why a flawless setup still does not turn it into a payment, and what a result signal has to survive to be trusted.
What Actually Fires
A conversion in Google Ads is an event the advertiser has designated as one. Most commonly a page load — a confirmation page, a receipt screen — or a click on a button. When the tag on that event fires, the counter increments by one.
The counter records that the tag fired. It does not record that money moved. A visitor who reaches a confirmation page and never pays counts exactly the same as one who pays — the page loaded, the tag fired, the number went up. Correct installation guarantees the tag fires reliably. It guarantees nothing about what the firing meant.
The Counts No One Clicked
Two categories widen the gap further, and both are on by default.
Modeled conversions. Where tracking is blocked — consent refusals, cross-device journeys, privacy restrictions — the platform estimates the conversions it believes happened and adds them to the total. These are statistical fills, not observed events. A portion of the column represents transactions no tag ever recorded.
View-through conversions. A user who saw an ad, did not click, and later converted can be credited to that ad. The attribution is assigned by the platform's rules, from an impression the advertiser cannot inspect. It appears in reporting as a conversion earned by the campaign.
The count, then, is a sum of tag firings, statistical estimates, and rules-based attributions. Useful signals, some of them — but not a list of payments.
Whose Definition It Is
One fact sits underneath all of it. What qualifies as a conversion, how it is modeled, and how it is attributed are defined by the platform — the party whose revenue is the advertiser's spend. That same count then feeds the bid algorithm and the budget recommendations, a point taken up in What Smart Bidding Optimizes For.
This is not fraud. The count is internally consistent and often directionally useful. It is simply the seller's measure of the advertiser's success, kept by the seller, and read back to the advertiser as evidence.
The Honest Improvements, and Their Limit
Two features narrow the gap and deserve credit. Enhanced conversions send hashed first-party data back to match conversions more accurately. Offline conversion tracking imports events that happen after the click — a signed contract, a completed sale — so a real payment can inform the record.
Both raise fidelity. Neither changes who holds the ruler. The matching, the modeling, and the attribution remain the platform's, and the imported payment becomes another input to the platform's count rather than an independent check on it. Better data, same custody.
What a Result Signal Has to Survive
A number worth optimizing toward has to answer one question without flinching: did money actually arrive, and from which ad. That means an event recorded where the money is — a payment in a payment system — attributed to the specific ad that produced it, in a ledger the seller does not keep. A record that can be recomputed from source, not one that has to be trusted.
Held to that standard, the conversion column is a diagnostic, not a verdict. It shows activity and direction; it cannot confirm revenue. Why the analytics dashboard next door fails the same test — unverifiable, self-disagreeing, built on ratios that can't be acted on — is set out in Google Analytics Is Useless.
Growity measures ads against a signal the platform does not keep: payments attributed to each ad, in a ledger that can be recomputed from source — budget then moves to what verifiably sells.
Common Questions
What counts as a conversion in Google Ads?
Any event the advertiser designates — usually a page load or a button click — plus modeled estimates where tracking is blocked and view-through credit from impressions never clicked. It records that the tag fired, not that a payment happened.
Why do Google Ads conversions not match actual sales?
The column sums tag firings, statistical estimates, and rules-based attributions. A visitor who reaches a confirmation page and never pays counts the same as one who pays. The two numbers measure different things, so they diverge.
Do enhanced conversions fix the accuracy problem?
They raise matching fidelity by sending hashed first-party data back to the platform. They do not change who defines and holds the count — the measurement stays with the party selling the clicks.
Does offline conversion tracking make the count a record of payments?
It imports real post-click events, which helps. The imported payment becomes another input to the platform's count rather than an independent check on it. Custody of the ruler does not move.
What signal should ads actually be judged by?
A payment recorded where the money is, attributed to the specific ad that produced it, in a ledger the seller does not keep and that can be recomputed from source. Anything else is a diagnostic, not a verdict.