Playbook · Customer segment metafield blank
Shopify customer segment metafield blank? Prove the owner, ShopifyQL, and segment read.
Written for a Shopify owner whose customer segment / ShopifyQL condition expects a metafield that is blank. Start with the customer owner, namespace.key, access, and what the segment actually reads—not with a discount rebuild. This is distinct from customer segment discount not applying and from customer metafield not saving.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
01
A blank metafield is not the same bug as a segment discount that never applies.
Use this page when the segment condition references a customer metafield that is empty, null, or never exposed to ShopifyQL—even though Admin Custom data may look fine on another customer. If the metafield has a value and the automatic discount still fails, use the customer segment discount not applying playbook first.
Capture segment name, ShopifyQL predicate, customer ID, namespace.key, and whether Admin shows a saved value before changing discounts or Flow.
02
Prove the customer owner and exact namespace.key the segment expects.
Confirm the metafield is on the Customer resource—not shop, order, or company. A product metafield will not satisfy a customer-segment ShopifyQL predicate. Record one synthetic test customer 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, access, and a saved reversible test value.
Record the definition type (boolean, single-line text, number, list), and whether Admin / Apps can read it for segments. Save one unmistakable, reversible test value on the exact customer, refresh Admin, and confirm it persists. If Admin itself is blank, the segment will correctly exclude the customer.
Keep PII, tokens, and passwords out of screenshots. Treat absent, null, empty string, and empty list as separate observations. If the value will not save, use customer metafield not saving first.
04
Inspect ShopifyQL / segment condition reads separately from discount combinesWith.
Open the segment editor and copy the ShopifyQL that references the metafield. Separate: wrong namespace.key, type mismatch (string vs boolean), segment not refreshed after save, customer not in preview membership, vs discount combinesWith / Functions failing after membership is correct.
Customer segments often lag briefly after metafield writes. Confirm the segment preview includes the test customer before blaming automatic discounts or Checkout Functions.
05
Retest one customer membership and preserve the proof.
Use one test customer, one segment, and one known namespace.key. Record customer ID, namespace.key, type, saved test value, ShopifyQL predicate, segment preview membership, and whether an automatic discount then applies. Refresh the segment only after the first Admin value is captured.
Classify the miss as owner, definition/value, access, ShopifyQL parse, segment lag, or discount not applying. Keep it separate from Flow triggers, Klaviyo lists, and Multipass / customer accounts login.
06
When to stay DIY vs pay $997.
Stay DIY when one owner, access, ShopifyQL, or segment-refresh check explains the blank field. Keep the proof packet so future segment or discount changes 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.