Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- From October 1, 2026, GraphQL and REST ScriptTag creation and updates fail, with no extension through older API versions. Existing tags temporarily keep running.
- From March 1, 2027, Shopify no longer injects ScriptTags into storefronts, stopping dependent UI, tracking and business logic.
- Storefront JavaScript or UI generally moves to an app embed in a theme app extension; analytics, conversion and behavior collection should move to web pixels.
- App embeds require merchant activation in the theme and rechecking after theme changes. Web pixels do not require manual merchant activation.
- Parallel old and new implementations can duplicate loading, analytics or UI. Establish observable cutover and rollback conditions.
The scenario: migrated code, but no new functionality in the published theme
An app team completes an app embed and the test store works, while real stores show no change and old ScriptTags remain in admin. The same version behaves differently across themes, or analytics events suddenly duplicate. Costs include broken storefront functionality, polluted attribution and concentrated merchant support requests.
The wrong instinct is deleting ScriptTags in bulk to force every store onto the new implementation. First export each store’s ScriptTags, script purposes, current published theme and replacement activation state. Do not delete old tags without per-store activation evidence.
Two deadlines, two different risks
Shopify’s official migration documentation says ScriptTag creation and updates are prohibited from October 1, 2026. GraphQL scriptTagCreate and scriptTagUpdate, and REST POST and PUT, fail even on older API versions. Existing ScriptTags keep running during this stage.
From March 1, 2027, Shopify stops injecting existing ScriptTags into storefronts, stopping the scripts and dependent functionality. Do not confuse this timeline with the separate order-status-page migration dates. This article covers storefront ScriptTags only.
Choose app embeds or web pixels by purpose
Move features that load storefront JavaScript, display components or change interactions to app embed blocks in theme app extensions. Move analytics, conversion and behavioral-event collection to web pixels. Do not put UI-rendering code into pixels or continue maintaining storefront injection for pure analytics.
App embeds support vintage themes and Online Store 2.0 but must be activated per theme and rechecked after theme switching. Web pixels need no manual merchant activation. Admin-created custom apps cannot use theme app extensions or web pixels; assess Custom Liquid or theme code while accepting the lack of an automatic upgrade path.
Six steps for per-store migration, activation and deletion
First, inventory active ScriptTags, purposes, owners and dependent pages. Second, separate UI/storefront logic from analytics collection. Third, build app embeds or web pixels and prepare an old-implementation switch. Fourth, use deep links to guide merchants into the theme editor to activate app embeds. Fifth, validate scripts, events, performance and critical pre-checkout paths in the published theme. Sixth, call scriptTagDelete only after confirming no duplicate loading.
Deployment success is not completion. The target store’s published theme must show expected functionality, the browser must load only one implementation, events must not fire twice, old tags must be deleted and checks must pass again after theme switches. Migrate stores in groups, retaining tag IDs, theme IDs, verification times and rollback owners.
Failures, rollback and stop conditions
If parallel implementations duplicate UI or events, stop the new rollout first rather than continuing to delete tags across an unknown scope. If the app embed is inactive in the published theme, regenerate the deep link and have the merchant confirm. Include activation checks in the theme-change workflow.
Stop the batch and escalate to the app owner if a ScriptTag’s function is unknown, a custom app has no maintainable alternative, critical conversion events cannot be reconciled or bulk deletion lacks a recoverable mapping. Rollback should restore only validated old switches. Do not plan to recreate ScriptTags indefinitely, because creation itself fails after October 1.
Common mistakes and the network boundary
Common mistakes include assuming old API versions extend the deadline, treating October 1 as immediate shutdown of every existing tag, deleting old tags before merchant activation, overlooking theme switches, and running app embeds and ScriptTags together indefinitely. Warning banners can explain risk but cannot replace per-store verification.
This is a Shopify extension-system migration, not an egress-IP problem. Consult the proxy connection troubleshooting checklist only when API requests also show explicit DNS, TLS, 407 or timeout evidence. Changing IPs cannot restore ScriptTag creation or updates rejected by the platform.
When to recheck, and why future changes belong on this page
Inventory dependencies now; recheck app embeds after every theme switch; verify creation/update calls have reached zero in September 2026; and complete final checks for all existing stores in February 2027. Update this page if Shopify changes dates, error behavior or replacement capabilities, rather than creating near-duplicate pages.
At each review, record GraphQL/REST call counts, remaining ScriptTags, published-theme activation rate, duplicate loading and event reconciliation. Without new official facts, do not describe one store’s theme problem as a platform-rule change.
Sources
Frequently Asked Questions
When does Shopify stop ScriptTag creation and updates?
From October 1, 2026, creation and updates fail through both GraphQL and REST. Older API versions do not extend the deadline.
Do existing ScriptTags stop immediately on October 1?
No. Existing tags temporarily keep running. Shopify plans to stop storefront injection from March 1, 2027.
How should I choose app embed or web pixel?
Use app embeds for storefront JavaScript or UI, and web pixels for pure analytics, conversion and behavior collection.
Why is there no store change after deploying an app embed?
The embed must be enabled in the current published theme. Recheck activation when the merchant switches themes.
Can ScriptTags and the new implementation run together long term?
That is not recommended. Parallel operation can duplicate scripts, UI or analytics events. Keep validation brief and define clear exit conditions.
How do admin-created custom apps migrate?
They cannot use theme app extensions or web pixels. Assess Custom Liquid or theme code while accepting the absence of an automatic upgrade path.