BFCM2026
Install on Shopify
Aimerce Blogs
Shopify Blocked Script Tags: Is Your Tracking Next?
9 October 2026
Shopify Blocked Script Tags: Is Your Tracking Next?
First-Party Data 101Shopify
A cover image of Aimerce's blog titled:"Shopify Blocked Script Tags: Is Your Tracking Next?"

Quick Answer: Since October 1, 2026, Shopify apps can no longer create or update script tags, on any API version. Existing script tags keep running on your storefront until March 1, 2027, when Shopify stops injecting them entirely. Any tracking, pixel, or tool that still loads through a script tag will silently stop working on that date, on every Shopify plan. The replacements are web pixels for tracking and conversion data, and app embed blocks for anything else that loads JavaScript on your storefront. Shopify brands should find out now which of their apps still rely on script tags, and plan the switch either before BFCM traffic peaks or right after it.

Key Takeaways

  • Nothing broke on October 1. That date stopped apps from creating or editing script tags. The date that actually turns your tracking off is March 1, 2027.
  • The change applies to every API version, so an app pinned to an older version can't put it off.
  • Script tags already stopped running on the Order status page. Storefront pages are the last place they still work.
  • Tracking and conversion scripts should move to web pixels. Other storefront JavaScript moves to app embed blocks, which show up in your theme editor where you can see and switch them off.
  • If a developer set up tracking through a custom app created directly in your Shopify admin, there's no extension-based replacement for its script tag. That setup needs to be rebuilt.
  • Avoid migrating your tracking in the middle of November. Do it this month or in early January, so the switch doesn't land in your BFCM data.

Most Shopify deadlines announce themselves. Something breaks, a banner appears, your numbers fall off a cliff, and you know where to look.

This one already passed, and nothing happened. That's exactly the risk. Shopify started blocking new script tags on October 1, and every store kept working, so it's easy to file this under "developer problem" and move on. The real date is March 1, 2027. On that day, any tracking still loading through a script tag stops firing, with no error in your Shopify admin and no alert from Meta beyond a slow drop in events you'd have to go looking for.

If you went through the Additional Scripts migration on your Thank You page this summer, this is the storefront half of the same shift.

What exactly did Shopify change?

A script tag is the old way for a Shopify app to load JavaScript onto your storefront without touching your theme code. Shopify replaced them with theme app extensions back in 2021, but kept old script tags running so apps had time to move.

That time is running out in two stages.

October 1, 2026. The scriptTagCreate and scriptTagUpdate mutations started returning errors, and the REST ScriptTag endpoint stopped accepting POST and PUT requests. This applies to every API version, including older ones, so pinning an app to an old version doesn't delay it. Existing script tags keep running, and apps can still read and delete them.

March 1, 2027. Shopify stops injecting script tags into storefront pages. Whatever JavaScript they were loading simply doesn't load anymore.

Script tags are already gone from the Order status page. They stopped running there for Plus stores in August 2025 and for all other stores on August 26, 2026. Storefront pages are the last place they still work.

Does this affect my store if nothing broke on October 1?

Possibly. October 1 only stopped apps from adding or changing script tags. A script tag an app installed last year is still running today, and it will keep running right up until March 1.

That means the question isn't whether your store broke. It's whether any app or custom setup on your store still depends on a script tag that has five months left.

There's one visible sign to watch for. Since October 1, Shopify shows a dismissible banner when you install an app that uses script tags, warning that part of the app will stop working. If you've seen that banner recently and clicked past it, that app is on the list.

Which tracking is most at risk?

Older tracking and analytics apps. Many apps that load a pixel, a heatmap, or an analytics script on your storefront were originally built on script tags. Most active vendors have migrated. Some smaller or less maintained apps haven't.

Custom apps built in your Shopify admin. If an agency or freelancer created an app directly in your admin to inject a tracking script, Shopify says there's no extension-based replacement for that kind of script tag. It has to be rebuilt as a web pixel or a properly built app.

Apps you uninstalled but whose scripts linger. Script tags belong to the app that created them, but it's worth checking for leftovers when you audit.

Tracking that runs through Shopify's built-in sales channels, such as the Facebook & Instagram or Google & YouTube apps, and anything you've added as a custom pixel under Customer events, already uses the web pixel framework. Those aren't affected.

How do you check whether your store still uses script tags?

  1. List every app that touches your storefront. Go through your installed apps and note any that load something on the store itself: tracking pixels, analytics, reviews, popups, chat widgets.
  2. Check your theme editor for app embeds. Open your theme editor and look at the app embeds panel. Apps that have migrated usually appear there as embeds you can switch on and off. A storefront app that doesn't appear there is worth asking about.
  3. Look at your page source. Open your storefront, view the page source, and search for "asyncLoad". Shopify lists the script URLs it injects from script tags inside that function. Each URL usually points to the app that added it.
  4. Ask each vendor directly. Email or chat with every app on your list and ask one question: "Does your app use script tags, and if so, when will it be migrated to an app embed or web pixel?" Get a date in writing.
  5. Check custom work. If an agency set up tracking for you, ask whether they used a script tag or a custom app created in your admin. Those need a rebuild.
  6. Verify after each migration. Once an app moves over, confirm events still reach Meta Events Manager and your other ad platforms at the same volume, and that purchases aren't now being counted twice.

