Two conversions can both show up in Google Ads, both look perfectly valid, and be worlds apart under the hood. The difference is not in the number. It is in what signal rode along with it.
That signal decides your match rate, and whether you are recovering the sales basic tracking quietly drops or just counting the easy ones.
Two Rails, Not One
A conversion can carry two very different kinds of signal into Google Ads, and they travel on separate rails.
The first is the gclid, the click ID Google appends to your ad’s landing-page URL. When that ID survives from click to checkout, it credits the campaign for the sale. The gclid is a click-attribution signal.
The second is Enhanced Conversions: a hashed (SHA-256) email or other user data attached to the conversion. This is a match signal. Instead of relying on a click ID surviving the journey, it ties the sale to the user by matching the hashed identifier against Google’s logged-in data. Different rail, different job.
What Each One Actually Recovers
The gclid is great at the easy case: a single device, cookies intact, a click that flows straight to a purchase. Credit lands cleanly.
Now look at what the gclid alone misses. Cross-device journeys, where the click happens on a phone and the purchase on a laptop. Safari and Firefox privacy protections that expire the cookie before the buyer returns. Ad blockers that stop the tag from firing at all. The gclid that simply did not survive a payment redirect or a checkout that happened days later. In every one of those, the click ID is gone, and a gclid-only setup records nothing, or records the sale with no campaign credit.
Enhanced Conversions catches a large share of exactly those cases. The hashed-email match does not care that the cookie expired or the device changed. As long as the buyer is in the consented cohort, the identifier can reconnect the sale to the click. That is the recovery.
The Trap: The GA4 Import Carries the gclid, Not Your Enhanced Match
Here is where a lot of accounts leave money on the table. A GA4-imported conversion action is a click-and-session attribution path. It can carry the gclid. It does not relay your Enhanced Conversions hashed-email match, because that match lives on the direct upload, not in the GA4 import.
So if Google Ads is counting and bidding on the GA4-imported action as your primary conversion, you get basic gclid attribution and you lose the match-rate uplift entirely. You are paying for the easy conversions and dropping the recovered ones.
This is the missing half of the double-count fix. When you choose which conversion action gets to be Primary (see The Conversion Double-Count Hiding in Your Google Ads Account), the answer is the action that carries the richer signal: the one with the Enhanced Conversion match, not the thinner GA4 import.
The Honest Version of Conversion Recovery
It is tempting to pitch first-party tracking as we capture more conversions than GA4. That claim does not survive scrutiny, and you should not make it.
Here is the version that does. First-party, server-side tracking with Enhanced Conversions recovers the conversions that client-side tracking loses to ad blockers, browser privacy limits, cross-device behavior, and broken click trails. It recovers them deterministically, as real matched orders, for the audience you are permitted to measure.
What it does not do is recover the opted-out cohort at the user level. Nothing can do that compliantly; only modeling estimates that group, and that is a separate, thinner path (Modeled vs. Measured covers it). So the defensible claim is not about raw volume. It is about quality: recovering the real, attributable sales that basic tracking drops, and feeding your bidder the clean deterministic signal instead of a noisy one.
Where CleanClicks Fits
This is the gap CleanClicks is built for: first-party, server-side conversion tracking that keeps both rails intact, the gclid and the Enhanced Conversion match, and gets that richer action set as the one your bidding actually runs on. You recover the conversions that privacy limits and broken click trails would otherwise erase, and you feed Smart Bidding the signal it optimizes best on. For the broader case on why this infrastructure is becoming non-optional, see First-Party Data and Server-Side Tracking: What Actually Works Now.
The number on the dashboard matters less than what is attached to it. A conversion with a surviving click ID and a hashed-email match is worth more to your account than two conversions carrying neither. Stop counting. Start checking what rode along.