Some time in September or October, a lot of Shopify store owners opened Meta Ads Manager or Google Ads and saw something that made no sense. Sales in Shopify looked normal. Ad platform conversions had fallen off a cliff. ROAS calculations were suddenly fiction, campaigns that had optimized fine for a year were starving for data, and nobody had changed anything.
Something had changed, though. On August 26, 2026, Shopify auto-upgraded the remaining stores to checkout extensibility, and the Additional Scripts box, where years of tracking code had quietly lived, stopped executing. No error message. No warning banner on the orders page. The pixels just went dark.
As a Shopify developer focused on speed and conversion, this is the repair job I have seen most often since the upgrade. This guide is the exact process: how to audit what you lost, how to rebuild the events with Web Pixels and customer events, and how to test the rebuild so you can trust your numbers again.
What Actually Changed on August 26, 2026
For years, Shopify gave store owners a free text field in Settings, Checkout called Order status page additional scripts. Developers pasted everything into it: Meta and TikTok pixels, Google Ads conversion tags, Google Tag Manager containers, affiliate tracking, post-purchase surveys, and custom thank you page code. It was never a good system, but it worked, so stores accumulated years of it.
Checkout extensibility replaced that world. Checkout and the thank you and order status pages are now built from apps, checkout UI extensions, and Shopify’s pixel system. The Additional Scripts field was deprecated as part of that move, and when Shopify auto-upgraded the stores that had not migrated themselves, the code in that field simply stopped running.
This was the second half of the same platform cleanup that retired Shopify Scripts in June 2026, which I covered in the Shopify Scripts to Functions migration guide. Scripts were the checkout logic. Additional Scripts were the tracking and thank you page layer. If your store used either one, the deadline you needed was not a single date, it was both of them.
One important detail: the upgrade did not break your store. Checkout works, orders come in, customers see a perfectly normal thank you page. It broke your measurement. That is exactly why so many stores discovered it weeks late, usually when ad performance reviews stopped matching the bank account.
The Symptoms of Dead Tracking
Broken post-upgrade tracking has a recognizable fingerprint. Check for these before you assume your ads or your products are the problem:
- Meta and TikTok purchases drop sharply from late August while Shopify orders stay steady. The platforms are not broken, they are blind.
- GA4 revenue no longer matches Shopify revenue, and the gap starts on a specific date rather than drifting gradually.
- Google Ads conversions undercount, so smart bidding shrinks budgets on campaigns that were actually working.
- Your thank you page extras vanished: post-purchase survey widgets, affiliate scripts, and review prompts that used to load after checkout no longer appear.
- Tag Assistant or the Meta Pixel Helper shows nothing firing on the order confirmation page, even though the same tools fire fine on product pages.
If two or more of those match your store, do not touch your ad campaigns yet. Fix the data first. Optimizing campaigns against broken conversion data makes the algorithms worse, not better, and the lost weeks are usually a tracking problem, not a marketing problem.
Step 1: Audit What You Actually Lost
Do not start by installing new pixels. Start by building a list of what the old setup was sending, so the rebuild covers everything and duplicates nothing.
Compare platform data against Shopify orders
Pick a clean window, for example September 1 to September 30, and compare three numbers: orders in Shopify, purchases in Meta Events Manager, and transactions or key events in GA4. Then do the same comparison for July, before the upgrade. If July matched within a normal margin and September does not, you have a date-stamped break, and you know exactly when it happened. Write down the shortfall per platform. That list becomes your rebuild checklist.
Inventory every script that lived in Additional Scripts
The field no longer executes, but in most stores the old code is still documented somewhere: ask whoever built the store, search old emails and project docs for pixel IDs, and check whether your agency kept a copy. Common residents of that box were the Meta pixel purchase event, TikTok Events, Google Ads conversion tags, a GTM container, affiliate networks like ShareASale or Refersion, and survey tools. Every item on that list needs a new home, or a deliberate decision to retire it.
Check for doubles as well as gaps
The messiest stores I audit are not the ones with no tracking. They are the ones where someone panicked in September, installed an app pixel on top of a surviving custom setup, and now Meta receives every purchase twice. Before rebuilding, open Settings, Customer events in your Shopify admin and list every pixel already there. Then check the sales channel apps (Meta, Google and YouTube, TikTok) and note which ones have data sharing turned on. One source per event per platform is the rule.
Step 2: Rebuild Tracking the Way Shopify Intends Now
There are three lanes for tracking on modern Shopify, and a clean rebuild uses them in this order.
Lane 1: Official app pixels first
For the big platforms, use the official sales channel apps: Meta (Facebook and Instagram), Google and YouTube, and TikTok. Connecting them creates managed app pixels that fire the standard events, including checkout and purchase, and they are maintained by the platforms when Shopify changes something. For most stores, this one step restores the majority of what Additional Scripts used to send, including the server-side feeds (Meta Conversions API and Google enhanced conversions) that make ad data resilient when browsers block cookies.
Lane 2: Custom pixels for everything else
Anything without an official app, affiliate networks, survey tools, secondary analytics, or your own internal events, goes into a custom pixel under Settings, Customer events. Custom pixels are written against Shopify’s Web Pixels API. They run in a sandboxed environment, subscribe to standard events like page_viewed, product_viewed, product_added_to_cart, checkout_started, and checkout_completed, and send the data wherever it needs to go.
A minimal purchase pixel looks like this:
analytics.subscribe("checkout_completed", (event) => {
const checkout = event.data.checkout;
// Send the purchase event to your platform here,
// using checkout.token as the unique order reference
// and checkout.totalPrice.amount as the value.
});Two properties of the sandbox matter for your expectations. First, a custom pixel cannot freely read the page DOM the way old scripts could, so copy-paste snippets written for the Additional Scripts era usually fail silently and need to be rewritten against the standard events. Second, pixels respect the consent settings in Settings, Customer privacy, which is a feature: a correctly built pixel will not fire for a visitor who declined tracking in a region where consent is required.
Lane 3: Server-side events for the purchase that matters most
Browser pixels alone under-report, because ad blockers and browser privacy features eat a share of events. For the purchase event, pair the browser event with a server-side feed (Conversions API on Meta, enhanced conversions on Google, Events API on TikTok) and send the same unique reference with both, so the platform can deduplicate instead of double counting. The official apps in lane 1 handle most of this for you when data sharing is set to its maximum level. Where you build custom, deduplication is your responsibility, and skipping it is how stores end up reporting more conversions than orders.
Step 3: Test the Rebuild Like a Developer
A rebuild is not finished when the code is pasted in. It is finished when a real test order produces the right event, with the right value, exactly once, on every platform.
- Use Shopify’s pixel helper (Settings, Customer events, the test and debug tools on each pixel) to confirm your custom pixels load and subscribe without errors.
- Place a real test order with a discount code so you can find it later, and complete it through the actual checkout, not a draft order.
- Verify in each platform’s own tester: Meta Test Events, the TikTok Events Manager test view, and GA4 DebugView. Check the event name, the value, the currency, and that the reference matches the Shopify order.
- Check the counts three days later. One test order proves the pipe works. Three days of platform purchases tracking within a sane margin of Shopify orders proves the rebuild is complete.
- Repeat the test for checkout_started, not just purchase. Mid-funnel events are what ad platforms optimize prospecting campaigns against, and they are the ones most often missing after a rushed rebuild.
While you are in the checkout settings, it is worth confirming the checkout itself is on the current version and configured properly. Tracking tells you what happened, but the checkout experience decides how much of it happens, which is the other half of the work in my Shopify checkout optimization guide.
Rebuild Mistakes That Quietly Wreck Your Data
- Pasting old Additional Scripts code into a custom pixel unchanged. The sandbox is a different environment. Old snippets that touch the DOM or rely on Shopify’s old checkout objects break, usually without any visible error.
- Loading Google Tag Manager the old way. A GTM container that was injected by Additional Scripts died with it. GTM now needs to be loaded through a custom pixel, and your tag configuration needs checking against the standard events, not the old data layer pushes.
- Double firing. App pixel plus custom pixel plus a theme-level snippet all sending purchase is the most common post-repair state I see. It inflates ROAS and teaches the ad platforms to chase fake performance.
- Forgetting consent behavior. If your pixel ignores the Customer Privacy settings, you may be tracking visitors who declined, which is a compliance problem in the EU and UK, not just a data problem.
- Declaring victory after one event fires. Firing is not the same as firing with the correct value, currency, and deduplication reference. Most bad rebuilds pass the first test and fail this one.
When This Stops Being a DIY Fix
If your tracking was only ever the standard Meta and Google setup, the official apps may genuinely fix you in an afternoon. It stops being DIY when your old setup included GTM with custom triggers, multiple ad platforms, affiliate networks, subscription or post-purchase events, or server-side feeds that were hand-built. In those cases the rebuild is a small development project: an audit, a pixel architecture that avoids duplicates, and proper testing across every platform.
That is the work I do. If your store lost its tracking in the upgrade and the numbers still do not add up, you can hire a Shopify developer to audit what died and rebuild it properly, rather than stacking another app on top and hoping.
FAQs
Why did my Meta pixel stop reporting purchases on Shopify?
Because the purchase event almost certainly fired from code in the Additional Scripts field, and that field stopped executing when Shopify auto-upgraded your store to checkout extensibility on August 26, 2026. The rest of your pixel may still work on product and cart pages, which is why the drop looks partial and confusing. The fix is to reconnect Meta through the official app pixel or rebuild the event as a custom pixel using the checkout_completed standard event.
Can I still use Google Tag Manager on Shopify checkout?
Yes, but not the way you used to. The old method, injecting the GTM container through Additional Scripts, is gone. GTM now loads through a custom pixel in Settings, Customer events, and your triggers should be rebuilt on Shopify’s standard events. Expect to rework any tags that relied on the old checkout page structure.
Do Web Pixels slow down my store?
No, not in any way your customers can feel. Custom pixels run in a sandboxed iframe managed by Shopify, isolated from your theme, so a broken pixel cannot break your storefront and the performance cost is minimal compared to the old pattern of pasting arbitrary scripts into checkout. Your theme and apps remain the things that decide store speed.
Is this different for Shopify Plus stores?
The end state is the same: app pixels, custom pixels, and checkout extensions. Plus stores were pushed through the upgrade earlier and also have access to checkout UI extensions for the visible parts of checkout and the thank you page, like post-purchase offers and status page blocks. The tracking rebuild itself, events through the pixel system, is identical on every plan.
Will my historical conversion data come back?
No. Events that never fired cannot be recovered, and the gap in your ad platform history between the upgrade and your rebuild is permanent. That is exactly why the rebuild should happen before you judge any campaign on post-August data, and why the platforms need a clean run of correct data before their bidding settles again.
Tracking still broken after the upgrade? I am Hamza Taj, a Shopify developer focused on speed and conversion. I audit what the August upgrade killed, rebuild your events with app pixels, custom pixels, and server-side feeds, and test every platform until the numbers match your orders. Hire Shopify Developer to get your data back, or view my Shopify projects first to see the standard of work.
Sources and how this article was made
The upgrade timeline and pixel system details in this guide are checked against Shopify’s developer documentation for Web Pixels and customer events, the Shopify changelog for checkout extensibility, and current migration guides from WeltPixel, Zapolu, and Jean Manzo covering the Additional Scripts sunset. No store data or client figures are published here; the audit steps are the ones I run on real repair projects.