We already migrated for the June 30, 2026 Scripts deprecation. Does the separate August 26, 2026 pixel deadline still affect our reporting?

Why clearing one did nothing for the other

A Scripts-to-Functions migration rewrites commerce logic: discounts, shipping rate presentation, payment method ordering. A pixel migration moves observation: the code that watched what happened and told a third party about it.

They have never been the same system, and in most mid-market organizations they do not even have the same owner. Scripts belonged to whoever owned promotions and checkout behavior. Pixels belong to marketing. A project that closed the first gap was usually run, staffed and signed off by people who were never asked about the second.

The third row is the one this page is about, and it is the row nobody's Scripts project touched.

What stopped firing, and why nobody got an alert

This is the hard part. None of these failures throws an error a merchant sees. The checkout still works. Orders still complete. The dashboards just get quieter, and quieter reads as "a slow month" for longer than anyone would like to admit.

The usual casualties, in the order we find them:

1. Anything in the "Additional scripts" box on the order status page. Historically this was where a Google Tag Manager container, a conversion pixel, an affiliate tag or a post-purchase survey got pasted. Shopify states plainly that "checkout.liquid and additional scripts were sunset for the Thank you and Order status pages on August 28, 2025" (shopify.dev, September 2026).
2. App script tags, including from apps still installed and still billing you. Shopify blocked app creation of ScriptTags on Thank you and Order status pages from 1 February 2025, existing ones stopped for Plus on 28 August 2025 and for non-Plus on 26 August 2026 (shopify.dev, September 2026). The app is present in your admin. Its tracking is not present on the page.
3. Anything that wrote to the order status page DOM, including content injected through the old Shopify.Checkout.OrderStatus.addContentBox pattern. There is no equivalent in the pixel sandbox, because the sandbox "can't render user interface elements" (Shopify Help Center, September 2026).
4. Affiliate and partner tags. These are frequently owned by a third party who pasted them once, years ago, and who is not on your migration distribution list.
5. The second checkout path. A subscription platform, a post-purchase upsell, or a separate thank-you page. Each one needed its own migration and each one is a different ticket.

What Customer Events does and does not replace

The last two rows are the ones that surprise finance. Even a correctly migrated pixel is now conditional. Its event volume depends on your market-level consent configuration and on how each pixel is classified in the pixel manager, which means a perfect migration can still produce a step change in reported conversions, and the step change is legitimate rather than a bug.

There is one more line worth quoting because it sets expectations about support. Shopify describes custom pixels as an advanced feature that is "unsupported by Shopify," and states that "compliance with applicable laws, consents, code security, troubleshooting, and updates are your responsibility" (Shopify Help Center, September 2026). Whatever you moved into a custom pixel, you now own end to end.

How to verify, in that order, inside a week

1. Reconcile one closed window. Take a full week that sits entirely after your store's script-tag sunset date and compare Shopify's order count against each ad platform's reported conversions and against your analytics property. Do the same for an equivalent week from before. You are looking for a channel where the ratio moved, not for an absolute match.
2. Open the pixel manager and read every entry. Confirm each active pixel, its type, and whether it is flagged as a data sale. That flag is a live switch on whether the pixel runs for opted-out customers.
3. Check consent configuration per market, because the consent requirement is configured by country and region, and a market you enabled since the last review may be collecting less than you think.
4. Place a real test order and watch the network. Not a draft order. A real one, through the real checkout, on the real theme.
5. List every installed app that claims to track something and confirm each one now ships an app pixel rather than a script tag. Apps that never updated are the quiet failure.
6. Audit the second checkout path if you have a subscription platform or a post-purchase upsell.
7. Write down what each dashboard is supposed to show before you look at it, so the reconciliation is a test rather than a rationalization.

When NOT to act on what you find

• When the gap is one week old. Analytics processing is not instantaneous, and a single week of data is not a finding.
• When the affected channel is not being optimised against. Fix it, but do not stop the quarter for it.
• When the cause is consent. That is a working system, not a broken one, and re-instrumenting around it is the wrong response to the wrong problem.
• When nobody has defined a conversion. If marketing and finance do not agree on what counts, no migration and no audit resolves the disagreement.

This page describes product behavior and migration mechanics. Consent configuration and data-sale classification carry legal obligations that vary by jurisdiction; confirm your own position with counsel.