Verified facts
What happened
Starting October 1, 2026, Shopify’s scriptTagCreate and scriptTagUpdate mutations will return a user error, while POST and PUT requests to the ScriptTag REST Admin API resource will be rejected.
On March 1, 2027, Shopify will stop injecting ScriptTags into online store storefronts. Existing storefront ScriptTags will continue running until that date.
The deprecation affects apps that create ScriptTags with a display_scope of online_store. ScriptTags for the Order status page are covered by an earlier deprecation.
Shopify recommends replacing storefront ScriptTags with app embed blocks shipped through a theme app extension. If a script only collects analytics or conversion data, Shopify identifies a web pixel as an alternative that does not require merchant activation. The available evidence is a Shopify changelog summary rather than the retained source body, so implementation details beyond that summary are not confirmed.
Business relevance
Why it matters
Shopify app developers that depend on ScriptTags for storefront JavaScript will need to change both their installation workflow and the storefront delivery mechanism before March 1, 2027.
App embed blocks require activation by Shopify merchants in the theme editor, creating a merchant-facing setup step that did not exist when ScriptTags loaded JavaScript without theme-code changes.
Analytics-only and conversion-data scripts may have a lower-friction migration path through a web pixel, while scripts that alter storefront behavior will need a theme app extension approach.
Pinning an older Shopify API version will not defer the deprecation, so version management alone cannot preserve the current ScriptTag workflow.
Editorial perspective
Analysis & judgment
The operational risk is likely highest for Shopify apps whose installation process assumes automatic storefront injection, because migration success will depend on both technical compatibility and merchant activation where app embed blocks are used.
Shopify merchants may experience inconsistent feature availability during migration if some stores activate the new app embed block and others do not; developers should therefore make activation status visible and test the resulting storefront behavior.
Separating analytics and conversion collection from scripts that modify storefront experiences should help teams choose between a web pixel and a theme app extension, but the supplied announcement does not define every eligibility or capability boundary.
Applicability
Seller impact
Shopify app developers using online_store ScriptTags should inventory every storefront script, its purpose, and its installation path; scripts that affect storefront behavior will require a theme app extension and app embed block.
Shopify merchants using affected apps should expect possible setup instructions in the Shopify theme editor and should confirm that critical storefront features remain active after any migration.
Teams using ScriptTags only for analytics or conversion data should evaluate the web pixel route, subject to confirming that it supports their specific measurement requirements.
Merchants relying on Order status ScriptTags should treat that surface separately because it is already covered by an earlier deprecation.
Action plan
What to do now
- 1
Inventory storefront ScriptTags
nowIdentify every Shopify app that creates an online_store ScriptTag, record the JavaScript function it serves, and separate analytics or conversion collection from storefront functionality.
- 2
Map each script to a replacement
this-weekFor each affected Shopify app, plan a theme app extension with an app embed block for storefront behavior or evaluate a web pixel for analytics-only and conversion-data use cases.
- 3
Review installation and activation flows
this-weekConfirm how Shopify merchants will activate app embed blocks in the theme editor, and prepare checks that show whether the required block is active on each relevant store.
- 4
Track the enforcement milestones
monitorMonitor the October 1, 2026 API enforcement point and the March 1, 2027 storefront injection stop while keeping the ScriptTags query and delete capabilities available for auditing and cleanup.
What not to do yet
- Do not rely on pinning an older Shopify API version to defer the deprecation; the supplied Shopify announcement states that the deprecation applies to all API versions.
- Do not remove all existing ScriptTags immediately without first confirming their purpose and migration path, because the supplied timeline says existing storefront ScriptTags continue running until March 1, 2027.
Sources & context
Evidence and sources
- 01Primary link
Starting October 1, 2026, the scriptTagCreate and scriptTagUpdate mutations will return an user error, and the ScriptTag REST Admin API resource will reject POST and PUT. The deprecation applies to all API versions, including older ones, so pinning won't defer it. On March 1, 2027, Shopify will stop injecting script tags into storefronts. Storefronts are the last place script tags still run, since they already stopped working on the Order status page. If your app uses a script tag to load JavaScript onto a store, then you need to replace it before then. What's changing A script tag loads JavaScript on a storefront without any changes to theme code. After March 1, 2027, Shopify won't inject those scripts, so script tags will stop loading JavaScript on storefronts. The scriptTags query and the scriptTagDelete mutation keep working, so you can audit and clean up your existing script tags. What you need to do Replace each script tag with an app embed block, which you ship in a theme app extension. App users activate app embed blocks in the theme editor. If a script only collects analytics or conversion data, then use a web pixel instead, which needs no action from the app user. Who's a
Shopify Developer Changelog · single-source · 72%
Retrieved: August 24, 2026 at 08:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.