Shopify Script Tags Are Being Switched Off: The Two Dates and What Breaks

Apps stopped being able to create script tags on 1 October 2026, and Shopify stops running them on 1 March 2027. What a script tag is, which parts of a store depend on one, and what replaces it.

Muhammad Shehryar2026-09-236 min read
Example screens on two phones: a made-up store's pages, of the kind this work is about
Shopify published the timetable on 24 August 2026, and it has two dates on it. From 1 October 2026 apps can no longer create or update script tags. From 1 March 2027 Shopify stops injecting them into storefronts at all.
The first date passed on 1 October, and on a storefront it looked as if nothing had happened at all. The second one is when things stop working. That gap is the whole problem: a store can look completely fine for five months and then lose tracking, a review widget, a currency switcher and a popup on the same morning.

The Short Answer

Two dates matter. From 1 October 2026 apps can no longer create or update script tags on a Shopify store, though existing ones keep running; nothing visible changes. From 1 March 2027 Shopify stops putting script tags on storefronts at all, so anything still delivered that way, typically analytics and pixels, review widgets, popups, cookie banners, currency selectors and upsell tools, quietly stops appearing. Nothing errors and nothing warns, and pinning an older API version does not defer it, because Shopify applies the change to every version. The work is finding which apps still use them before March. March sits with the other platform deadlines in every eCommerce change already dated for 2027.

What a Script Tag Is, and Where Yours Came From

A script tag is an old mechanism that lets an app inject a JavaScript file into your storefront without touching your theme. You install the app, the app registers a script tag through Shopify's API, and Shopify adds that script to every page.
Almost nobody creates one deliberately. They arrive with apps: analytics and pixel managers, review widgets, upsell and bundle apps, chat, cookie banners, currency and country selectors, wishlist tools, stock counters. A store that has been trading for a few years and has tried a dozen apps is usually carrying several, including some belonging to apps that were uninstalled without cleaning up.
They are also one of the reasons a Shopify storefront gets slow, because each one is a blocking request the theme did not ask for. Anyone who has been through what actually slows a Shopify store down has met them.

1 October 2026: Apps Stopped Being Able to Add Them

Shopify's wording is precise. The scriptTagCreate and scriptTagUpdate mutations return a user error, and the ScriptTag REST Admin API resource rejects POST and PUT.
Nothing on your storefront changed that day. What changed is that an app can no longer install a new script tag or modify one it already placed. In practice this means a newly installed app that has not migrated will silently fail to do the thing you installed it for, and an existing app can no longer update its own script, which is how a script quietly goes stale.
It was the date to audit on, not the date to panic on, and a store that has not audited yet should do it now.

1 March 2027: They Stop Running

On 1 March 2027 Shopify stops injecting script tags into storefronts. Anything that was still relying on one stops appearing.
The storefront is the surface involved. Checkout has had its own extension model for some time, so this is about the theme pages: product, collection, cart, search, home.
The failure mode is worth picturing. Nothing errors, nothing 404s, no banner appears in the admin. The widget is simply not there, the pixel is simply not firing, and the first sign is usually a reporting number that looks wrong a week later. If your conversion tracking is attached to a script tag, you lose the data before you notice you lost the script.

Pinning an Old API Version Does Not Help

Shopify states that the deprecation applies to all API versions, including older ones, so pinning will not defer it.
That closes the usual escape route. A developer who has pinned an app to an older API version to avoid a breaking change is on the same timetable as everybody else, and so is any internal or agency built app doing the same.

What Replaces a Script Tag

Two things, depending on what the script was for. For anything that renders or behaves on the storefront, the replacement is an app embed block shipped in a theme app extension, which a merchant activates in the theme editor. For anything whose only job is analytics, the replacement is a web pixel, which Shopify notes needs no action from the app user.
The distinction matters when you are chasing an app developer for an answer. A review widget needs an app embed block and a merchant has to switch it on. A tracking pixel should move to a web pixel and appear without you doing anything. An app that tells you it has migrated but leaves a widget missing has probably done the pixel and not the block.
Web pixels also interact with how sessions and traffic are attributed, which is a good moment to be sure you can tell real sessions from bot traffic in your analytics before you change the plumbing under it.

Questions to Ask Each App's Developer

