TagExit · Waitlist
Tell us your purpose (UI inject vs tracking), distribution (Partner app / Admin-created custom / paste-token SaaS), and whether you already ship ScriptTag, app embed, or web pixel. Get one recommended exit path — app embed, web pixel, theme Liquid, or become a real Partner app — plus a merchant theme-editor deep-link enable checklist, dual-load warning, and Oct-1 / Mar-1 countdown with an audit list. Not Shopify Admin API, not a migration agency — a decision-readiness layer before new installs lock you out.
Market-validation page · Free waitlist · No fake user counts
Problem
Shopify is removing storefront ScriptTags. From 2026-10-01, scriptTagCreate/Update (GraphQL) and ScriptTag REST POST/PUT return permission errors on all API versions — pinning an old version does not help. New installs without app embed or web pixel cannot turn features on. Existing tags may keep running until 2027-03-01, when Shopify stops injecting into the storefront. Paths split: UI → theme app embed (merchant must enable in the theme editor; active theme only); analytics → web pixel (no merchant action). Admin-created custom apps cannot use app extensions or web pixels — move into theme Liquid or ship a real Partner app (easy to miss at the bottom of the docs). Running old tag + new embed = double-count / double UI. Long docs educate; they don’t turn purpose × distribution × state into one path + checklist.
Solution
A ScriptTag exit-path decision-readiness layer for Partner / Indie / paste-token SaaS: purpose × distribution × current state → one recommended path + merchant enable checklist + dual-load / Admin-custom warnings + Oct-1 / Mar-1 countdown — not another long doc or migration agency.
Shopify Partner / Indie app developers still injecting storefront JS via ScriptTag; and third-party tracking / chat / A/B / loyalty / pixel SaaS plus agency eng / CS who create Admin-created custom apps and paste access tokens into their dashboards.
From Oct 1 2026 create/update dies on all API versions; Mar 1 2027 injection stops. Paths split (embed vs pixel); Admin-custom is a dead end for extensions/pixels; dual-load risks double-count. Docs don’t give one path for your distribution type.
Form: purpose (UI vs tracking), distribution (Partner / Admin custom / paste-token SaaS), ScriptTag / embed / pixel state → one path (app embed / web pixel / theme Liquid / real Partner app) + deep-link enable checklist + dual-load warning + Oct-1 / Mar-1 countdown & audit list. MVP: no Shopify Admin API.
Pick the right exit path before 1 Oct 2026 — avoid Admin-custom dead ends and dual-load — don’t wait until March kills the rest.
Features
Marketing points from the product hypothesis — for demand validation, not a formal spec promise.
Enter purpose (UI vs tracking), distribution (Partner / Admin custom / paste-token SaaS), and current ScriptTag / embed / pixel state → one recommended path (app embed / web pixel / theme Liquid / become Partner app).
Call out that Admin-created custom apps cannot use app extensions or web pixels; guide to theme Liquid or a real Partner app — so you don’t finish the long docs and still miss it.
Theme-editor deep-link enable steps; active-theme / theme-switch reminders; confirm replacement is live before scriptTagDelete to avoid double-count / double UI.
Countdown for create/update death (Oct-1) and injection stop (Mar-1); audit existing tags, confirm replacement, delete old tags, check new-install banner risk.
Form + path recommendation + checklist + countdown. Explicitly not Shopify Admin API reads/writes, building theme app extensions, or publishing Partner apps for you.
How it works
A three-step loop matching the waitlist-stage product hypothesis.
UI vs tracking; Partner app / Admin custom / paste-token SaaS; current ScriptTag / embed / pixel state.
App embed / web pixel / theme Liquid / become Partner app; Admin-custom dead-end callout included.
Merchant theme-editor deep-link steps, dual-load warning, Oct-1 / Mar-1 countdown + audit list — not Admin API, not a migration agency.
Use cases
If these situations sound familiar, join the waitlist to help us validate.
Confirm you should move to theme app embed and get a merchant deep-link enable checklist so new installs don’t break after Oct 1.
Confirm web pixel (no merchant action) and avoid dual-load double-count with the old tag.
Merchants use Admin-created custom apps and paste tokens — get told clearly you can’t use extensions/pixels; ship a real Partner app or move into theme.
Need an audit list and dual-load warning to decide when to scriptTagDelete.
Need dual countdown + new-install banner risk so reading docs doesn’t replace execution.
Public signals
Public reporting from Shopify only — not customer testimonials or invented metrics.
FAQ
Official docs are the rules. We turn purpose × distribution × current state into one executable path and checklist.
Those are tips and deep-link fragments. We are a distribution-aware decision-readiness layer — not a forum.
Notion is hand-maintained. We structure Oct-1 / Mar-1 and the Admin-custom dead end into a decision form.
No. MVP is a static form + path recommendation + checklist + countdown.
Per Shopify: they can’t use app extensions or web pixels. Move into theme Liquid or ship a real Partner app; paste-token services must release a real app.
Running an old ScriptTag and its replacement at once can double-count or double-render. Confirm the replacement is live before deleting the tag.
Static form + path recommendation + enable checklist + countdown. Admin API, building extensions, and publishing Partner apps are out.
Waitlist invites go out in batches by email. No fake launch date.
Waitlist
Leave your email for TagExit early access and launch notes. We will not invent a ship date.
We’ll email early-access invites and launch updates in batches. Unsubscribe anytime.