Shopify’s 26 August deadline has passed. Did your purchase tracking survive?

This was the rare tracking problem with a date on it. Most of what I write about is a slow leak you can fix whenever you notice. This one arrived for a large population of stores simultaneously, and the stores affected are precisely the ones least likely to be watching, because the change happens to them, not because of anything they did.

What actually gets removed

The word doing the damage is removed. Not migrated, not converted, not preserved in a compatibility layer. Shopify replaces the old Thank you and Order status pages with new ones, and customisations that depended on the old rendering model do not come along.

Read the last row twice. Server-side tracking is the only row that was never at risk, because it does not depend on a browser rendering a page Shopify controls. That is the real lesson of this deadline, and it will still be true the next time a platform changes something underneath you.

The ten-minute check

1. Read your Additional Scripts boxShopify admin → Settings → Checkout → Additional scripts. It has been view-only since 28 August 2025, but you can still read it. Copy the contents somewhere safe.
2. Find anything that fires a conversionSearch that text for gtag, fbq, googletagmanager, snaptr, ttq, or any <script src=. Every hit is a tag that was due to stop working on 26 August.
3. Check what your platforms think they are receivingOpen Google Ads → Goals → Conversions, and Meta Events Manager. Compare daily purchase volume for the days before and after 26 August. That before-and-after comparison is your proof, without it you cannot show that anything broke, or that you fixed it.
4. Rebuild each one as a Custom PixelShopify admin → Settings → Customer events → Add custom pixel. Custom Pixels run in a sandbox and subscribe to events such as checkout_completed.
5. Verify with a real orderNot a test link. A real purchase, on a phone, through the actual checkout. Then confirm the event arrived in the platform, not just that it fired in the browser.

The trap inside the fix

Migrating to a Custom Pixel is the right move, and it introduces a failure mode most guides skip.

checkout_completed is not guaranteed to fire on the thank-you page. With post-purchase upsells enabled it can fire on the first upsell page instead, and if that page fails to load, it may not fire at all. Practitioners have also reported a race condition where the pixel fires before customer data is populated, producing events with near-zero match quality.

What it looks like when it hits

Nothing dramatic. That is the problem.

Your ads keep running. Your budget keeps spending. Orders keep arriving in Shopify. The only thing that changes is that Google Ads and Meta stop being told which clicks produced those orders, so Smart Bidding, which optimises toward conversions it can see, starts optimising toward a signal that has quietly gone to zero.

You will notice it as a sudden drop in reported conversions and a rise in cost per acquisition, roughly a week later, with no obvious cause. By then the algorithm has been learning from bad data for seven days.

The honest limits of this article

The 26 August date and the auto-upgrade behaviour come from Shopify’s own help documentation, verified on 12 August 2026, before the deadline. Statements about the Additional Scripts box reflect that date too, and I have not re-verified them since. The table above reflects how these integrations are architected, sales-channel and server-side integrations do not depend on Additional Scripts, and hand-pasted page code does. I have not tested every row on a live store, and your setup may include something not listed here.

So do not take the table as permission to skip step one. Read your own Additional Scripts box. What is in there is the only list that matters.