Shopify Customer Privacy API metafield blank? Prove consent state, owner, and one privacy write.

Use this page when consent is collected (or should be) but the metafield the app or theme should set from Customer Privacy API state never appears. If the miss is a sticky CMP overlay trapping clicks on ATC or checkout, use cookie banner blocking checkout. If the miss is Consent Tracking / analytics event gating, use Consent Tracking API metafield missing.

Do not flip Markets or CMP apps yet. Capture the shop, region, Customer Privacy banner mode, analytics/marketing/preferences flags, namespace.key, and whether any metafield mutation runs after consentCollected.

Open Settings → Custom data and confirm the definition is owned by the Shop, Customer, or app-owned resource your privacy callback writes. Record the exact namespace and key, for example privacy.consent_snapshot, 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 Customer Privacy API listeners.

Confirm Customer Privacy is enabled for the region you are testing, the banner (or headless consent UI) actually presents a decision, and window.Shopify.customerPrivacy (or the equivalent headless Customer Privacy API) reports the expected analytics/marketing/preferences state after Accept or Decline.

Compare CMP apps (Consentmo, Cookiebot, and similar) against native Customer Privacy: two banners can leave the API in a forever-pending state so your write never runs. Soft-link cookie consent banner broken when Accept never unlocks pixels. Log region and consent flags only — never log personal data beyond what the shop already stores.

After a stable consent state, run one authenticated metafieldsSet (or Storefront-safe write path your app uses) for the namespace.key you recorded. Prove the same value in Admin GraphiQL. If GraphiQL shows the test value but the theme or pixel path does not, fix the read path or consent gate — not the definition alone.

Keep the diagnosis distinct from customer events pixels broken and Web Pixel metafield blank. Those touch pixel payloads and sandbox events, not Customer Privacy API entitlement or consent-snapshot fields.

Use one test shop, one region (for example EU vs non-regulated), and one browser profile. Record region, banner mode, Accept vs Decline timeline, Customer Privacy API flags, namespace.key, type, GraphiQL value after callback, and whether the dependent UI or pixel path respects the field. Clear consent cookies between Accept and Decline trials so the shop is not left with a stale decision.

If the field is still blank, classify it as definition/value, consent never decided, listener skipped, CMP fight, missing write scope, or read-path lag. Do not enable a second CMP until one Accept/Decline path writes and reads cleanly on one shop.

Stay DIY when one definition, consent-state check, CMP conflict, or callback write explains the blank. Keep the proof packet so future Markets and privacy changes stay grounded in real Customer Privacy API 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.