Quick Answer: On August 26, 2026, Shopify retires Additional Scripts on Thank You and Order Status pages for every non-Plus store. Anything still tracking purchases that way stops firing. Moving that pixel to a Web Pixel keeps it alive, but it's still a browser script tied to a page loading, not a fix for the deeper reliability problem.

Key Takeaways

• Non-Plus Shopify stores have until August 26, 2026 to migrate off Additional Scripts on the Thank You and Order Status pages, or Shopify auto-upgrades the pages and deletes the customization entirely, no preview, no undo after the fact.
• Plus stores already crossed this line on August 28, 2025, and have been auto-upgraded in batches since January 2026.
• If a purchase pixel, Meta, Google, TikTok, or an affiliate tag, still lives in Additional Scripts, it goes silent the moment the auto-upgrade hits, with no error message anywhere in your admin.
• Doing everything right on your end doesn't fully protect you: if an app you rely on for tracking or page content hasn't been updated by its developer to support the new pages, migrating your own settings correctly doesn't help, you're stuck waiting on someone else's release schedule.
• Migrating that same pixel into a Custom Pixel or Web Pixel keeps it alive past the deadline, but it's still browser-executed and still depends on the page loading, the same fragility ad blockers and Safari's ITP have exploited for years.
• A Shopify order webhook, not a page-rendered pixel, is the only purchase-tracking approach immune to both this specific deadline and the underlying browser dependency that caused the problem in the first place.

What is actually changing on August 26, 2026?

Shopify is permanently retiring Additional Scripts, checkout.liquid, and Script Tag apps on the Thank You and Order Status pages for every store still using them, replacing that customization path with app blocks for visible content and Web Pixels or Custom Pixels for tracking.

Non-Plus stores have until August 26, 2026 to migrate manually. Miss that date and Shopify auto-upgrades the pages for you, which strips out every Additional Scripts customization at the same time, whether it's a tracking pixel, an affiliate tag, or a visible page element like a custom order note display [1]. Plus stores already went through this: Script Tags stopped working on August 28, 2025, and any Plus store that hadn't migrated began being auto-upgraded, with 30 days' notice, starting in January 2026.

According to Shopify’s documentation, if you pause your store at any point, the upgrade happens automatically too, and it can't be reverted afterward.

Why is Shopify doing this now?

Because the old customization path, injecting arbitrary script code directly into a page, was never built for a checkout system that needed to be fast, secure, and privacy-compliant by default.

Shopify's own documentation on this migration makes a specific point worth repeating: app pixels and Custom Pixels only track customer behavior in line with a shopper's actual consent settings, while Additional Scripts and checkout.liquid code frequently weren't wired into consent logic correctly at all [2]. The new foundation also decouples page rendering from data availability for performance reasons, which has a side effect worth knowing about: order-specific fields that used to populate reliably when the page rendered aren't guaranteed to be available the same way anymore, which is precisely why Shopify is telling merchants to swap references like order.{anything} for checkout.order_id rather than assuming the old variables still behave the same way.

What breaks if you do nothing?

Everything sitting in Additional Scripts stops running the moment your store is upgraded, whether that upgrade happens manually or automatically on the deadline.

For a lot of stores, that's a visible page customization, an order note display, a custom thank-you message, something you'd notice within a day. For others, it's a conversion pixel quietly firing a purchase event to Meta, Google, or an affiliate network, and that's the dangerous version, because nothing in your Shopify admin tells you it stopped. Your ad platform dashboards simply start showing fewer conversions than your actual Shopify orders, and unless someone happens to be watching for that gap, it can take weeks to notice.

What if an app you rely on hasn't been updated yet?

Then migrating your own settings correctly doesn't fully protect you, because the fix depends on a release you don't control.

Shopify's personalized upgrade guide splits your installed apps into two groups: apps whose developer has already shipped compatibility with the new Thank You and Order Status pages, and apps that haven't been updated yet. For the first group, the guide points you to what to configure. For the second, the honest answer is that there's nothing to configure yet, the app itself needs an update before its tracking or page customization will work on the new pages at all. Your options at that point are contacting the developer directly, watching for their release, or switching to an alternative app that's already compatible. This is worth checking well before the deadline rather than after, since finding out an app you depend on hasn't shipped support with two weeks left gives you far fewer options than finding out with two months left.

Is moving to a Web Pixel or Custom Pixel actually a fix?

