The customer tag never sticks—or lands on the wrong record.

This page is for a tag that should be written onto the customer record but is not there, arrives late, is replaced, or appears on a customer who should not match. An order tag belongs in the order-tags playbook; a buyer-entered note belongs in cart-note-not-saving; a customer metafield is a different field and write path.

Write down the customer ID, intended tag spelling and case, email or phone match used by the automation, market, channel, timestamp, and owner: Shopify Flow, an app, Admin action, API integration, or custom service. Use a non-sensitive controlled record where possible. Do not diagnose from a segment count alone.

Choose one test customer already available to the store owner. Record tags before and after, account state, source channel, consent state, order event if relevant, and the exact time the automation should have run. Inspect Flow run history or the app's supported log for that customer ID.

• No run exists: the workflow status, trigger, event, connector, or customer match is wrong.
• A run is skipped: inspect the first condition and whether the customer actually reached that state.
• The run succeeds but no tag appears: inspect the target object, API response, write scope, and whether the Admin view is stale.
• The tag appears and disappears: find a second Flow, app, import, merge, or cleanup job writing the same customer.

Test a unique marker such as LATCH-CUSTOMER-TEST-01, then remove it after verification. Never paste customer data or access tokens into screenshots or logs.

Start with ordinary causes: the workflow is inactive or a draft; the trigger is Customer created when the test was a Customer updated event; a condition expects a paid order while the customer has none; a segment or Market condition excludes the record; a wait step has not elapsed; or the customer was merged after the workflow ran.

• Confirm the Flow or app is installed for this store and its documented customer write scope is still authorized.
• Compare exact tag spelling, case, whitespace, and the target's current tag list. Check whether a full-list replacement drops tags added by another writer.
• Check customer merges, imports, duplicate profiles, guest checkout identity, and email normalization before blaming the tag action.
• Review app webhooks or supported logs for retries, rate limits, and idempotency; do not create a second unbounded retry loop.

Keep consent, privacy, fraud, and account controls intact. A tag is an operational label, not proof of consent, identity, payment, or eligibility.

Fix the first confirmed gate: activate the correct workflow, select the event that actually occurred, loosen only the disproved condition, reconnect the supported app, restore its documented permission, or change a replace-tags action to add-tag when that is the intended behavior. Remove one duplicate writer only after its run history proves it is the overwriter.

Retest with two distinct customers that should match and one negative control that should not. Confirm the tag lands once, survives the next relevant update, does not land on the negative control, and is visible in Admin and in the downstream tool that reads it. Record the before/after, run ID, timestamp, exact tag, and rollback step. Keep the change narrow and reversible.

Stay DIY if one customer-tag rule has one confirmed trigger, condition, permission, or conflict to repair. Prove it on controlled records, publish the smallest change, remove test markers, and document the result. No agency is required and no conversion, revenue, or customer-count guarantee is implied.

Pay $997 one-time when the work is wiring the Shopify stack you already use: lead capture, ops alerts, and a checkout-ready workflow. Nico at Latch AI Ops installs it on one live store in 72 hours after collaborator access is in. You are buying the install, not more orders, more customers, a tagging guarantee, or an earnings outcome.