Most of the work of this change belongs to the app developers. The merchant's job is to find out, app by app, whether that work is done, and five questions cover it.
Does the app still use a script tag? And if it has moved, to what: a theme app extension, a web pixel, or something else. An answer of soon, with no date, is a reason to plan for a replacement.
Does the merchant need to do anything? App embeds are switched on in the theme editor by the merchant, not by the app. A developer that has moved its app may still be waiting for each store to turn the embed on, and the old script tag will keep running only until 1 March 2027.
Will anything look or behave differently? An app rebuilt on a new mechanism can place its widget differently or lose an option the old version had. Ask before the change, not after a customer reports it.
Will the tracking change? For any app that reports sales or visits, ask whether the move changes what is measured or how it is attributed, so a shift in the numbers afterwards is understood rather than chased.
What happens if the app is not updated in time? For an app whose developer cannot commit to a date before March 2027, the honest answer may be a replacement app, chosen in the quiet season rather than in a hurry.

How to Find What Your Store Is Running

Start with the app list, not the code. Go through every installed app and ask the developer, or read their changelog, for one thing: has this app moved to a theme app extension or a web pixel, and does the merchant have to activate anything.
Then check the theme editor. App embeds appear in the theme customiser under App embeds, and an app that has migrated but whose embed is switched off is the commonest version of this going wrong.
Then look at the storefront itself. View source on a product page and look at what is loading from outside your theme. Anything you cannot account for belongs to an app, possibly one you removed. Uninstalling an app does not always remove its script tag, and a script belonging to an app you no longer have is the easiest thing on this list to delete.

Testing the Store After Each Migration

Moving an app from a script tag to an app embed or a web pixel is usually quick. Knowing that nothing else changed with it takes a short, deliberate test, and the test is the part most often skipped.
Write down what each app does on the storefront first. A review widget on product pages, a size chart, a popup on the home page, a badge in the cart. The list is what the test checks, and without it a missing feature is noticed by a customer instead.
Preview before publishing. Duplicate the live theme, turn on the app's embed in the copy, and preview it. The live store stays untouched until the copy is right.
Check the pages that matter. The home page, a collection, a product page, the cart and the start of checkout, on a phone and on a laptop. For each listed feature, confirm it appears and works, and that nothing appears twice, which happens when an old script tag and its replacement both run.
Check the tracking. The customer events page in the admin lists the store's web pixels and whether each is connected. After moving a tracking app, place a test order and confirm the platforms it reports to received the purchase once.
Change one app at a time. If something breaks after three apps were migrated at once, finding the cause takes far longer than migrating them one by one.

Audit Now, and Migrate the Scripts in January

The timing is awkward and it is worth naming. The audit wants doing now, and the migration wants doing in January, because nobody should be changing the tracking on a storefront during peak. If you are in the middle of preparing a store for BFCM, do the audit and schedule the work.
One exception: if an app you depend on has already told you it will not migrate, replace it before peak rather than after. Discovering in February that the replacement changes your page structure or your URLs is a worse February than doing it now.

Tracking That Depended on Script Tags

Of everything script tags put on storefronts, tracking is the part where a mistake costs most quietly. A missing review widget is seen in a day; a pixel that stopped reporting purchases can go unnoticed for weeks while advertising is optimised on the wrong numbers.
Where tracking moves. Marketing and analytics pixels that ran through script tags move to web pixels, managed on the customer events page. They run in a sandbox, apart from the page's own code, and they work with the store's customer privacy settings, so a visitor's consent choices are respected by design.
Expect the numbers to shift. A pixel running in a different way, and respecting consent where the old one may not have, can report somewhat different numbers. Compare a few weeks before the change with a few weeks after, against the store's own orders, before deciding anything is wrong.
Avoid counting twice. During a migration it is easy to have the old script and the new pixel both running, each reporting every purchase. Advertising platforms then see double the conversions and bid as though the campaigns were working twice as well. Check that each platform receives each test purchase once.
Keep a list of what reports where. One line per pixel: the platform, what it reports, how it is installed, and who owns it. After March 2027 that list is also the record of which tracking survived the change.

Where This Goes Next

The direction of travel on Shopify is consistent: every mechanism that let code get onto a storefront sideways is being replaced with one the merchant can see and switch off. Checkout went first, and the storefront is going the same way. It is better architecture and it makes stores faster, and it does mean a store that accumulated apps for five years has a bill to pay.
Working out which of your apps still matter, which have migrated and which should simply be removed is an afternoon of unglamorous work with a deadline attached, and it is the kind of thing Shopify store management is for. The stores that do it in January will not notice 1 March 2027 at all.

Frequently Asked Questions

The questions that come up most often on this subject.

Want This Applied to Your Account?

Tell us the category and the numbers you have. We will review the account and tell you where the opportunity is and what we would change first.