On 26 August 2026, Shopify auto-upgraded Thank you and Order status pages on every non-Plus store that had not upgraded manually. Anything in the Additional Scripts field stopped running. Google Ads, Meta, TikTok, GA4/GTM, and affiliate tags pasted there went silent, with no error message and no warning banner.
If you run a non-Plus Shopify store and your ad platforms show a sudden drop in purchase events this week, this is the likely cause. The fix ranges from a ten-minute pixel swap to a larger stack review, depending on what you had in that field and whether your tracking ever worked correctly in the first place.
Introduction
Shopify announced this deadline months ago. The Additional Scripts field has been view-only since August 2025, and the upgrade path through Customer Events has been available for over a year. Merchants who followed the prompts in Settings, Checkout, Configurations saw the notice and handled it.
The stores now in trouble are the ones where nobody clicked Upgrade, nobody checked if tracking still worked, and nobody realised the auto-upgrade was coming. That describes a lot of brands, especially those without a dedicated technical partner watching checkout settings.
This article explains what actually changed, how to check if you are affected, and what the fix path looks like depending on your stack. Everything here comes from public Shopify documentation and the observable behaviour of stores that went through the upgrade.
For Plus stores that went through this process a year earlier, the same lessons apply if you still have apps or scripts relying on deprecated checkout.liquid patterns. The checkout abandonment guide covers the diagnostic when conversions drop and funnel analytics look healthy.
If your tracking breakage sits alongside a broader stack of apps and integrations, the fix may connect to issues we cover in the hidden cost when twelve apps eat margins and the real cost of running a Shopify store. Tracking is one part of the checkout and post-purchase surface; the rest of the stack matters when the fix expands beyond a pixel swap.
What happened
Shopify runs a timeline for deprecating legacy checkout customisations. For non-Plus stores, the Thank you and Order status pages were the only surfaces that ever supported Additional Scripts. The Information, Shipping, and Payment checkout steps were never customisable via Liquid on non-Plus plans.
| Date | What changed | Who it affects |
|---|---|---|
| February 2025 | Apps can no longer create script tags on Thank you or Order status pages | All plans |
| August 2025 | Additional Scripts becomes view-only; Plus stores auto-upgraded | Plus stores |
| 26 August 2026 | Non-Plus stores auto-upgraded; Additional Scripts content removed | Basic, Shopify, Advanced |
The replacement is the Web Pixels API, which Shopify calls Customer Events in the admin. This is a sandboxed environment where tracking scripts subscribe to standard events (checkout_completed, page_viewed, add_to_cart, and others) rather than executing arbitrary JavaScript in the page.
Stores that upgraded before the cutoff kept their new pixel setup. Stores that did not upgrade had their Additional Scripts content removed with no migration. If you relied on that field for tracking, conversion events stopped firing the moment the auto-upgrade happened.
The upgrade cannot be reverted. Shopify's help documentation states this explicitly: stores that are auto-upgraded cannot return to the legacy pages.
Who is affected
Non-Plus stores with code in Additional Scripts. If you ever pasted a Google Ads conversion tag, Meta pixel, TikTok pixel, affiliate snippet, or custom JavaScript into Settings, Checkout, Order processing, Additional Scripts, that code no longer runs.
Stores using app script tags on post-purchase pages. Apps that injected tracking or UI via the ScriptTag API with a display scope of order_status or all stopped working on these pages. Some apps updated to use Customer Events or Checkout UI Extensions. Others did not.
Stores that never checked whether tracking worked. Shopify showed an upgrade notice in Settings, Checkout, Configurations for affected stores. If your team ignored that notice or assumed someone else handled it, the auto-upgrade applied.
Stores already on the new pages are fine. If you manually upgraded at any point since the option appeared, your tracking should still work (assuming the migration was done correctly). Check Settings, Customer events to confirm your pixels are active.
How to diagnose it
The symptom is usually a drop in reported purchase conversions on one or more ad platforms while Shopify order volume stays the same. Here is the diagnostic sequence.
Step 1: Check if you were using Additional Scripts
Go to Settings, Checkout. Look for the Order processing section. If you see "Additional scripts" with code in it, and you are on a non-Plus plan, that code is no longer executing.
If you do not see the field at all, your store has already been upgraded and the legacy scripts are gone.
Step 2: Check if Customer Events are active
Go to Settings, Customer events. You should see a list of app pixels and custom pixels. Each one should show a status (Active, Inactive, or Error).
If you see no pixels listed, you have no tracking on the post-purchase flow. If you see pixels but they show errors, check the error messages for missing permissions or configuration issues.
Step 3: Place a test order
The only reliable way to know if tracking fires is to test it. Place a real order (you can refund it afterwards) and check your ad platforms for the corresponding event.
Google Ads: In Conversions, Goals, Summary, look for recent conversion events. The event should appear within a few hours.
Meta Events Manager: Check the Events tab for Purchase events. Use the Test Events tool to see real-time events from your browser.
TikTok Events Manager: Look for CompletePayment events in the event history.
GA4: In Admin, Data Streams, select your stream, then Realtime or DebugView if you have debug mode on.
If orders appear in Shopify but purchase events do not appear in your ad platforms, your tracking is broken.
Step 4: Identify what was lost
If you have access to old admin screenshots, backups, or documentation, find out what code was in the Additional Scripts field. Common contents:
- Google Ads conversion tracking (
gtag('event', 'conversion', ...)) - Meta pixel purchase event (
fbq('track', 'Purchase', ...)) - TikTok pixel (
ttq.track('CompletePayment', ...)) - Google Analytics 4 purchase event
- Affiliate network postback scripts (Impact, ShareASale, AWIN, etc.)
- Custom JavaScript for order confirmation logic
The fix depends on what you need to restore.
Post-cutoff tracking diagnostic
How to fix it
The fix path depends on your stack complexity. For most stores, this is a ten-minute swap to native channel apps. For stores with custom conversion logic, deduplication requirements, or multiple tracking platforms, the work is larger.
Path 1: Native channel apps (ten-minute swap)
Shopify recommends native channel apps for major advertising platforms. These apps use the Web Pixels API correctly and stay updated when Shopify changes the event schema.
Google and YouTube channel: Install from the App Store. Configure your Google Ads and Analytics accounts. The app handles purchase events automatically.
Meta (Facebook and Instagram) channel: Install from the App Store. Connect your Meta Business account. The app uses the Conversions API for server-side tracking alongside browser events.
TikTok channel: Install from the App Store. Connect your TikTok Ads account.
After installing, place a test order and confirm events appear in each platform. If you previously had manual pixel code, you may see duplicate events during the overlap period; the native apps handle deduplication when configured correctly.
Path 2: Custom pixels for other platforms
For affiliate networks, analytics platforms, or custom conversion logic, add a custom pixel in Settings, Customer events.
- Go to Settings, Customer events, Add custom pixel.
- Give the pixel a name (e.g., "Affiliate postback").
- Paste the JavaScript code that subscribes to the
checkout_completedevent.
Custom pixels run in a sandboxed iframe. They can access standard Shopify analytics events but cannot access the DOM or run arbitrary scripts on the page. The event object includes order details like total price, line items, and customer email (if consented).
Example structure for a custom pixel:
analytics.subscribe('checkout_completed', (event) => {
const checkout = event.data.checkout;
// Send conversion data to your platform
// checkout.totalPrice, checkout.order.id, etc.
});
Shopify documents the available events and data in Customer events reference.
Path 3: Server-side tracking for reliability
If you need conversion data that survives ad blockers, use server-side tracking alongside browser pixels. The Meta Conversions API and Google Ads Enhanced Conversions both support server-to-server event transmission.
This typically involves:
- A Shopify app that listens to the
orders/paidwebhook - Server-side code that sends the conversion event to the ad platform's API
- Deduplication using the same event ID or order ID in both browser and server events
Server-side tracking is more work to set up but more reliable for attribution. Many of the native channel apps already do this.
When this becomes a stack problem
The Additional Scripts cutoff is a symptom of a larger shift. Shopify is moving checkout customisation away from arbitrary JavaScript toward structured, sandboxed extensions. This follows the same architectural pattern as Online Store 2.0, where Shopify deprecated older patterns in favour of sections, blocks, and metafields.
If your post-purchase flow involves:
- Checkout UI extensions that display order details, upsells, or surveys
- App integrations that depend on order data not available in standard events
- Custom attribution models that need line-item or discount data
- Multiple tracking platforms with conflicting deduplication logic
Then you are looking at architecture work, not a quick swap. The native apps cover the common case; everything beyond that requires mapping which systems need which data and in what format. This is the same class of foundation work we cover in the anatomy of a high-performance Shopify theme, where checkout and storefront architecture affect what merchants can configure without code.
| Scenario | Fix path | Effort |
|---|---|---|
| Single ad platform (Google or Meta) | Install native channel app | Low: under one hour |
| Multiple ad platforms | Install native apps, test each | Low to medium: a few hours |
| Affiliate network postbacks | Add custom pixel with correct event data | Medium: half day to one day |
| Server-side tracking required | App or custom integration for Conversions API | Medium to high: days |
| Complex attribution or deduplication | Stack audit, then integration work | High: scoped project |
When to get help
Stay in-house when the fix is installing one or two native channel apps and confirming test orders appear in each platform. That is a settings task, not engineering.
Bring in technical help when:
- You have more than three platforms that need tracking on the post-purchase flow
- Your tracking involves custom conversion values, line-item data, or discount attribution
- You need server-side tracking and do not have the infrastructure for webhook handling
- Apps on your store appear in the "Requires update by app developer" section of the upgrade report and the vendor has not shipped an update
- Your attribution model depends on data that standard Customer Events do not expose
A Shopify stack audit maps who owns what: which tracking belongs in native apps, which needs custom pixels, which needs server-side work, and which apps need replacing. For stores that had checkout UI or order-status customisations beyond tracking, the fix sits alongside theme development or app architecture work.
Conclusion
The 26 August 2026 cutoff removed Additional Scripts from non-Plus stores and auto-upgraded the Thank you and Order status pages. If your tracking lived in that field, it stopped firing without an error message.
Check Settings, Customer events to see if you have active pixels. Place a test order and confirm purchase events appear in your ad platforms. For most stores, installing the native Google, Meta, and TikTok channel apps restores tracking in under an hour. For stores with affiliate networks, custom conversion logic, or server-side requirements, the work scales up from there.
If you are looking at multiple platforms, deduplication, or app dependencies that the upgrade broke, book a stack assessment and I will map the fix path against your actual checkout and tracking setup.
