Playbook · ScriptTag metafield missing
Shopify ScriptTag metafield missing? Prove the owner, access, and script payload.
Written for a Shopify owner whose legacy ScriptTag or app script mounts but the metafield it needs is missing. Start with the resource owner, namespace.key, storefront access, and what the script actually reads—not with a theme rebuild. This is distinct from ScriptTag not firing and from Online Store 2.0 metafield display bugs.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
Buy the 72-hour install — $997ScriptTag not firingMerchant FAQ
01
A missing metafield is not the same bug as a ScriptTag that never fires.
Use this page when the ScriptTag network request succeeds and the script executes, but the expected metafield is absent, null, or never exposed to the page. If the script never loads after Checkout Extensibility, use the ScriptTag not firing playbook first.
Capture the ScriptTag src, display_scope, page type, owner ID, namespace.key, and the exact console or DOM place where the value should appear before changing the app or theme.
02
Prove the owner and exact namespace.key the script expects.
Confirm whether the field belongs to the shop, product, variant, customer, cart line, or collection. A product metafield will not appear because a script reads a shop-level key. Record one synthetic test record and its ID.
Copy the exact namespace.key, including case. Do not create a duplicate definition because its label looks identical in Admin Custom data.
03
Check type, storefront access, and a saved reversible test value.
Record the definition type, list or reference shape, and storefront access. Save one unmistakable, reversible test value on the exact owner, refresh Admin, and confirm it persists. If Admin itself has no value, the script will correctly look empty.
Keep customer data, tokens, and passwords out of screenshots. Treat an absent field, null, empty string, and empty list as separate observations.
04
Inspect the ScriptTag URL and runtime payload separately from theme Liquid.
Open the ScriptTag src and confirm it still points at the intended app host. In DevTools, separate: script never injected, script loaded but no metafield in window/JSON, metafield present but script mis-parses type, or theme Liquid never exposing the field the script expects.
Legacy ScriptTags often read Liquid-injected JSON or AJAX product endpoints. A correct Admin value with Storefront access off, or a theme that never prints the metafield into the page, will look like a “missing” field even when the ScriptTag fires.
05
Retest one Online Store page and preserve the proof.
Use one product or cart page, one ScriptTag src, and one known owner. Record owner ID, namespace.key, type, saved test value, storefront access, script console output, and network payload. Hard-refresh only after the first trace is captured.
Classify the miss as owner, definition/value, storefront access, Liquid exposure, script parse, or ScriptTag not firing. Keep it separate from customer events pixels, theme app embeds, and Storefront API throttle.
06
When to stay DIY vs pay $997.
Stay DIY when one owner, access, Liquid exposure, or script-parse check explains the missing field. Keep the proof packet so future ScriptTag or Customer Events migrations are reversible.
Pay for the $997 one-time install when several Shopify surfaces, apps, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.