What replaces script tags?

Script tag (deprecated)Web pixelApp embed block
What it's forLoading any JavaScript onto the storefrontTracking and conversion dataStorefront features like widgets, popups, and reviews
Where it runsStorefront pages only (already removed from the Order status page)Storefront and checkout, including purchase eventsStorefront pages, through your theme
Can you see it in your admin?Not easilyYes, under Customer eventsYes, in the theme editor, where you can switch it off
Follows Shopify's consent settingsOnly if the app wired it inYes, built inDepends on the app
StatusCan't be created or edited since Oct 1, 2026. Stops running Mar 1, 2027SupportedSupported

The consent row matters more than it looks. Script tags only respected a shopper's cookie choice if the app developer built that in. Web pixels follow your Shopify consent settings by default, so moving to them tends to make your tracking more compliant, and it can also change how many events you see from regions that require consent.

Should you migrate before BFCM or after?

Here's the part I'd push back on in most of the coverage I've read. Everyone says "migrate now," and for most stores that's right. But the worst time to switch how your tracking works is the middle of November.

Any migration changes how events fire. A web pixel runs in a sandbox, follows consent, and may send slightly different volumes than the old script. That's usually an improvement, but it means your numbers shift. If the shift lands during BFCM, you can't tell whether a drop in purchases is the migration, the market, or a real problem.

So pick one of two windows. Migrate in October, so you have a few clean weeks of data before peak traffic. Or freeze everything through Cyber Monday and migrate in early January, which still leaves plenty of time before March 1. What you shouldn't do is let a vendor push a tracking migration onto your store the week before Black Friday.

For what it's worth, Aimerce doesn't rely on Shopify script tags. On Shopify storefronts it runs through a web pixel and webhooks, and purchases reach Meta and Google server-side from Shopify's order data, so neither deadline touches it.

While you're auditing, it's also a good moment to check that your server-side tracking on Shopify is in place. Browser-side scripts of any kind, old or new, can be blocked by ad blockers and browser privacy settings. Server-side events reach Meta and Google regardless of what happens in the browser.

Common mistakes to avoid

  • Assuming you're fine because nothing broke on October 1. That date blocked new script tags. Existing ones are still running until March.
  • Waiting for a warning. There's no admin alert for script tags that are already installed. You have to check.
  • Trusting "we're updating soon" from a vendor. Ask for a migration date, and set a reminder to verify it.
  • Forgetting custom apps. A script tag injected by a custom app created in your admin has no extension-based replacement and needs to be rebuilt.
  • Migrating during BFCM. A tracking change in late November makes it impossible to read your peak-season data cleanly.
  • Not checking for double counting afterward. If an old script and its replacement both run during the switch, Meta can count purchases twice.

FAQ

What did Shopify change on October 1, 2026? Shopify apps can no longer create or update script tags. The scriptTagCreate and scriptTagUpdate mutations return an error, and the REST ScriptTag endpoint rejects POST and PUT, on every API version. Existing script tags keep running.

When do Shopify script tags stop working? March 1, 2027. On that date Shopify stops injecting script tags into storefront pages, and any JavaScript they load, including tracking pixels, stops running.

Does the script tag deprecation affect Shopify Plus stores? Yes. It applies to every Shopify store and every API version. Plus stores already lost script tags on the Order status page in August 2025.

What replaces Shopify script tags for tracking? Web pixels. Shopify recommends building a web pixel to replace a script tag that only collects analytics or conversion data, and an app embed block for other storefront JavaScript.

How do I know if my Shopify store uses script tags? Check which apps load something on your storefront, look for them in your theme editor's app embeds, search your page source for "asyncLoad" to see injected script URLs, and ask each app vendor directly whether they still use script tags.

Should I migrate my tracking before Black Friday? Either migrate in October, so you have clean data before peak traffic, or wait until early January. Avoid switching tracking in late November, when a shift in event volume is hard to tell apart from real performance changes.

Sources

[1] Shopify Developer Changelog, "Script tags are deprecated and will stop running on March 1, 2027)"

[2] Shopify Developers, "Storefront script tags,"

[3] Shopify Developers, "Script tag deprecation,"

[4] Shopify Developers, "The ScriptTag resource (legacy),"

[5] Shopify Developer Community, "Script tags will stop running on March 1, 2027,"

[6] Aimerce, "Shopify Retiring Additional Scripts: Is Your Tracking Safe?,"

[7] Aimerce, "How to Set Up Server-Side Tracking for Shopify,"

[8] Aimerce, "How to Fix the Shopify vs. Meta Revenue Discrepancy,"

Try Aimerce Pixel Risk-Free
for 30 Days

Most teams see results within 2 weeks.

Money-back guarantee.
It pays for itself, or you don't pay anything.

Install On
Sign Up for a
30-Day Aimerce Pixel Free Trial
Sign Up Using Your Shopify Account Email
*Money back guaranteed.
Aimerce pays for itself or you don’t pay anything.