00 The diagnosis library
Conversion tracking, diagnosed.
Every founder I audit thinks their ads are the problem. Half the time the problem is the data the ads bid against. This library covers the signals that say your tracking is broken, the reason each one happens, and how to confirm it on your own Shopify account. Read the umbrella answer below, then jump to the number that does not reconcile.
Think the spend is the leak, not the data? Read the Wasted Ad Spend library
Last updated June 2026 · 9 answers
01 The direct answer
How should a Shopify brand
wire conversion tracking?
Set up conversion tracking on Shopify in one direction: store first, server second, platforms last. Emit clean order data from Shopify, run a server-side GTM container as the spine, fire one de-duplicated purchase event to Google Ads and Meta through their conversion APIs, and keep GA4 for behavior, not attribution. Wire the layers in that order. Skip the order and your numbers will never reconcile.
The full architecture lives in my Tracking Stack reference, the eight-layer blueprint I rebuild every account to. This page is the diagnostic layer on top of it. When a number does not reconcile, the questions below name the cause and the order to check it in.
02 The six signals
Six signals.
One broken layer underneath.
-
SIGNAL 01
Platform totals and Shopify revenue do not agree
Google Ads says one revenue number, Meta says another, GA4 says a third, and Shopify says a fourth. None of them match. Some gap is normal because each platform attributes differently. A gap larger than fifteen percent against Shopify is a tracking problem, not an attribution quirk. Until the totals reconcile inside that band, every bid is placed against a number that is wrong.
-
SIGNAL 02
No server-side container, so the data is leaking
Safari and iOS strip client-side cookies, ad blockers eat browser beacons, and you lose roughly fifteen percent of conversions before they ever reach a platform. If tracking still runs entirely browser-side, the account is bidding on a thinned-out signal. A GTM server container on a custom subdomain is the spine the rest of the stack hangs from. Without it, every downstream number is already short.
-
SIGNAL 03
Meta ROAS is inflated by missing deduplication
The browser pixel fires a purchase. The Conversions API fires the same purchase. Without a shared event_id, Meta counts both and inflates reported ROAS by thirty to fifty percent. This is the most common reason Meta looks like it is printing money while Shopify revenue does not move. The fix is a dedup contract, not more budget.
-
SIGNAL 04
The conversion event is firing on the wrong trigger
Purchase conversions wired to a URL path fire on cart pages and refreshes. Conversions wired to button copy die silently the moment someone changes the CTA text. Triggers belong on actual server confirmations, not page paths or click text. When a conversion count looks too high or drops to zero overnight, the trigger is almost always the cause.
-
SIGNAL 05
The conversion value is the wrong number
Most accounts send order total as the conversion value. Smart Bidding then optimizes toward revenue that includes shipping, tax, and discounts you never kept. The value that belongs in the platform is gross revenue minus discounts and shipping. Feed the bidding algorithm an inflated number and it will buy you the wrong customers at the wrong price.
-
SIGNAL 06
GA4 is being used to grade ad performance
GA4 sessionizes traffic. Shopify counts orders. Those two will never agree, and grading ad spend against GA4 revenue guarantees a number that drifts further off every week. GA4 is for behavior: which pages lead to add-to-cart, which campaigns produce sessions that convert. Judge ad performance inside the ad platforms, from server-side conversions, not from a GA4 report.
03 Confirm on your account
Three references.
No sales call.
-
The Tracking Stack
Eight-layer reference for Shopify.
The architecture every answer here points back to. How the store, server container, platforms, and reconciliation fit together.
Read the stack -
Google Ads Setup Audit
Free 25-page PDF. No email gate.
The workbook I run before every diagnostic conversation. Covers conversion setup, dedup, and the standard tracking leaks.
Download the audit -
Wasted Spend Calculator
A two-minute directional estimate.
Bad tracking leads to bad bids. This estimates what the misallocated budget is costing you each month.
Run the calculator
04 The questions
Every question,
answered in full.
Grouped by where the number breaks. Each question links to a self-contained answer. No gate, no email.
01
Reconciliation
2 questions
-
What conversion value should I send to Google and Meta, and how do I keep them reconciling?
How to pick the conversion value you send to Google Ads and Meta so the two platforms reconcile with each other and with the numbers in Shopify or your CRM.
-
Why don't my GA4 and Meta conversion numbers match?
GA4 and Meta count conversions differently: attribution windows, modeling, and dedup. Here is how to read the gap and when it signals a real tracking problem.
02
Architecture
4 questions
-
How do I set up the Meta Conversions API the right way?
How to set up the Meta Conversions API so server events deduplicate with the pixel, match well, and reconcile with platform reporting instead of double-counting.
-
What are enhanced conversions in Google Ads and how do I set them up correctly?
How enhanced conversions work in Google Ads, the two types (Leads and Web), setup paths via GTM or the API, and the consent and hashing rules that decide match rates.
-
What is server-side tracking?
Server-side tracking sends conversion data from your own server to ad platforms instead of the browser. Here is how it works, why it matters, and when to use it.
-
What's the difference between Google Tag Manager and GA4?
Google Tag Manager is the delivery system for your tracking tags. GA4 is one report those tags feed. Here is how they differ and how they work together.
03
Troubleshooting
3 questions
-
How does Shopify Checkout Extensibility break my tracking, and how do I fix it?
Shopify retired checkout.liquid and additional scripts. What that breaks in your pixel, GA4, and CAPI tracking, and how to rebuild it with Web Pixels.
-
What is Google Consent Mode and how does it work?
A plain explanation of Google Consent Mode v2: the consent signals, basic vs advanced mode, conversion modeling, and the setup mistakes that break tracking.
-
Why is my Shopify conversion tracking not working?
Shopify tracking breaks at predictable points: a missing Customer Events pixel, mismatched event names, or no deduplication. How I find the real cause.
05 What I do with this
Same diagnosis,
run by a senior operator.
Every founder reading this can run the reconciliation on their own account. Pull Shopify gross revenue for the last thirty days, line it up against Google Ads conversion value and Meta purchase value, and read the gap. If the platforms land within fifteen percent of Shopify, the tracking is healthy and the problem is somewhere else. If they do not, the questions below walk through why.
That diagnosis is what I do. I am Conner Crowe. I spent a decade inside agencies and in-house teams, and more than $15M of managed ad spend working with founders direct. I rebuild the tracking before I touch a single bid, because bidding against a broken number for sixty days costs more than the rebuild ever does. Same person on the call as on the keyboard. No account manager.
The Tracking Stack is the architecture I rebuild every account to. This library is the diagnostic layer on top of it. If the questions get you to the answer, that is the point. If they convince you the rebuild is bigger than a weekend project, that is also the point. The book-a-call link is below, and the free audit covers the same ground first.
Want this reconciled in your account?
Same diagnosis,
run on your tracking.
Thirty minutes on the phone. I look at your pixel, your server container, and how your platform numbers line up against Shopify before the call. You walk out knowing which numbers to trust and what to fix first.