We Chased a Store's Vanishing Shopify Conversion Tracking

Quick answer: The ad account was healthy the whole time. Shopify's checkout migration had switched off the script that fed conversions back to Google, and nothing in the admin marked the store as affected.

A store's Google Ads conversions read 25 a day, then dropped to 1. Spend kept leaving the account. Orders kept landing in Shopify. Nothing in between connected the two anymore. The screen that confirms it is Settings > Customer Events in your Shopify admin: if that screen is empty and you run paid ads, you are probably looking at the same broken Shopify conversion tracking we spent an afternoon chasing across the wrong dashboards.

What we checked first

We did what most people do when Shopify conversion tracking craters: assume the problem is where the alarming number is. The alarming number was in Google Ads. So we started there.

Budget pacing looked normal. Bids were intact. The campaigns were still serving, impressions were steady, click costs were in their usual band. No policy strikes, no disapproved ads, no billing hold. By every internal Google signal, the account was working. The only thing wrong was that the conversions column had fallen off a cliff and stayed there.

We will admit the embarrassing part: we spent the better part of that afternoon inside the Google Ads interface, toggling attribution windows and re-checking conversion actions, before anyone opened the Shopify admin. When the symptom shows up on one platform, that is the platform you interrogate. It took a while to accept that the platform reporting the problem was not the platform causing it.

Why the ad account was not the problem

The test that broke the assumption was a manual purchase. We ran a real checkout, all the way through the thank-you page, with Google Tag Assistant open in the background.

The conversion tag did not fire. It was not late or duplicated, it simply did not run. The page that was supposed to carry the purchase event loaded, looked completely normal to a shopper, and reported nothing back. That single test moved the whole investigation off the ad account and onto the store. If the tag is not firing on the thank-you page, no amount of bid tuning in Google Ads will ever bring the conversions back, because there are no conversions arriving to count.

That is the moment Shopify conversion tracking stopped being an advertising question and became a checkout question.

Where the trail went cold

The obvious next suspect was the tracking code itself. Someone must have deleted it, or an app must have stripped it.

So we went looking for it. The store had, for years, run its Google conversion script in the Additional Scripts field under Settings > Checkout. That is where a lot of stores set tracking up once, during launch, and never touch again. We expected to find the script removed or mangled.

It was still there. The code was intact, exactly as it had been written. It was just not executing anymore. And sitting above it was a deprecation notice we had skimmed past twice: "Additional scripts is deprecated. Replace your additional scripts with pixels in customer events and with app blocks in the editor." No date in front of us, no explanation of consequences, no banner anywhere else in the admin. The trail did not lead to a deleted file. It led to a field that Shopify had quietly stopped running.

This is the part that makes the problem so hard to catch from the merchant's chair. The code is present. The setting looks configured. The store looks set up correctly to anyone glancing at it. There is no error, no red flag, no "this is broken" message. The script is just inert.

The clue we almost missed

Settings > Customer Events was empty. That was the actual signal, and it is unremarkable enough that you scroll right past it.

Shopify's newer system routes checkout events through Customer Events and Custom Pixels rather than through raw scripts injected into the checkout. When the platform locked the legacy checkout, the old Additional Scripts went dark and the new home for tracking stayed empty unless someone deliberately filled it. Nobody had. So we did the documented thing: installed the native Google & YouTube channel app, connected the Google Ads account, let its wizard register a purchase pixel.

GA4 stayed flat. This is where we nearly declared victory and left, because the official advice ends at "install the app." It took finding a year-old community thread where a merchant named eCominMotion had hit the same wall to learn the missing step: the native app alone did not re-emit the purchase event reliably on this store. Installing the channel app gives you a pixel; it does not guarantee working Shopify conversion tracking. We had to manually add an App Pixel that re-fires the purchase and checkout_completed events through Customer Events. That step is not in Shopify's migration guide. It surfaced through merchants comparing notes after months of flat dashboards.

After that, a fresh test purchase fired the tag. Conversions started arriving again the next day.

What it actually was

