TL;DR
Shopify Plus stores crossed this bridge on August 28, 2025. Everyone else gets auto-upgraded by August 26, 2026, whether they have migrated their scripts or not [1]. Anything you pasted into Additional Scripts on the thank-you page, conversion pixels, affiliate tags, survey snippets, stops executing on the new pages. The replacements already exist: web pixels for analytics events (which now also load on customer accounts and the order status page [2]), app blocks and checkout UI extensions for visible widgets, and server-side delivery for the one event that should never have lived on a page render in the first place: the purchase.
What exactly stops working on August 26, 2026?
The legacy Thank you and Order status pages, and with them the Additional Scripts box. After the auto-upgrade, scripts entered under Settings → Checkout (the Order status page section) no longer run on either page [1].
This is the second half of a transition that began with checkout extensibility, which we covered in what checkout extensibility broke and what it did not. Checkout pages moved first. The thank-you and order-status surfaces are the last holdouts, and the date applies to every store that has not already upgraded: Shopify's own upgrade flow shows which scripts it detected and asks you to confirm their replacements before you flip the switch, but on August 26 the flip happens with or without you [1].
If your conversion tracking still lives in that box, the failure mode is quiet. Orders keep flowing. The thank-you page renders fine. Your Google Ads and Meta numbers just go to zero, and you find out from a spend dashboard, not an error message.
Where does thank-you page tracking live now?
Three destinations, depending on what the script did:
| Legacy Additional Scripts use | Its home after the upgrade |
|---|---|
| Conversion pixels (GA4, Meta, TikTok, Google Ads) | Web pixel (app pixel or custom pixel) subscribed to checkout_completed
|
| Purchase delivery you cannot afford to lose | Server-side, from the orders/create webhook, not from any page |
| Affiliate and referral tags | Web pixel checkout_completed subscription, or the vendor's app |
| Post-purchase surveys, upsell widgets | Checkout UI extensions / app blocks on the new pages |
| Session replay on the thank-you page | Gone from Additional Scripts; replay vendors need their own pixel or app block |
| Order-status page tracking for returning buyers | Web pixels, which now load there automatically [2] |
Two of these rows deserve expansion.
Web pixels run in a sandboxed worker and subscribe to Shopify's standard events (page_viewed, checkout_completed, product_viewed, and the rest). They are the sanctioned way to observe checkout and post-purchase pages, and since July 21, 2025 they also load automatically on the Order status page, and on customer accounts pages when the store uses a custom customer-accounts domain such as accounts.your-store.com [2]. That order-status coverage matters here: it is the direct replacement for the "fire something when the buyer returns to check their order" scripts that used to sit in Additional Scripts. Support on those surfaces covers page_viewed and the Advanced DOM API, and apps can publish custom events through an app block [2].
App blocks and checkout UI extensions cover the visible widgets. If the script rendered something the buyer could see, a survey, a referral offer, a tracking-number widget, it needs to become an extension component, not a pixel.
Why should purchases never depend on the thank-you page?
Because the event that reports them, checkout_completed, is not guaranteed to fire there. With post-purchase upsells enabled, it fires on the first upsell page instead of the thank-you page, and if that page fails to load, it does not fire at all [3]. A buyer who closes the tab after paying, a flaky mobile connection, an ad blocker that kills the pixel runtime: each one is a purchase your browser-side tracking never saw.
The order webhook has none of those failure modes. Shopify emits orders/create from its own backend the moment the order exists, regardless of what the buyer's browser did next. A tracking app listening there can deliver the purchase to GA4, Meta, TikTok, Google Ads, and the rest with the full order record attached, and if the browser event also fired, event deduplication by shared event ID keeps the two paths from double counting.
This is the emphatic point of the whole migration: August 26 only threatens stores whose revenue reporting depends on a page render. Rebuild the same fragile dependency inside a web pixel and you have upgraded the syntax, not the architecture. Put the purchase on the webhook and the deadline becomes a non-event.
How do you check what your store still runs in Additional Scripts?
A short audit, in order:
- Go to Settings → Checkout in Shopify admin and scroll to the Order status page section. If the Additional Scripts box exists and has content, copy it somewhere safe and inventory every tag in it.
- Check whether you are already upgraded: stores on the new pages show an upgraded Thank you / Order status configuration under Settings → Checkout instead of the scripts box [1].
- For each script you found, classify it against the table above: conversion pixel, visible widget, or vendor tag, and identify its replacement before the deadline, not after.
- Go to Settings → Customer events and review what already runs as a pixel. Each app pixel now has an activity log on its detail page: released June 29, 2026, it records every change to what customer data that pixel can access, with history from June 3, 2026 onward [4]. If you are auditing what your tracking apps actually see, this log is the first neutral record Shopify has given you.
- Place a test order and confirm the purchase lands in each ad platform. Our conversion tracking checklist walks the full verification, platform by platform.
One aside for stores that migrated long ago: it is still worth opening Settings → Checkout once before August. Old Additional Scripts content survives in the admin even when a pixel-based setup has been layered on top, and finding a forgotten duplicate Meta tag there is more common than you would expect.
What changes on customer accounts and the order status page?
Tracking coverage expands, and so does event volume. Because web pixels now load on those surfaces automatically [2], stores with pixel-based setups will see page_viewed events from buyers checking order status or browsing their account, sessions that were previously invisible to analytics. That is useful signal: until now most Shopify analytics setups simply lost the buyer at the thank-you page, and these sessions were invisible.
It also means your platforms may show a small uptick in page-view counts without any change in actual traffic. If you reconcile pixel page views against sessions, expect the new surfaces to account for the difference. What data reaches a pixel on any surface is still governed by Shopify's redaction rules, which we mapped in what customer data web pixel events expose, and browser events still respect the buyer's consent signals through Shopify's Customer Privacy API.
The custom-domain caveat is easy to miss: customer-accounts pixel loading requires the store to use a custom domain for accounts, such as accounts.your-store.com [2]. Stores on the default shopify.com accounts domain do not get that surface.
Key Takeaways
- August 26, 2026 is the auto-upgrade date for all remaining stores; Additional Scripts stops running on the Thank you and Order status pages that day [1].
- Shopify Plus already crossed this line on August 28, 2025; if you run Plus and still see legacy scripts, they are already dead weight [1].
- Inventory Settings → Checkout → Additional Scripts now and classify every tag: conversion pixel, visible widget, or vendor tag. Each has a different replacement.
- Move purchase delivery to the
orders/createwebhook path (server-side);checkout_completedcan fire on the first upsell page instead of the thank-you page, or not at all if that page never loads [3]. - Web pixels auto-load on the Order status page and custom-domain customer accounts since July 21, 2025, replacing the old "returning buyer" scripts [2].
- Use the app pixel activity log (Settings → Customer events, per-pixel detail page) to audit what data each tracking app can access; it records changes from June 3, 2026 [4].
- Run a test order before and after your upgrade and verify the purchase in every ad platform, not just one.
FAQ
Will my orders stop being tracked on August 26, 2026?
Only if your tracking still lives in Additional Scripts on the legacy thank-you or order-status page. Stores using a web-pixel-based app or a custom pixel, with server-side purchase delivery, are unaffected. The upgrade removes the legacy script surface; it does not touch pixels or webhooks.
Do I need Shopify Plus for the new thank-you page tracking?
No. The Web Pixels API, app pixels, and the new Thank you and Order status pages are available on all plans. Plus stores simply hit the migration deadline a year earlier, on August 28, 2025 [1].
What happens to the scripts I never migrate?
They stay visible in your admin but stop executing on the upgraded pages after the auto-upgrade [1]. Shopify's upgrade flow lists the scripts it detects so you can confirm replacements first; after August 26, 2026 the upgrade no longer waits for that confirmation.
Can a web pixel really replace my thank-you page conversion tag?
For the browser side, yes: subscribe to checkout_completed and you receive the order data the old tag scraped from the page. The stronger setup pairs it with server-side delivery from the order webhook, deduplicated by a shared event ID, so a purchase is recorded even when the browser event never fires [3].
How do I see what data my pixel apps can access?
Open Settings → Customer events, select the app pixel, and read its activity log. Shopify released the log on June 29, 2026; it records every data-access change per pixel from June 3, 2026 onward [4].
Tracking that does not care what the thank-you page does
WeltPixel Conversion Tracking never depended on the thank-you page. The web pixel captures checkout identity and Shopify's native event ID in the browser, and every purchase is delivered server-side from the orders/create webhook to GA4, Meta, TikTok, Google Ads, Reddit, and OpenAI Ads, with Klaviyo receiving the order for your email flows. Where a browser event also fires, the shared event ID keeps the two paths from double counting. Stores already running it have nothing to migrate before August 26: install WeltPixel Conversion Tracking and the deadline is someone else's problem.
Sources
- Shopify Help Center, Upgrade the Thank you and Order status pages: https://help.shopify.com/en/manual/checkout-settings/customize-checkout-configurations/upgrade-thank-you-order-status
- Shopify Changelog, Web Pixels load on Customer Accounts and Order Status Page (July 21, 2025): https://changelog.shopify.com/posts/web-pixels-load-on-customer-accounts-and-order-status-page
- Shopify.dev, Web Pixels API standard events, checkout_completed: https://shopify.dev/docs/api/web-pixels-api/standard-events/checkout_completed
- Shopify Changelog, View data access changes with the new app pixel activity log (June 29, 2026): https://changelog.shopify.com/posts/view-data-access-changes-with-the-new-app-pixel-activity-log