Google Ads
Google Ads says I have conversions. Shopify says I have no orders.
This is almost always a configuration or labeling issue, not a fake or fraudulent conversion. Somewhere in the account, a conversion action is counting something that isn't a completed Shopify purchase — the fix is finding out which one and what it's actually measuring.
First, find out which conversion action is firing
The headline "Conversions" number in Google Ads reporting is a sum across every conversion action enabled in the account. It isn't automatically a purchase count — it's whatever combination of actions someone set up, sometimes including actions added for a specific campaign and never revisited. Break the conversions report down by individual conversion action before assuming the whole total represents sales. That single step resolves this more often than any tag-level troubleshooting.
What's usually behind it
The "Conversions" total in Google Ads is a rollup across every enabled conversion action, not just Purchase. A lead form submission, a phone call click, an add-to-cart event, or even a generic page-view goal mislabeled as a conversion can all sit inside that same total without producing a Shopify order — because they were never supposed to.
If Google Ads is importing a GA4 conversion, check what GA4 event it's actually attached to. A GA4 event named something purchase-adjacent — begin_checkout, add_payment_info, or a custom event — can get imported as a conversion action without being the completed-purchase event itself.
Google Ads can attribute a conversion using data collected before a store migration, a domain change, or a conversion action reconfiguration. What's showing up today can reflect a click and a conversion window that both predate the current setup.
A conversion action created for a staging site, a previous Shopify domain, or a since-abandoned custom checkout can keep firing if it was never removed — recording activity that has nothing to do with the store currently taking orders.
Google Ads' conversion date and Shopify's order date aren't guaranteed to fall on the same calendar day, and comparing two reports pulled with different date ranges — or comparing "by conversion date" to "by conversion time" — can make matched activity look mismatched when it isn't.
Why "false conversion" is the wrong frame
It's tempting to call a conversion with no matching order "false," but that implies Google Ads invented an event that didn't happen. In nearly every case, something real did happen — a lead form was filled out, a checkout was started, a call was placed — and the conversion action is faithfully reporting it. The mismatch isn't fabrication, it's that the conversion action isn't scoped to "completed Shopify purchase" the way whoever's reading the report assumes it is. Once the action is identified correctly, the numbers usually stop looking mysterious.
The same pattern shows up on Meta too
This isn't a Google Ads-specific quirk. Meta accounts run into the equivalent problem when a Pixel or CAPI event fires for something other than a genuine completed order — see Meta Ads shows sales but Shopify has no orders for the same diagnosis applied to that platform. If you're managing both, it's worth checking both the same way.
Common questions
Is Google Ads fabricating conversions that never happened?
How do I check which conversion action produced a specific conversion?
Could this be the same issue as duplicate conversions?
Need help auditing the conversion actions themselves
Sorting out which conversion action is actually counting sales usually means going through account-level configuration. Send an inquiry and we'll help identify what's actually firing.