Shopify Is Switching Off Script Tags: What Ecommerce Directors Should Check Before Their Tracking Goes Quiet

Many Shopify stores still have tracking that nobody in the business remembers installing. An affiliate tag, an older conversion pixel, an analytics script: small pieces of code that an app added to the storefront years ago, quietly sending data to Google Ads, Meta and your analytics tools.

Shopify has now set an end date for one of the older ways apps put code onto a store. Since 1 October 2026, apps can no longer create or update “script tags”, and on 1 March 2027 Shopify will stop running them on storefronts altogether. In this blog, we’ll explain what has changed, why it matters for the P&L, and what to check now so your tracking doesn’t go quiet in the middle of spring planning.

What has changed

A script tag is a way for an app to load its own JavaScript onto your storefront without anyone editing the theme. Shopify’s developer changelog, published on 24 August 2026, sets out two dates:

• 1 October 2026 (already passed): apps can no longer create or update script tags. This applies to every version of Shopify’s API, so an app can’t get round it by using an older one. Existing script tags keep running.
• 1 March 2027: Shopify will stop adding script tags to storefront pages. Whatever they load, including tracking, simply stops loading.

Shopify says script tags have already stopped working on the Order status page, so the storefront is the last place they still run.

Its reason is control. According to the changelog, script tags run code on your storefront without appearing in the theme editor, which makes them hard for merchants to find and switch off. The replacements are more visible:

• App embed blocks, which appear in the theme editor where you can see them and turn them off.
• Web pixels, which Shopify names as the replacement when a script only collects analytics or conversion data. These are managed in the Customer events section of your Shopify admin and, according to Shopify’s pixels overview, load on the storefront, checkout, Thank you page and Order status page.

Why it matters for the P&L

Tracking that stops doesn’t send an error message. Orders keep arriving in Shopify while the ad platforms stop hearing about them.

• Your bidding depends on it. Google Ads and Meta use conversion data to decide where to spend your budget. If a conversion feed stops on 1 March, automated bidding starts optimising on less data, just as spring budgets are being set.
• Double counting is the opposite risk. Shopify’s migration guide warns that if an old script tag and its replacement run at the same time, the script loads twice, which can double-count analytics events. Inflated conversions make ROAS look better than it is, and budgets follow.
• Your numbers may legitimately change. In markets that require consent, usually the UK and EEA, Shopify says web pixels only run when the visitor has given the permissions the pixel needs. By default, new pixels need both Marketing and Analytics permission. If an old script ignored consent, the new setup may report fewer conversions. That is a reporting change, not lost sales, and finance should hear it from you first.
• Some data may not carry over. Pixels run in a sandbox. Shopify says features that automatically pick up email addresses or phone numbers from forms on the page might not work there. That data often feeds match quality on ad platforms, so ask how your provider will pass it instead.

A worked example

Imagine a UK fashion retailer on Shopify, running Google Ads, Meta and Pinterest, with an affiliate network paid on tracked sales. (An illustrative scenario, not a real client.) The Pinterest tag and the affiliate tag were both added by apps installed in 2022.

In January, the team asks each app provider how their storefront code is delivered. The affiliate provider has already moved to a web pixel, but the old script tag was never removed, so sales have been reported twice since the switch. The Pinterest app still relies on a script tag and has a replacement planned for February. The team removes the duplicate, adjusts affiliate payments, and tests the new Pinterest setup alongside the old one before 1 March, rather than discovering the gap in April’s reporting.

Director checklist before 1 March 2027

1. Name an owner. Make one person responsible for every piece of storefront code, including apps, agency work and anything in the theme.
2. List what loads on your store. Start with the apps listed in Customer events and the app embeds in your theme editor, then ask your developer to compare that with what your storefront actually loads.
3. Ask every app provider one question, in writing. “Does your storefront code use a script tag, an app embed or a web pixel, and what is your plan for 1 March 2027?” Shopify’s tools let each app list its own script tags, so the provider is the one who can answer for certain.
4. Check your custom apps. Shopify says apps created directly in the Shopify admin can’t use app embeds or web pixels at all, so their scripts need moving into the theme or rebuilding. If a third-party service asked you to create one of these apps, it needs to release a proper app.
5. Don’t reinstall old tracking apps during peak. Since 1 October, an app that still depends on a script tag can’t create one. Shopify warns that any store installing such an app without a working replacement loses what the script tag provided.
6. Watch for theme switches. Shopify says an app embed only works on the theme it was switched on for. If you publish a special theme for Black Friday or a relaunch, check your embeds are switched on there too.
7. Remove old code only once the replacement is proven. Ask for a test order to be checked in each destination, confirm each sale is counted once, then remove the old script tag.
8. Brief finance on consent. If the new setup respects consent where the old one didn’t, agree in advance how you’ll explain any drop in reported conversions.

Caveats

• Nothing breaks today. Existing script tags keep running until 1 March 2027. The 1 October change affects creating and updating them, not running them.
• Not every script is a script tag. Code pasted directly into your theme, including a Google Tag Manager snippet added that way, is a different mechanism and isn’t covered by this change. Your developer needs to confirm which mechanism each script uses.
• Pixels aren’t the same as server-side tracking. Shopify’s pixels run in the customer’s browser, so consent choices still apply. Moving to a web pixel won’t recover sales a visitor hasn’t consented to share.
• Timing is yours to manage. Most retailers won’t want tracking changes during peak trading. Use October and November to audit, then plan the switch for January and February, leaving room to test before 1 March, which is a Monday.

Final thoughts

#10/100 — The script nobody remembers installing is the one that goes quiet first.

Shopify has given every merchant a clear deadline and a cleaner way of running storefront code. The risk isn’t the change itself; it’s the tracking that no one owns. An hour spent listing what runs on your store now is far cheaper than explaining a sudden drop in reported conversions next spring.

Want help auditing the tracking on your Shopify store, or planning the move to web pixels? Email info@taggurus.co.uk or book a meeting today to discuss.

FAQ

Q: Will our tracking stop working on 1 October 2026?
A: No. Since 1 October, apps can’t create or update script tags, but existing ones keep running. Shopify stops running them on storefronts on 1 March 2027.

Q: Does this affect Google Tag Manager on Shopify?
A: Not directly. Shopify’s change is about script tags added by apps. If you run Google Tag Manager as a custom pixel, Shopify says it runs inside the same sandbox as other pixels, with the same limits.

Q: Should we wait for our app providers to fix it?
A: Ask now rather than wait. The providers have to build the replacements, but you need their answers, and time to test, before 1 March 2027.