Thank You Page Scripts Stopped? Recover Tracking and Content
checkout.liquid and additional scripts were sunset on Shopify's Thank you and Order status pages. How to rebuild tracking with pixels and custom content with extensions.
In this guide
Conversions in your ad platform dropped to zero. The affiliate network says it stopped receiving sales. The delivery note or survey link you showed after purchase is gone. If any of that started after your store’s Thank you and Order status pages were upgraded, the cause is almost certainly the same: the code that did it lived in additional scripts or checkout.liquid, and those no longer run there.
This guide covers what was sunset and when, what each old script type should become, and the steps to get tracking and custom content working again.
What was sunset, and when
Shopify’s checkout.liquid documentation gives the dates:
| What | Plus stores | Non-Plus stores |
|---|---|---|
checkout.liquid and additional scripts on Thank you and Order status pages |
Sunset August 28, 2025 | Sunset August 28, 2025 |
| Script tags on Thank you and Order status pages | Sunset August 28, 2025 | Sunset August 26, 2026 |
| Upgrading the pages themselves | Deadline August 26, 2026, per the help center |
The help center adds that since August 28, 2025, the additional scripts box in checkout settings is view-only. You can read what is there, but you cannot add to it. Upgrading replaces the existing pages and their customizations with the new versions, and a store that is paused is upgraded automatically and permanently.
What stopped working
Anything that depended on code pasted into those pages:
- Conversion and analytics tags: ad platform purchase events, analytics purchase tags, tag manager containers.
- Affiliate and referral tracking: sale pixels that send the order number and total to a network.
- Custom content: delivery instructions, a thank-you message per product type, links to a survey, a loyalty sign-up prompt, a Liquid block that read order details.
- Small scripts: chat widgets, redirects, cookie-based logic that ran after purchase.
If something on the old pages came from an app instead, it only keeps working if the app now uses the new technologies. Shopify’s upgrade guide flags those apps as incompatible.
What replaces each script
| Old script did | Replace with | Where |
|---|---|---|
| Ad or analytics purchase tracking | An app pixel from the platform’s app | App pixels |
| Tracking for a platform without an app | A custom pixel | Settings > Customer events (custom pixels) |
| Static or conditional text, banners, buttons | Blocks from an app, such as Shopify’s Checkout Blocks app, added in the checkout editor | Checkout Blocks |
| Custom content using your own logic or data | A checkout UI extension in an app | purchase.thank-you.block.render and customer-account.order-status.block.render |
| Post-purchase surveys | An App Store app, or a UI extension | Shopify has a survey tutorial |
Plans matter less here than in checkout itself. Shopify’s checkout technologies page says Thank you and Order status extensions and web pixels are available on all plans except Shopify Starter, while checkout UI extensions on the information, shipping and payment steps are Plus only. The Checkout Blocks help page says the dynamic and static content blocks work on the Thank you and Order status pages from the Basic plan up.
Recover tracking: step by step
1. Open the upgrade guide
In Settings > Checkout, open the upgrade guide or the customizations report. It sorts your additional scripts by purpose, such as order tracking, and lets you replace or deactivate each one. If the view-only additional scripts box still shows your old code, copy it somewhere safe before you start.
2. List each tag and its destination
For each script, note the platform it sends data to, the event (usually a purchase), and the fields it sends: order ID, total, currency, line items, coupon. This list is what you will check against later.
3. Prefer the platform’s own app
Shopify’s additional scripts guide recommends app pixels “for improved stability, security, and performance.” Many ad and analytics platforms connect through their own Shopify app. Install it, connect it, and test the app pixel.
4. Write a custom pixel for the rest
When a platform has no app, a custom pixel replaces the pasted script. Shopify’s steps to add one:
- Go to Settings > Customer events.
- Enter a unique name and click Add pixel.
- Adjust Customer privacy settings if needed.
- Paste the code, click Save, then Connect pixel.
The code changes shape. Instead of reading values printed into the page, you subscribe to events. For purchases, the event is checkout_completed:
analytics.subscribe("checkout_completed", (event) => {
const checkout = event.data.checkout;
// send checkout.order.id, checkout.totalPrice and
// checkout.currencyCode to the platform's own SDK
});
Shopify’s custom pixel code guide says to remove any HTML and replace script src= tags with JavaScript equivalents. Custom pixels run in a lax sandbox, and Shopify notes that not all pixel functionality works there, so check with the platform.
5. Know what the event does and does not do
A few details from Shopify’s docs explain most “the numbers don’t match” questions:
checkout_completedfires once per checkout, typically on the Thank you page. If the store shows a post-purchase upsell page, it fires on that page instead, and if that page fails to load, it does not fire at all.- The order ID is only available on
checkout_completed. - Customer email, phone and address need protected customer data access.
- Pixels track only with customer consent, so expect fewer events than the old scripts reported in regions where consent is required.
- New custom pixels require the Marketing and Analytics permissions by default.
- If the store uses a custom domain, the customer account domain should be a subdomain of the store domain, such as
account.example.com. Otherwise pixels and cookie consent do not work on the Order status page.
6. Remove duplicates, then compare
Shopify’s guidance is to disable the old script after the replacement works, to avoid duplicate events. It also says to remove pixel code from theme.liquid, checkout.liquid and additional scripts before adding a custom pixel. Then place test orders and compare each platform’s received purchases against Shopify’s orders for the same days.
Recover custom content
If the content is the same for everyone, or follows simple rules
Use blocks. Open the checkout editor, switch to the Thank you or Order status page, and add a block from an installed app. Shopify’s Checkout Blocks app offers static content and dynamic content with conditional rules. This covers most “show a message after purchase” needs without code.
If it depends on your own logic or data
Build a checkout UI extension. It lives in an app, renders in a target such as purchase.thank-you.block.render on the Thank you page or one of the Order status targets like customer-account.order-status.block.render, and the merchant places it in the checkout editor. Typical cases:
- delivery instructions that depend on product type or shipping method;
- a link to your own portal with the order number filled in;
- information from metafields or another system;
- a survey that writes answers to your own database.
UI extensions use Shopify’s components rather than free HTML, so plan the design around what the components offer. A custom app with this extension can be created in the Dev Dashboard.
A short checklist
- Copy any old additional scripts text still shown.
- List every tag, its platform and the fields it sends.
- Install platform apps for app pixels where they exist.
- Write custom pixels for the rest, subscribing to
checkout_completed. - Check consent settings and the customer account domain.
- Recreate content with blocks, or a UI extension where logic is needed.
- Disable old scripts, place test orders and compare numbers.
When to have it built for you
Often tracking comes back with the platform’s app and a few custom pixels. A custom app makes sense when the content depends on your own data, when several systems need the same purchase event, or when the old script did something no block covers. The team behind Storefleet Store Ops builds that kind of custom app; see our custom solutions page for what we take on, and when to build a custom Shopify app to decide whether you need one.
Two other 2026 changes often hit the same stores: Shopify Scripts moving to Functions and market-driven shipping for custom apps. If you are sending purchase data on to other systems, our integrations checklist covers what a reliable connection needs.
FAQ
Can I still paste code into additional scripts?
No. Since August 28, 2025, the additional scripts section in checkout settings is view-only, and checkout.liquid and additional scripts no longer run on the Thank you and Order status pages.
Why does my ad platform report fewer purchases than before?
Pixels only track with customer consent, so regions that require consent send fewer events. Also check that the old script was removed rather than running twice, that checkout_completed fires on your post-purchase page if you have one, and that the customer account domain is set up as a subdomain of your store.
Do I need Shopify Plus to customize the Thank you page?
No. Shopify says Thank you and Order status extensions and web pixels are available on all plans except Shopify Starter. Checkout UI extensions on the information, shipping and payment steps need Plus.
What is the difference between an app pixel and a custom pixel?
An app pixel comes from an installed app and is set up through that app. A custom pixel is code you add yourself in Settings > Customer events. Shopify recommends app pixels where one exists and notes that it does not support custom pixel code.
What if my store was upgraded automatically?
The old pages and their customizations were replaced. Copy any code still shown in the view-only additional scripts box, then follow the tracking and content steps above.