The Shopify script tag deprecation means any app feature or tracking code that still loads through a script tag stops running on your storefront on 1 March 2027. Since 1 October 2026, apps can't create or update script tags, so whatever sits on your store now is frozen in place until it switches off.
Shopify announced the change in its developer changelog on 24 August 2026, which gave app developers about five weeks before the first deadline. Some developers said in Shopify's own forum that the notice never showed up in their dashboard, so don't assume the people behind your apps have warned you. When this breaks, it breaks quietly: a review widget stops loading, a chat bubble vanishes, or an ad account stops seeing purchases while orders keep arriving.
What did script tags do on a Shopify store?
A script tag is a pointer from Shopify to a JavaScript file hosted by an app. Shopify's API reference describes it as remote JavaScript code loaded into the pages of a shop's storefront or the order status page of checkout. When you installed an app, the app registered its script and Shopify injected it into your pages, with nobody touching the theme files.
That made installs fast. Reviews, chat, pop-ups, upsell offers, loyalty badges and conversion tracking could all go live minutes after you clicked Install, and Shopify removed an app's script tags automatically when you uninstalled it.
The weakness was visibility. Script tags never appeared in the theme editor, so you had no screen listing what was loading and no switch to turn any of it off. Shopify brought in a replacement, theme app extensions, in 2021. Script tags kept working next to it for five more years, and plenty of older installs never moved.
What stopped working on 1 October 2026
From 1 October 2026, apps can't create new script tags or change existing ones. The scriptTagCreate and scriptTagUpdate mutations in the GraphQL Admin API now return an error, and the older REST ScriptTag resource rejects POST and PUT requests. The block covers every API version, including old ones, so an app pinned to a 2023 version can't use that to buy time.
Your storefront looked the same the next morning. Existing script tags kept running, and apps can still read and delete them. The difference is that any app installed after that date has to use the newer methods from day one, and any app still running on a script tag can no longer adjust it.
The order status page ran on an earlier clock. Script tags stopped running there for Shopify Plus stores on 28 August 2025 and for all other stores on 26 August 2026. If a post-purchase survey or tracking script disappeared from that page in late August, that's the reason. The replacement there is a customer account UI extension or a web pixel.
What stops on 1 March 2027
On 1 March 2027, Shopify stops injecting script tags into storefronts. Anything that still depends on one stops loading that day. Customers won't see an error message. They'll see a page without the feature.
Don't count on the admin to warn you either. Shopify planned a banner for merchants installing apps that still rely on script tags, then dropped the idea. Once the date passes, leftover script tag records do nothing at all.
Consider a store spending $4,000 a month on paid social, with purchase tracking still delivered by an old app's script tag. On 1 March the tag goes silent. Shopify keeps recording sales, the ad platform's reported purchases drop toward zero, and campaigns set to bid for purchases lose the signal they were trained on. Someone then spends a week working out why the ads stopped "working" when the ads were never the problem.
Why Shopify is retiring script tags
Shopify's stated reason is short: script tags run JavaScript directly on a storefront without showing up in the theme editor, which makes them hard for merchants to find and control. The replacements put each app's storefront code behind a switch you can see.
Privacy is the second reason. Web pixels run in a sandbox and follow your store's customer privacy settings. In regions where shoppers must consent to tracking, an app pixel's code runs only after consent is given, and Shopify then replays the events it held back. A script tag ran whatever JavaScript the app supplied.
Which stores and apps are affected
Every store with an app that loads storefront code through a script tag is affected, whatever its plan or theme. In Shopify's terms, that's any script tag with a display scope of online store. Four situations carry most of the risk:
- Apps installed years ago. Shopify gives developers no programmatic way to switch on the replacement for existing users. An app that has already moved can keep running its old script tag in your store until you turn the new version on.
- Ad conversion or analytics tracking that runs through an app's own script rather than through a pixel.
- A custom app created in the Shopify admin by a freelancer or an in-house developer. Those apps can't use app extensions at all, according to Shopify's storefront script tag guide, so their code has to move into the theme through a custom Liquid block or the theme code editor.
- A theme change planned before March 2027. App embeds are switched on per theme, so a new theme starts with every one of them off.
If every app you use came from the Shopify App Store and already shows up in your theme editor, your risk is lower. Shopify requires App Store apps that integrate with themes to use theme app extensions instead of script tags. Older installs are the exception, and those are the ones to check first.
How to audit your apps before the deadline
Most of this takes clicks and emails, not code. Work through it in order:
- List every app that changes what shoppers see or records what they do: reviews, chat, pop-ups, upsells, loyalty, analytics and ad tracking. Apps that only work inside your admin can come off the list.
- Open your theme editor and click the App embeds icon in the sidebar, as shown in Shopify's help page on app embeds and blocks. Any app from your list that appears there has a replacement ready. If its toggle is off, that app may still be running on a script tag.
- Open Settings and go to Customer events, where Shopify lists the app pixels and custom pixels connected to your store. Tracking apps that have moved to web pixels appear there.
- Email the developer of every app that shows up in neither place. Ask two things: does the app still load anything on our storefront through a script tag, and what do we need to switch on to replace it? Script tags belong to the app that created them, so the developer is the one who can confirm.
- Check your admin for custom apps built only for your store, and ask whoever built them to move the code into your theme.
- Switch each replacement on in your published theme, then ask the developer to delete the old script tag. Running old and new together can double-count analytics or show a widget twice.
- Repeat the App embeds check after any theme change.
Give yourself until the end of January 2027 for the emails and checks. That leaves February for developers to ship fixes and for you to compare a week of tracking numbers before the switch-off.
Moving storefront features to app embed blocks
App embed blocks replace script tags for anything that floats over your pages or runs in the background: chat bubbles, pop-ups, badges, and code shoppers never see. Developers ship them inside a theme app extension, and they show up in your theme editor under App embeds with an on and off toggle.
The step that catches store owners out is that app embeds start switched off. An app can't turn its embed on for you. The better apps send a link that opens the theme editor with their embed ready to activate, so the job is one toggle and a save.
A vintage theme doesn't need a rebuild for this. Shopify's help documentation says app embeds can be used with any theme version. App blocks, the kind that sit inside a page section, are the ones that need a compatible theme.
Moving tracking to web pixels
If a script only collects analytics or conversion data, Shopify points developers to web pixels rather than app embeds. A pixel listens to the customer events Shopify publishes as shoppers browse and buy, then passes that data to the analytics or ad platform. App pixels need no action from you once the app ships one.
Developers face one real constraint. App pixels run in a strict sandbox with no access to the page itself, so older tracking code that reads or edits the page won't work unchanged and has to be rewritten. Custom pixels, which a developer adds in the pixels manager, run in a looser sandbox inside an iframe. Older pixel code runs there, but it still can't reach the main page. Shopify recommends choosing an app pixel over a custom pixel wherever one exists, for security and automatic updates.
Watch the week you switch. If the old script tag and the new pixel both fire, purchases get counted twice. Compare orders in Shopify with purchases in the ad platform for the same seven days: if the platform suddenly reports close to double, both are still running.
What you gain and what you give up
The gains are control and consent. Every app's storefront code now sits behind a toggle in the theme editor or a listing on the Customer events page, so you can see what runs and switch off what you don't want. Pixels respect your privacy settings, and app embeds work on old and new themes alike.
The costs land on setup. Each embed needs a manual switch, on each theme. Existing installs don't migrate themselves. Tracking code that touched the page needs rewriting for the sandbox, and a custom admin app means paying a developer to move its code into the theme.
On balance, the change favours store owners. The extra clicks happen once. A store where every script has a visible switch is easier to debug and easier to hand to a new developer without a week of detective work.
Who needs to act on the Shopify script tag deprecation
Act now if your store has apps installed years ago, runs ad tracking through an app, uses a custom admin app, or is changing themes before March. Those are the stores where a script tag is most likely still loading something that matters.
You can relax if every storefront app on your list appears under App embeds with its toggle on, and every tracking tool appears on the Customer events page. That store has already moved, whether or not anyone noticed.
Pinning an old API version won't move the deadline, and nobody will send you a reminder. Put the audit on this month's list.
If you want help checking your store's tracking and site scripts before 1 March 2027, email the Techno Mantraa team at info@technomantraa.com for a quote.
Frequently asked questions
Script tags stop running on Shopify storefronts on 1 March 2027. Apps lost the ability to create or update them on 1 October 2026, and they already stopped on the order status page on 26 August 2026, or on 28 August 2025 for Shopify Plus stores.
No. Shopify applies the block to every API version, including older ones, so pinning an app to an old version changes nothing.
Only if it still loads through a script tag. Tracking delivered as an app pixel or a custom pixel, listed on the Customer events page under Settings in your Shopify admin, keeps running.
An app embed block adds code or a floating element, such as a chat bubble, to your storefront, and you switch it on in the theme editor. A web pixel only collects analytics or conversion data, runs in a sandbox and needs no action from you once the app provides it.
Yes. Shopify says app embeds can be used with any theme version, so a vintage theme can keep its app features after script tags stop. You need to switch each embed on again if you change your published theme.