It fixes the deprecation. It doesn't fix the reliability problem that made browser-based tracking fragile in the first place.

A Web Pixel or Custom Pixel runs in a sandboxed environment Shopify controls, which is a real improvement, it's more consistent than an arbitrary script tag and it respects consent settings by default. But it's still browser-executed code tied to a page successfully loading and running in the shopper's device. Ad blockers still target known tracking patterns. Safari's ITP still caps what a browser-set identifier can do. And a script that depends on the Thank You page rendering fully still depends on the Thank You page rendering fully, express checkout flows, connection drops, and in-app browsers can all still get in the way. Migrating your purchase pixel to a Web Pixel means it survives August 26. It doesn't mean it stops missing conversions the way its predecessor did.

What's the difference between a Custom Pixel and an app pixel?

Shopify's own guidance actually draws this line on purpose: use web pixels to recreate page design and functionality, and use app pixels specifically to continue tracking customer events. That's not interchangeable wording, it points to two different ownership models for the same underlying Web Pixels framework.

A Custom Pixel is code you paste into Shopify's Customer Events settings yourself. You own it going forward: if a field name changes, if Shopify adjusts the API, if a new privacy requirement shows up, updating it is your job. An app pixel is registered and maintained by whichever app provides it instead, Meta's own sales channel app registers one automatically, and a dedicated tracking app does the same for whatever platforms it connects to. Both run in the same sandboxed environment, so neither is more or less exposed to ad blockers or ITP than the other. The difference is who's responsible for keeping the code correct as Shopify's platform keeps changing underneath it.

That distinction matters most right now, for anyone deciding how to migrate a purchase pixel out of Additional Scripts before the deadline. Rebuilding it as a Custom Pixel means it's yours to maintain indefinitely. Getting it through an app that already provides a maintained app pixel removes that ongoing maintenance from your plate, and if that same app also delivers the purchase event server-side rather than depending on a pixel firing at all, the maintenance relief and the reliability fix come from the same decision.

Additional Scripts vs. Custom Pixel vs. App Pixel vs. Server-Side Purchase Capture

What should you actually do before the deadline?

If you have no Additional Scripts today: no action needed for this specific deadline, but it's worth confirming, since Shopify's Configurations section under Settings → Checkout will tell you directly rather than leaving it to guesswork.

If your Additional Scripts only handle a visible page customization: app blocks are a fairly direct one-to-one replacement, and Shopify's auto-generated upgrade guide will point you to the specific block you need.

If your Additional Scripts fire a conversion pixel: don't stop at moving it into a Custom Pixel and calling it resolved. That step keeps the pixel alive past the deadline, but it doesn't address the browser-dependency problem underneath it, and building it as a Custom Pixel means you own maintaining that code going forward. An app that provides its own maintained app pixel removes that maintenance burden, though the underlying browser dependency is still there either way.

If purchase tracking accuracy actually affects your ad spend decisions: move the purchase event specifically to a server-side source, a Shopify order webhook, independent of this deadline entirely. That's the only version of this fix that isn't still exposed to ad blockers, ITP, or a page failing to load.

Can you undo the migration if something breaks?

Sometimes, but only under specific conditions, and only if you upgraded manually rather than getting auto-upgraded.

If your store was created before January 6, 2025, had pre-existing Additional Scripts or script-tag customizations, and you manually upgraded less than 30 days ago, you can revert to the old pages while you sort out whatever broke. After reverting, anything you'd already rebuilt with blocks is saved as a draft you can pick back up and publish later, so you don't lose that work. This window doesn't apply to stores that hit the deadline and got auto-upgraded, so it's a reason to migrate deliberately before August 26 rather than let the deadline force the change, a deliberate migration gives you a safety net an automatic one doesn't.

Common mistakes to avoid

• Assuming every app you use has already been updated. Check the Apps section of your upgrade guide specifically. An app that hasn't shipped compatibility yet needs a developer update or a replacement, not a settings change on your end.
• Waiting for the auto-upgrade instead of migrating deliberately. The auto-upgrade deletes Additional Scripts customizations with no preview and no way to inspect what you're about to lose first, and it forfeits the 30-day revert window that a manual migration keeps open.
• Treating "moved to a Custom Pixel" as equivalent to "fixed my tracking." It solves the deprecation, not the underlying browser-side fragility.
• Assuming old field references still behave the same way. Shopify's own guidance flags that fields like order.{anything} may no longer populate reliably under the new page-rendering model, and recommends switching to checkout.order_id and updating any downstream systems that depend on the old reference.
• Forgetting downstream systems entirely. If another tool or script reads data that used to come from the old Additional Scripts variables, that system breaks too, even if the page itself looks fine.
• Not re-testing after migration. A pixel that fires correctly in a test order isn't proof it's catching every real-world path, express checkout, connection drops, and in-app browsers all behave differently.

