Shopify Consent Tracking API metafield missing? Prove consent gate, event, and one tracking write.

Use this page when analytics consent allows tracking but the metafield the app should set from Consent Tracking / customer events never appears. If the miss is Customer Privacy API consent state or a privacy snapshot field, use Customer Privacy API metafield blank. If the miss is a Web Pixel event payload field, use Web Pixel metafield blank.

Do not disable all pixels yet. Capture the shop, region, analytics/marketing consent flags, event name (page_viewed, product_viewed, checkout_completed), namespace.key, and whether any metafield mutation runs after an allowed event.

Open Settings → Custom data and confirm the definition is owned by the Shop, Order, Customer, or app-owned resource your tracking callback writes. Record the exact namespace and key, for example tracking.last_allowed_event, the type, and whether the app owns the definition.

Manually save a short test value in Admin, refresh, and confirm it survives. If Admin cannot store the field, fix the definition before debugging Consent Tracking listeners.

Confirm analytics (and marketing if required) consent is granted for the session under test, Consent Tracking / Customer Privacy reports tracking as allowed, and the customer event you expect actually fires in the customer events debugger or pixel sandbox.

Compare declined vs accepted sessions: a write that runs on page load without checking consent will look “missing” in regulated regions and noisy elsewhere. Soft-link analytics not matching GA4 when purchases fire in one system but not the other. Log event name and consent flags only — never log payment secrets or full PII dumps.

After an allowed event, run one authenticated metafieldsSet (or approved server webhook path) for the namespace.key you recorded. Prove the same value in Admin GraphiQL. If GraphiQL shows the test value but the analytics dashboard or app UI does not, fix the read path or cache — not the consent gate alone.

Keep the diagnosis distinct from customer events pixels broken and cookie consent banner broken. Those touch pixel sandbox delivery and banner unlock, not Consent Tracking entitlement metafields.

Use one test shop and one event. Record region, Accept analytics timeline, event name and timestamp, Consent Tracking allowance, namespace.key, type, GraphiQL value after callback, and whether the app UI shows the tracking marker. Decline once afterward to prove the write does not run when tracking is blocked.

If the field is still missing, classify it as definition/value, consent blocked, event never fired, listener skipped, missing write scope, or read-path lag. Do not add a second analytics pixel until one allowed event writes and reads cleanly on one shop.

Stay DIY when one definition, consent gate, event fire, or callback write explains the miss. Keep the proof packet so future pixel and Markets changes stay grounded in real Consent Tracking state.

Pay for the $997 one-time install when several Shopify surfaces, apps, catalogs, 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.