Shopify script tags are ending: what merchants need to audit before 2027

At a glance

• From 1 October 2026, apps can no longer create or update Shopify ScriptTags.
• On 1 March 2027, Shopify will stop injecting existing ScriptTags into storefronts.
• Merchants should inventory affected features now, ask vendors for a migration plan, and test replacements before removing anything.
• App embed blocks are the normal replacement for storefront behavior; analytics-only scripts should usually move to web pixels.

Some Shopify apps and custom integrations add JavaScript to a storefront through Shopify's legacy ScriptTag API. The script may power a chat bubble, product badge, popup, recommendation widget, analytics event, or a connection to another system. The feature can look like part of the theme even though its code is loaded remotely by an app.

That installation method now has an end date. Shopify announced the change on 24 August 2026, giving merchants and app teams a short window to identify old integrations and replace them deliberately. Waiting until the final shutdown risks losing visible features or measurement without a clear explanation.

What exactly is Shopify changing?

Shopify's deprecation announcement sets out two separate deadlines:

• 1 October 2026: the GraphQL mutations used to create or update ScriptTags will return an error, and the equivalent REST operations will reject writes. Pinning an app to an older API version will not postpone this change.
• 1 March 2027: Shopify will stop injecting ScriptTags into online storefronts. Existing tags will then stop loading their remote JavaScript.

The first date matters to app developers because it prevents them from repairing or changing legacy installations through the same mechanism. The second matters directly to merchants because whatever storefront behavior depends only on that tag will disappear.

This change is about the ScriptTag resource. A JavaScript file that is deliberately included in your theme code is a different installation path and is not removed merely because this API is deprecated. It may still deserve a performance, privacy, and maintenance review, but it requires a separate decision.

Script tags have already stopped working on order-status pages. The March 2027 deadline concerns the remaining online_store use on the storefront.

Why merchants should care before the shutdown

A ScriptTag often acts as a loader. Its own code may be small, but it can fetch a larger application and create customer-facing elements or send business data elsewhere. If that loader stops, the symptom depends on what sits behind it.

Possible effects include:

• a review badge, size guide, stock notice, or floating support widget no longer appearing;
• personalization, recommendations, or promotion logic no longer running;
• analytics and advertising events dropping without an obvious storefront error;
• consent-dependent tracking behaving differently after a rushed replacement;
• a custom integration losing the browser-side signal that starts an internal workflow.

This does not mean every installed app is affected. Modern apps may already use theme app extensions, app blocks, app embed blocks, or web pixels. An app name alone does not reveal its installation method, and seeing JavaScript in the browser does not prove that it came from a Shopify ScriptTag.

The useful merchant question is therefore not “Do we use JavaScript?” It is “Which business functions still rely on Shopify injecting an online_store ScriptTag, and who owns their migration?”

How to build an affected-function inventory

Start with the functions customers and staff would notice, then connect them to their technical owners. Do not begin by deleting code.

Review apps and custom integrations

List installed apps that add something to the storefront or collect storefront events. Include private and custom apps, old agency-built tools, tracking services, chat, subscriptions, reviews, merchandising, wishlists, localization, accessibility tools, and feed or ERP connectors with browser-side components.

For each one, record the owner, purpose, pages used, data sent, and how you would recognize failure. Ask the vendor or developer directly whether the current installation creates a Shopify ScriptTag with display_scope: online_store, and whether a replacement is already available.

App developers can audit the tags their app owns through Shopify's scriptTags GraphQL query, which requires the relevant script-tag access. The result includes the source URL and display scope. Because tags are tied to the app that created them, a merchant should not treat a query from one app as proof that no other app has a tag.

Compare technical evidence with business behavior

Capture a browser network trace or a list of external script hosts on representative pages. This can help match a remote URL to a vendor, but it is supporting evidence rather than a complete ScriptTag audit. Also review old implementation notes, app invoices, theme handover documents, and previous developer access.

Turn the result into a simple register: feature, owner, current loader, proposed replacement, test case, and target date. Give revenue, checkout-adjacent behavior, privacy controls, and core measurement the highest priority.

Choose the right replacement for each job

Shopify's legacy resource guide directs storefront integrations toward app embed blocks or web pixels. The correct choice depends on what the script actually does.

App embed block

An app embed block suits behavior without an inline section, including floating or overlaid UI and scripts that need to load around the document head or body. It is part of a theme app extension and works with both vintage and Online Store 2.0 themes. Shopify also lets an embed limit loading to relevant templates, reducing unnecessary page impact.

There is an operational detail: an app embed is normally inactive after installation. The merchant must activate it in the theme editor. A vendor can provide a deep link, but activation still needs to be confirmed on the published theme.

App block

Use an app block when customers see content inside a theme section and merchants should be able to place or reorder it—for example ratings near product information. The published theme and target section must support app blocks.

Web pixel

If the old script only collects analytics or conversion events, Shopify says to use a web pixel. Web pixels subscribe to Shopify customer events in a sandbox and work with Customer Privacy API consent signals. They do not have unrestricted access to the page DOM, so a migration may require event mapping rather than copying the old JavaScript line for line.

Do not combine unrelated work into one replacement. A widget that renders UI and also sends analytics may need a theme app extension for the interface and a web pixel for measurement.

Migrate without creating a new outage

A safe migration has a short overlap only where duplication cannot cause harm. Shopify's migration guide warns that running a ScriptTag and its app-embed replacement together can render UI twice or double-count analytics.

Use this sequence for each affected function:

1. Record the current behavior and baseline metrics before changing it.
2. Build or enable the replacement in an unpublished theme or controlled test environment.
3. Test its loading conditions, settings, translations, consent behavior, and failure handling.
4. Publish or activate the replacement on the live theme.
5. Confirm that the app embed is active and the intended feature works in production.
6. Only then delete or disable the old ScriptTag.
7. Monitor the relevant storefront, analytics, and operational metrics after release.

Theme duplication alone is not always a full test environment. App configuration, customer events, consent state, markets, and third-party endpoints can behave differently. Use low-risk test orders or vendor test modes where the feature crosses a purchase flow.

What to test before signing off

Test the customer outcome, not only whether a JavaScript request returns 200.

• Check home, collection, product, cart, search, and account-facing pages where the feature should or should not load.
• Test mobile and desktop layouts, several product states, and every active storefront language.
• Check the published theme, not only the theme-editor preview.
• Test consent accepted, rejected, and not yet chosen where tracking is involved.
• Confirm that analytics events occur once, with the intended identifiers and values.
• Check page speed and browser errors before and after the change.
• Verify that uninstalling or disabling the app removes its behavior cleanly.
• Document the new activation and rollback procedure for the team.

For important measurement, compare order counts and revenue in Shopify with the receiving analytics or advertising platform over a representative period. Perfect equality is unlikely, but a sudden structural break or duplicated event rate should be investigated before sign-off.

Shopify ScriptTag migration checklist

• Every storefront app and custom integration has an owner.
• Vendors have confirmed whether they use an online_store ScriptTag.
• Each affected feature has a documented replacement and deadline.
• App embeds are activated on the published theme.
• Visual features work on relevant templates, devices, markets, and languages.
• Analytics and consent behavior have been tested separately.
• Old and new loaders are not double-counting or rendering twice.
• Legacy tags are removed only after the replacement is verified.
• Monitoring and a practical rollback path are in place.
• The migration is complete well before 1 March 2027.

If an old custom app or undocumented storefront integration appears in this audit, the first useful step is a focused technical inventory. Stormdev can trace the current behavior, map it to the appropriate Shopify extension, and migrate it in small, testable releases.