The cause was the checkout migration, full stop. Shopify moved stores onto Checkout Extensibility and locked checkout.liquid, which is where the Additional Scripts field used to inject code into the thank-you and order-status pages. Every downstream analytic that depended on those scripts - Google purchase events, the Meta pixel, TikTok and Microsoft conversion goals - stopped at the same instant the migration flipped.

The cruelty of it is the silence. There was no outage to point at. The store kept taking orders. The shopper experience never changed. The only thing that broke was the invisible wire carrying purchase data back to the ad platforms, and that wire breaks without a sound. We have seen merchants chalk the resulting performance drop up to "seasonality" or "ad fatigue" and keep spending against numbers that no longer mean anything. One documented brand watched its Facebook return on ad spend fall from 4.2x to under 1x after the migration deadline and only recovered after rebuilding the pixel path. The ad money was real. The conversions it was optimizing toward were a phantom.

If you take one thing from this: when Shopify conversion tracking collapses overnight and the ad account looks fine, open the checkout settings early instead of burning an afternoon in Google Ads first.

A second store, same symptom, a different culprit

We hit this pattern again a few weeks later, and the second time the cause was not the migration at all. It is worth telling because the symptom was identical and the fix was not.

This store had already completed the pixel migration. Customer Events was populated. The native channel apps were connected. And then Begin Checkout and Purchase events went dark for about 48 hours before anyone noticed the ad data getting weird. The store was running a third-party server-side tracking app, Stape DataLayer, and a Shopify platform update had silently revoked its Customer Events permission. The app still appeared in the list. It still looked installed and active. It had just lost the authorization it needed to receive events.

The fix was a two-minute re-authorization inside Settings > Customer Events. The hard part was knowing to look, because Shopify sends no alert when this happens. There is no email, no admin banner, no dashboard flag. The first symptom is your ad platform going quiet, which is exactly the symptom that sends everyone to the wrong dashboard first. An external audit of 97 active stores in mid-May found that 82% had no server-side tracking that was even detectable from outside the store, which means most merchants cannot confirm their own Shopify conversion tracking is alive without logging into the admin and checking. This is precisely the sort of silent gap help1's free store scan is built to surface before it costs you a month of ad spend.

If you are on Shopify Plus, there is a deadline attached

There is a related break coming that has a date on it, and it is close.

Shopify Scripts - the discount, shipping, and payment logic engine that Plus stores have leaned on for years - stops executing on June 30, 2026. That is 41 days from today. As of April 15, you can no longer even edit the Scripts you already have. The official replacement is Shopify Functions, and migrating to it is not a copy-and-paste. Scripts run in Ruby; Functions run in a sandbox with a hard 5ms execution limit, and complex conditional logic that ran fine in Ruby can quietly return nothing inside Functions without throwing an error. So you get the same failure shape we have been describing all along: logic that looks migrated, looks active, and silently does nothing.

Migration consultants we trust quote four to six weeks for complicated discount logic, and they all say the same thing: run Scripts and Functions side by side for at least two weeks before you cut over, and test against real customer data, not dummy accounts. If you are staring at a tangle of tiered discounts or postcode-based shipping rules and a calendar that ends June 30, that is exactly the wall where you want a second pair of hands. The first 15 minutes with a help1 expert is free, and for "is this Script going to survive the move or not," that is usually enough to get a clear answer.

The dead end we could not fix

Honesty demands we end on the case we did not solve. Merchants whose product category Shopify bans from Shopify Payments - one we worked with sells nutritional supplements - are in a genuine corner. The old thank-you-page script that used to fire their purchase event is gone with the migration. The native Google app only fires reliably when Shopify Payments is the gateway, which they are not allowed to use. A custom webhook pipeline they built did not make it out of the sandbox, and Google's own support staff gave up on it. We do not have a clean answer for that store, and as far as we can tell, neither does Shopify. If you are in that category and you have found a working path, we would genuinely like to hear it.

Tracking is the one part of a store that breaks without making a sound. If your ad numbers have shifted lately and you cannot point to a cause, when did you last run a real test purchase with a tag inspector open and watch the conversion event fire?