We already migrated for the June 30, 2026 Scripts deprecation. Does the separate August 26, 2026 pixel deadline still affect our reporting?
Short answer
Yes, the pixel deadline for the Thank you and Order status pages still affects your reporting, because a Scripts-to-Functions migration moved checkout logic and never touched tracking. Shopify Scripts ran only on Shopify Plus (Shopify Help Center, October 2026). Plus stores lost script tags there on 28 August 2025, and every other plan on 26 August 2026 (shopify.dev, October 2026).
- Script tags stopped on Shopify Plus
- 28 August 2025On the Thank you and Order status pages. Shopify Scripts ran only on Plus, so a store that migrated Scripts hit this date, not 26 August 2026 (Shopify, October 2026).Sources: Shopify developer docs (checkout.liquid); Shopify Help Center (Setting up quantity rules and volume pricing in B2B)
- Script tags stopped on other plans
- 26 August 2026Every non-Plus plan. It was also the non-Plus deadline to upgrade the Thank you and Order status pages, and stores that missed it were upgraded automatically (Shopify, October 2026).Sources: Shopify developer docs (Order status script tags); Shopify Help Center (Non-Plus: Upgrading and replacing your Thank you and Order status pages, Upgrading and replacing your Thank you and Order status pages)
- Shopify Scripts
- Deactivated as of 30 June 2026Per Shopify's Script Editor page and changelog. Shopify's B2B quantity rules page says 28 August 2025 instead; both agree Scripts no longer run (Shopify, October 2026).Sources: Shopify Help Center (Shopify Scripts and the Script Editor app, Setting up quantity rules and volume pricing in B2B); Shopify Changelog (Shopify Scripts deprecation: editing ends April 15, execution ends June 30, 2026)
- What tracks on those pages now
- Web pixels in Customer eventsApp and custom pixels load on the Thank you and Order status pages. They can't scrape the page or render content, and wait for consent where it is required (Shopify, October 2026).Sources: Shopify Help Center (Pixels overview); Shopify developer docs (Order status script tags)
Deploi’s call
Yes: two migrations, two owners, and clearing one clears nothing on the other. We scored checkout tracking and pixels CUSTOMIZE: buy the pixel delivery, own the event contract. The Scripts work fixed checkout logic. The pixel deadline moved your measurement into a sandboxed runtime with consent gating attached, and those are unrelated projects that happened to have adjacent dates (Deploi verdict, October 2026).
CustomizeAudit and rebuild the tracking layer when
- A Google Tag Manager container, conversion pixel or affiliate tag sat in the Additional scripts box on the Thank you or Order status page.
- Ad-platform conversions moved against Shopify's order count after your store's script-tag date: 28 August 2025 on Plus, 26 August 2026 on other plans (shopify.dev, October 2026).
- Paid acquisition is a meaningful share of revenue: Deploi's checkout tracking record scores that CUSTOMIZE, an app for delivery plus an audit you own.
WaitSpend nothing new on tracking while
- Every tag already runs as an app pixel or custom pixel, because pixels load on the Thank you and Order status pages (Shopify Help Center, October 2026).
- The drop traces to consent: in markets that require it, web pixels wait for the visitor's permission (Shopify Help Center, October 2026).
- Paid acquisition is a small share of revenue. The same record scores that WAIT, because the free Google & YouTube and Facebook & Instagram channel apps cover baseline pixels.
Basis: Should You Build or Buy Checkout Tracking & Pixels on Shopify?, our Build vs. Buy decision record, scored CUSTOMIZE.
Why didn't your Scripts migration fix your tracking?
Your Scripts migration didn't fix tracking, because Shopify Scripts and script tags were different surfaces doing different jobs. Shopify Scripts ran checkout logic: discounts, shipping rates and payment methods. Script tags and the Additional scripts box on the Thank you and Order status pages ran tracking and post-purchase content. So a Scripts-to-Functions migration rewrote the logic and left the tracking where it was.
| Retired surface | What it ran | Where it went |
|---|---|---|
| Shopify Scripts | Discount, shipping and payment logic | Shopify Functions |
| checkout.liquid | Checkout page layout on Shopify Plus | Shopify Extensions in Checkout |
| Script tags and additional scripts used for tracking | Analytics tags and conversion pixels | Web pixels in Customer events, Shopify's pixel manager |
| Script tags and additional scripts used for content | Surveys, review prompts and post-purchase offers | Checkout and customer account user interface (UI) extensions, added as blocks |
Deploi's Scripts-to-Functions record covers the first row. The tracking and content rows usually belonged to marketing, not to whoever owned promotions, which is why the team that signed off the Scripts work was rarely asked about them.
When did Scripts and script tags stop on your store?
Script tags on your Thank you and Order status pages stopped on 28 August 2025 on Shopify Plus, and on 26 August 2026 on every other plan (shopify.dev, October 2026). Shopify Scripts had stopped by 30 June 2026 at the latest (Shopify Help Center, October 2026). Scripts ran only on Plus (Shopify's quantity rules page, October 2026), so a store that migrated Scripts was on Plus, and its script-tag date was 28 August 2025. That means 26 August 2026 reaches you only through any non-Plus stores you run. Every checkout retirement date by plan has its own answer.
What stopped firing on the Thank you and Order status pages?
Every app script tag and Additional scripts tag on the Thank you and Order status pages has stopped firing. Shopify upgraded every store that missed the 26 August 2026 deadline automatically (Shopify Help Center, October 2026), and an upgrade replaces old customizations (Shopify Help Center, October 2026). Nothing alerted you, because checkout and orders kept working. The usual casualties, in the order we check them:
- Tags in the Additional scripts box, such as a Google Tag Manager container, a conversion pixel or a survey. Shopify sunset additional scripts on these pages on 28 August 2025 (shopify.dev, October 2026). On non-Plus plans the box went view-only that day (Shopify Help Center, October 2026).
- Script tags from apps you still pay for. Shopify stopped apps creating script tags for the Order status page on 1 February 2025 (shopify.dev, October 2026). The app is in your admin; its tag is not on the page. Stores that never installed a custom pixel are exposed through exactly this route.
- Content written onto the page, such as a review prompt or post-purchase offer. Web pixels can't render anything, so that content now needs a customer account user interface (UI) extension (shopify.dev, October 2026).
- Affiliate and partner tags, often pasted years ago by a partner who was never on your migration list.
- A second checkout path, such as a subscription platform, which needed its own migration.
What can web pixels not do that script tags could?
Unlike script tags, web pixels in Customer events, Shopify's pixel manager, can't read the page, show anything to the customer, or fire without consent where a market requires it. Web pixels still send Shopify's standard events.
| Job | Web pixels in Customer events |
|---|---|
| Purchase and funnel events | Yes: 15 standard events, including checkout_started and checkout_completed |
| Delivery to a vendor | Yes: app pixels in a strict sandbox, a web worker with no page access; custom pixels in a lax sandbox, an iframe cut off from the page |
| Reading the page | No: no scraped events, metadata, email addresses or outbound clicks, and no scrolling or heatmaps |
| Showing anything to the customer | No: no buttons, forms, banners or modals |
| Firing without consent | No: in markets that require consent, only with the visitor's permission |
| Data-sale pixels for opted-out customers | No, unless the pixel supports limited data use |
The consent rows surprise finance. Pixel event volume now follows each market's consent setting, so a correct migration can still lower reported conversions. New pixels require Marketing and Analytics permissions by default (Shopify Help Center, October 2026). Custom pixels are "unsupported by Shopify", and Shopify makes compliance, troubleshooting and updates your responsibility (Shopify Help Center, October 2026). Server-side delivery doesn't lift consent either, as what server-side tracking can't fix explains.
How do you check your reporting now?
Check your reporting by reconciling Shopify's order count against every platform, then reading what each pixel is allowed to send, so you know what broke before you buy anything. Deploi's checkout tracking record puts this audit first, at CUSTOMIZE.
- Reconcile two closed weeks. Your store's script-tag date was 28 August 2025 on Plus or 26 August 2026 on other plans (shopify.dev, October 2026). Compare Shopify orders with each ad platform's conversions and your analytics for a full week after it and one before it. Look for the channel whose ratio moved.
- Read each pixel's privacy settings in Settings > Customer events. An app pixel's customer privacy settings are set by its developer and can't be changed, so a correctly installed pixel can still skip some customers (Shopify Help Center, October 2026).
- Check consent settings per market, because a market added since your last review may collect less than you expect.
- Place a real test order on the live checkout and watch which events fire, for example with the Shopify Pixel Helper.
- Write down what each dashboard should show before you open it, so the check is a test.
When should you leave a tracking gap alone?
Leave a tracking gap alone when fixing it would change no decision, or when the gap is consent working as designed.
Consent and data-sale settings carry legal duties that vary by jurisdiction, so Shopify tells merchants to consult their own legal counsel (Shopify Help Center, October 2026).
Deploi’s point of view
Our own position, from building on Shopify. Kept apart from the sourced facts above.
- Where we disagree
- The category framed 26 August 2026 (28 August 2025 on Plus) as a deadline you either met or missed. It is better read as the date your measurement moved into a runtime with different rules, and the work does not end when the pixel is registered. Consent gating, data-sale classification and the sandbox's refusal to read the page are permanent properties of the new system, not transition costs.
- Where we look first
- In our judgment, the likeliest casualty is a custom checkout or order-status event that nobody re-registered, because the person who pasted it has left and the app that replaced it was assumed to cover it. Next is an affiliate tag owned by a partner who was never on the migration list.
Decision records behind this answer
What we’ve built
When this answer changes
- Shopify changes the events web pixels receive or loosens the pixel sandbox, for example letting pixels read the page.
- Shopify reconciles its Help Center pages on when Shopify Scripts ended.
- Shopify moves the 1 March 2027 date when app script tags stop running on storefront pages.
- Shopify changes its consent defaults for pixels, such as the permissions new pixels require.
- You add a market that requires consent, which changes how many events your pixels send.
Follow-up questions
If you're not the typical case
- Does the legacy-script removal deadline affect stores that never installed custom checkout pixels in the first place?
Yes, stores that never wrote a custom checkout pixel were still affected, because apps added script tags to the Order status page for them.
What to do next
- Should marketing pause paid-spend optimization decisions for a period after the Aug 26 migration until reporting numbers are re-validated?
Marketing keeps paid spend on after the 26 August 2026 non-Plus script-tag cutoff (shopify.dev, October 2026) and pauses only structural changes.
Related questions
- Does the checkout.liquid shutdown affect stores on every Shopify plan, or only Shopify Plus stores?
The checkout.liquid shutdown hit Shopify Plus stores only, because checkout.liquid, the theme file for custom checkout code, was a Plus-only layout (shopify.dev, October 2026).
- What does server-side tracking NOT fix, even after a full and correct implementation?
Server-side tracking, even correctly implemented, does not fix declined consent, 48-hour deduplication windows or ad platforms' attribution models.
- Do we need to budget for a tracking-app plan upgrade (e.g., to a server-side tier) at the same time we migrate to Checkout Extensibility?
A tracking-app upgrade belongs in the migration budget only when purchase tracking sat in the Additional scripts box or a script tag, because both stopped on the Thank you and Order status pages (shopify.dev, October 2026).
- How many tracking pixels and third-party scripts is 'too many' before they measurably hurt Shopify conversion rate?
Third-party scripts hurt Shopify conversion when they block the main thread, not at a set count, and neither Shopify nor Google publishes a safe number.
Sources
Every figure on this page traces to one of these. Official and vendor pages are checked on the date shown; Deploi records are our own published decisions.
- Shopify developer docs, Order status script tags
- Shopify Help Center, Shopify Scripts and the Script Editor app
- Shopify Changelog, Shopify Scripts deprecation: editing ends April 15, execution ends June 30, 2026
- Shopify Help Center, Setting up quantity rules and volume pricing in B2B
- Shopify developer docs, checkout.liquid
- Shopify Help Center, Non-Plus: Upgrading and replacing your Thank you and Order status pages
- Shopify developer docs, Web Pixels API standard events
- Shopify developer docs, About web pixels
- Shopify Help Center, Pixels overview
- Shopify Help Center, Custom pixels
- Shopify Help Center, App pixels
- Shopify developer docs, About Thank you and Order status page customization
- Shopify Help Center, Upgrading and replacing your Thank you and Order status pages
- Deploi Build vs. Buy, Should You Build or Buy Checkout Tracking & Pixels on Shopify?
- Deploi Build vs. Buy, Should You Build or Buy Your Shopify Scripts-to-Functions Migration?