On this page
Why the old snippet no longer runs
Many older app tutorials recommend scriptTagCreate with display_scope=order_status or all, then attach code to the legacy order confirmation DOM. That was once practical. It is no longer a supported way to extend the new Order status page. Since February 1, 2025 apps have also been unable to create new ScriptTags with those display scopes.
Separate UI from tracking before migrating
Inventory each script’s purpose. A shipment notice, warranty link, or post-purchase help panel is UI and belongs in an appropriate customer account UI extension target. Purchase analytics, attribution, and conversion events belong in a web pixel using Shopify’s supported event subscriptions. A pixel cannot insert HTML. An extension is not a drop-in replacement for unrestricted DOM manipulation or arbitrary third-party scripts.
Audit existing ScriptTags
Use the Admin GraphQL scriptTags query for tags your app owns and inspect their displayScope. Also inspect old theme assets, tag-manager containers, and app configuration for code that assumes the confirmation page loads a storefront script. Read-only ScriptTag operations remain available for cleanup. The exact extension target and API depend on the page and the installed customer-account experience, so validate against the current extension target reference before implementation.
query AuditLegacyScriptTags {
scriptTags(first: 50) {
nodes {
id
src
displayScope
}
}
}
Record what each tag did and who owns its replacement. If a store has not upgraded the Thank you and Order status experience, a customer account UI extension cannot render there until it upgrades. Shopify’s checkout customization report helps identify apps requiring developer updates.
How to test this
- List app-owned ScriptTags and flag
order_statusorall. - Open the store’s checkout upgrade/customizations report and confirm its upgrade state.
- For UI, preview the customer account extension at the intended Order status target on desktop and mobile.
- For analytics, run a test purchase and inspect pixel events in the supported test environment.
- Verify one purchase produces one downstream conversion, without duplicate legacy tracking.
- Test a returning customer revisiting Order status, not just the first Thank you view.
- After sign-off, remove obsolete tags and document the new owner and rollback path.

