Shopify Dynamic Customer Segments: Reset Tags

Reset on Mismatch makes Shopify dynamic customer segment tags follow the rule that added them. When a customer stops matching, SO: Auto Tags removes those tags from the customer. Use it for a VIP tag that should track current spending, and leave it off when the tag should remain after the condition stops matching.

Turn on Reset on Mismatch for a moving segment

Customer rules are evaluated in near real time from Shopify webhooks. For customers, the app subscribes to customers/create, customers/update and customers/purchasing_summary. If the current customer record falls outside the rule, Reset on Mismatch removes the tags that rule added.

Treat the setting as a choice about what the tag means. A VIP tag that represents current eligibility should leave with a mismatch. A tag intended to record that the customer qualified at some earlier point should remain outside this reset behavior.

Removal is limited to the tags created by that rule. Reset on Mismatch does not turn the rule into a general tag cleaner or remove unrelated tags from the customer.

Build the VIP rule from customer fields

Set customers as the resource type, add conditions, choose AND or OR logic, enter the tags, set the enable flag and assign a priority. Lower priority numbers are evaluated first, and the default priority is 10. The rule library also includes a VIP customer recipe that you can import and edit.

Spending and purchases: total spent and order count.
Identity and contact: email domain, accepts marketing, verified email, first name and last name.
Customer data: tags, country, province, city and created date.

These conditions use standard Shopify fields. A condition based on a metafield requires Shopify Flow or a feature request, so do not build the segment around a metafield and expect this rule form to evaluate it.

Rule tree showing how AND and OR logic determine whether customer conditions match

Account for duplicate tag triggers

Several rules can apply the same VIP tag. Shopify shows that tag once on the customer, but each rule trigger counts as an operation against the plan quota. Consolidating overlapping conditions changes the number of triggers even though the visible tag still appears once.

Operation accounting follows the modification: one tag applied counts as one operation, each resource cleaned counts as one, and each modified resource in a bulk job counts as one. The quota resets monthly.

Free includes 200 tagger tags per month, while Basic includes 2,000. Pro removes every operation limit. Pick the plan against the number of rule triggers, not the number of distinct tag names visible in Shopify.

Test one customer before enabling the rule

The Activity Log supplies the evidence for a controlled check. Every rule trigger records a timestamp, a status of Success, Failed or Pending, and details. Filters narrow those records by category, status and date range.

Use the one-resource path before exposing the rule to matching customer events. It keeps the first review focused on the tag result for a known customer instead of mixing that result with activity from the rest of the store.

Rules are event-triggered. For scheduled batch tagging, run Data Reprocess over a date range or connect the rule to Shopify Flow scheduled triggers.

Flow from saving a disabled rule through checking one resource and enabling the rule

Leave Reset off for a tag that must stay

Do not enable Reset on Mismatch for a tag whose meaning is that the customer met a condition at some point. A later mismatch instructs the app to remove the tag, which changes a historical marker into a current-state segment.

Every rule has an enable toggle. Duplicating one creates a disabled copy with "(Copy)" appended to its name, giving you a separate rule configuration to inspect before enablement.

Uninstalling the app does not remove tags already applied to Shopify resources. Rules and settings survive for 30 days, while the existing tags stay on the resources because they are Shopify data.

Watch monthly usage after enablement

Billing & Usage shows the current plan, this month's usage against its limit, the last three months of usage and a progress bar. Check that surface after enabling overlapping customer rules because each matching trigger consumes quota even when the tag already exists.

Once the monthly quota is exhausted, rules stop processing new events and the app displays a warning banner. Upgrading applies the larger quota immediately, so processing can continue under the new limit.

More posts on SO: Auto Tags are on the blog.