FAQ

What is the August 26, 2026 Shopify deadline? It's the date by which every non-Plus Shopify store must upgrade its Thank You and Order Status pages off the deprecated Additional Scripts and checkout.liquid customization path. Stores that haven't migrated by then are auto-upgraded, which removes those customizations.

What happens if I don't upgrade in time? Shopify automatically upgrades your Thank You and Order Status pages, and any Additional Scripts customizations, including tracking pixels, are removed as part of that process. There's no way to preview or recover the specific customization afterward.

Does moving my tracking pixel to a Custom Pixel fully fix the problem? It fixes the deprecation, since a Custom Pixel survives past the deadline. It doesn't fix the underlying issue, a Custom Pixel is still a browser-executed script tied to the page loading, so it remains exposed to ad blockers, Safari's ITP, and page-load failures the same way the old script was.

Is my store affected if I'm on Shopify Plus? Plus stores already crossed this deadline on August 28, 2025. Script Tags stopped working then, and any Plus store that hadn't migrated has been getting auto-upgraded in batches, with 30 days' notice, since January 2026.

How do I check if I still have Additional Scripts in use? Go to Settings → Checkout in your Shopify admin and look at the Configurations section. If there's a notice to upgrade your Thank You and Order Status pages, you're still on the deprecated version and have existing customizations to review.

Will this affect my Meta, Google, or Klaviyo conversion tracking? Only if that tracking currently runs through Additional Scripts or checkout.liquid rather than through an app-based pixel or server-side integration. If it does, it will stop firing once your store is upgraded, whether that happens manually or automatically.

What's the difference between a Web Pixel and server-side tracking? A Web Pixel still runs in the shopper's browser, in a sandboxed environment Shopify maintains, and still depends on the page loading successfully. Server-side tracking sends the purchase event from Shopify's backend directly, using the confirmed order record, independent of whether the browser executes anything at all.

Do I need a developer to migrate? For a purchase pixel, usually not if you use an app that provides its own app pixel, most tracking apps handle that setup entirely in their own settings, no code required. Building it yourself as a Custom Pixel does typically need someone comfortable writing and maintaining that code. Custom page content built with Additional Scripts can often be replaced with app blocks without code, though more complex customizations may need developer help.

What's the difference between a Custom Pixel and an app pixel? Both run in the same sandboxed Web Pixels environment, so neither is more exposed to ad blockers or ITP than the other. The difference is ownership: a Custom Pixel is code you write and maintain yourself in Shopify's Customer Events settings, while an app pixel is registered and kept up to date by whichever app provides it, removing that ongoing maintenance from your plate.

What if an app I use for tracking or page customization hasn't been updated yet? Check the Apps section of your Shopify upgrade guide, it separates apps that have already shipped compatibility from ones that haven't. If yours hasn't, your options are contacting the developer, waiting for their update, or switching to an app that's already compatible. Migrating your own settings won't fix a customization that depends on an app update you don't control.

Can I undo the migration if something breaks afterward? Only under specific conditions: your store must have been created before January 6, 2025, had pre-existing script-based customizations, and you must have upgraded manually less than 30 days ago. Stores that get auto-upgraded at the deadline don't have this option, which is one reason to migrate deliberately before August 26 rather than let the deadline do it for you.

Sources

[1] Shopify Help Center, "Non-Plus - Upgrading and replacing your Thank you and Order status pages" [2] Shopify Help Center, "Reviewing and replacing additional scripts on your Thank you and Order status pages" [3] Shopify Help Center, "Plus - Upgrading and replacing your Thank you and Order status pages"

Related reading

• Does Server-Side Tracking Really Bypass Ad Blockers?
• One Pixel, 16+ Destinations: How Aimerce Moves Your Data
• Cross-Device Stitching: Connecting Mobile Safari Discovery to Desktop Chrome Purchases