If Shopify already upgraded your Thank you and Order status pages—or purchase events quietly stopped after August 26, 2026—rebuild conversion tracking first, then replace page UI, then clean up leftover scripts. Visual customizations matter, but ads and analytics decisions break first when purchase events stop arriving.
This guide shows non-Plus and Plus merchants how to triage what broke, prioritize rebuilds with a Continuity Rebuild Ladder, score readiness, and validate events before trusting campaign data again.
Key takeaways
-
Shopify states that August 26, 2026 was the deadline for non-Plus stores to upgrade Thank you and Order status pages, and stores that were not upgraded by that date were upgraded automatically.
-
Script tags stopped running on the Order status page for non-Plus stores on August 26, 2026; Plus stores hit that cutoff earlier on August 28, 2025.
-
Tracking and analytics that used Additional scripts or script tags typically need web pixels; visual page customizations need blocks or customer account UI extensions.
-
Connect and test the replacement pixel before you permanently trust ads reporting—then disable the old script to avoid duplicate conversions when both paths still fire.
What changed—and what did not
Shopify’s newer Thank you and Order status pages are customized in the checkout and accounts editor. Legacy Additional scripts, incompatible apps, and script-tag-based customizations are not supported on those upgraded pages.
Two timeline facts matter for triage:
-
As of August 28, 2025, the Additional scripts field in Checkout settings became view-only. Merchants could no longer edit those scripts in place.
-
On August 26, 2026, Shopify’s developer docs say script tags with an Order status display scope stopped running for non-Plus stores. The non-Plus Thank you / Order status upgrade deadline was the same date, and Shopify’s Help Center now says remaining stores were upgraded automatically.
This is not the same problem as Shopify Scripts for Plus checkout discounts. Scripts were a Plus-only pricing feature replaced by Shopify Functions. Here the breakage is post-purchase pages: thank-you confirmation, order status revisits, conversion pixels, loyalty widgets, and similar customizations. For the Scripts→Functions rebuild path, see what to rebuild first after Shopify Scripts stopped.
Shopify also separates Thank you from Order status: Thank you is a one-time confirmation experience after checkout; Order status is the page customers can reopen to track and manage the order. Rebuild work often spans both.
The Continuity Rebuild Ladder
Use this ladder when measurement looks soft, CPA looks worse, or post-purchase UI disappeared after the upgrade. Climb only as far as the business impact requires.
L0 — Confirm the page version and the breakage type
In Shopify admin, open Settings → Checkout and review Configurations. If an upgrade notice still appears, follow Shopify’s personalized upgrade guide. If the store already upgraded, treat missing events or missing blocks as rebuild work rather than “wait for the deadline.”
Classify each missing capability as one of three types:
-
Measurement: purchase, lead, affiliate, or analytics events that used Additional scripts, app script tags, or legacy pixel injection.
-
UI: trust badges, upsell modules, delivery messaging, or other rendered content on Thank you / Order status.
-
Incompatible app: an installed app that still depends on script tags or has not shipped blocks / web pixels.
Shopify’s migration guidance is explicit: use web pixels for analytics and conversion tracking; use customer account UI extensions or app blocks for rendered content. Mixing those replacements is a common failure pattern.
L1 — Restore revenue-critical purchase tracking
Start with the events that feed paid media and revenue reporting—typically Google Ads, Meta, and primary analytics purchase events. Prefer an official app pixel when Shopify’s upgrade guide recommends one. If no compatible app fits, create a custom pixel under Settings → Customer events and subscribe to standard events such as checkout_completed.
Shopify recommends app pixels in the upgrade guide for stability, security, and performance. Custom pixels are an advanced option: they run in a sandbox, require JavaScript, and Shopify does not support building them for you. Expect consent-aware pixels to report fewer events than poorly consented Additional scripts—that drop can be measurement hygiene, not simply “broken tracking.”
L2 — Replace remaining tracking and analytics scripts
Work through every Tracking and analytics item in the Additional scripts section of the upgrade guide. Connect the replacement pixel, test with Shopify Pixel Helper (and the destination platform’s own helper when available), then disable the old script so both paths do not keep duplicate-counting.
If you use a custom domain for customer accounts, Shopify notes that the customer account domain should be a subdomain of your online store domain—such as account.example.com—otherwise pixels and cookie consent may not work correctly on the Order status page.
L3 — Rebuild high-impact Thank you / Order status UI
Only after measurement continuity is credible should you rebuild visual customizations with compatible app blocks in the checkout and accounts editor. Prioritize modules that change support tickets, delivery confidence, or post-purchase revenue—not decorative extras.
Non-Plus stores can use eligible apps that customize Thank you and Order status pages. Apps that customize Information, Shipping, and Payment steps remain Plus-only. Do not assume a Plus checkout UI extension pattern is available on Basic, Grow, or Advanced.
L4 — Resolve incompatible apps and retire dead weight
Apps listed as needing a developer update block a clean upgrade and leave merchants with false confidence. Contact the developer, replace the app, or uninstall it if it only provided a sunset script-tag feature. Then re-test a live or test order end to end.
Continuity Readiness Scorecard
Score each row 0 (not done), 1 (partial), or 2 (verified). Total out of 14. Treat a score below 8 as “do not judge ads performance yet.”
|
Check |
What “2” looks like |
|
Page state known |
Checkout Configurations reviewed; upgrade guide opened or confirmed already upgraded |
|
Purchase pixel live |
Primary ads purchase / checkout_completed path connected in Customer events |
|
Pixel Helper pass |
Shopify Pixel Helper shows the expected event after a test checkout |
|
Destination receives event |
Google / Meta / analytics UI shows the mapped purchase event with value when required |
|
Legacy script disabled |
Additional script deactivated after pixel verification to limit duplicates |
|
Critical UI rebuilt |
Must-have Thank you / Order status blocks live in the checkout editor |
|
Incompatible apps resolved |
Blocking apps updated, replaced, or removed; no silent script-tag dependency remains |
Worked example: a DTC brand with soft Meta purchases
Hypothetical example: a mid-market DTC brand on Advanced Shopify notices Meta Purchase volume drop the week after August 26, while store orders look stable in Shopify admin. Support also reports that a post-purchase loyalty block is gone from Order status.
-
L0: Checkout Configurations show the new Thank you / Order status pages. Upgrade guide still lists an Additional script for Meta and an incompatible loyalty app.
-
L1: Team connects a Meta app pixel (or a verified custom pixel subscribed to checkout_completed) before changing campaigns.
-
Validate: Pixel Helper confirms checkout_completed; Meta Events Manager shows the mapped Purchase after a test order.
-
Disable: Additional script is disabled to stop dual firing.
-
L3–L4: Loyalty UI is rebuilt with a compatible block app, or the old app is replaced. Ads learning is judged only after scorecard ≥ 8.
In this situation, rebuilding the loyalty widget first would have left media teams optimizing against incomplete purchase data. The ladder deliberately reverses that instinct.
Common failure patterns
-
Treating a consent-related event drop as a full outage. Shopify notes that pixels respect customer privacy settings more consistently than many legacy Additional scripts. Compare consented vs total traffic before rewriting every campaign.
-
Leaving the old script active “just in case.” That can duplicate conversions and poison bidding. Shopify’s upgrade guide expects you to disable the script after the pixel is verified.
-
Using a UI extension to “fix tracking.” Rendered blocks are not a substitute for web pixels.
-
Blaming theme liquid. Thank you / Order status customizations now live in checkout and accounts configuration, not the Online Store theme editor.
-
Confusing this with Plus Scripts retirement. Discount Scripts and post-purchase page script tags are different migrations with different replacements.
When this advice applies—and when it does not
This process applies when Thank you / Order status customizations or purchase events depended on Additional scripts, script tags, or apps that have not migrated to pixels and blocks. It also applies when Shopify auto-upgraded the pages and removed legacy customizations.
It does not apply if your only issue is a theme storefront regression, a Markets localization bug, or a Shopify Functions discount rewrite. Those need different workstreams. It also does not guarantee that restoring pixels will return prior ROAS—consent, auction dynamics, and creative still move independently.
Recommended next steps
-
Open Settings → Checkout → Configurations and work the upgrade guide inventory, even if the deadline already passed.
-
Restore L1 purchase tracking with an app pixel or custom pixel subscribed to checkout_completed.
-
Verify with Shopify Pixel Helper and the ads platform, then disable the legacy Additional script.
-
Rebuild only the Thank you / Order status UI that changes support load or post-purchase revenue.
-
Re-score the Continuity Readiness Scorecard before you pause, scale, or rebuild campaigns.
If your store needs theme, checkout configuration, and measurement rebuilt together, Oasbit’s website and SaaS development services cover Shopify storefront and post-purchase implementation work as one engineering surface—not as disconnected ticket fixes.
When purchase tracking and Thank you page customizations both need a sequenced rebuild, book a growth strategy session to map which pixels, blocks, and apps should ship first for your stack.
