Shopify Customer Tags Automatically: Conditions

To apply Shopify customer tags automatically, create a customer rule with the conditions that define the segment, choose AND or OR logic, add the tags, then enable the rule. SO: Auto Tags evaluates rules from Shopify webhook events in near real time.

Set total spent and order count in a customer rule

Customer rules can use total spent, order count, email domain, accepts marketing, verified email, first name, last name, tags, country, province, city and created date. Total spent and order count supply the two purchase-history inputs for a customer tier.

Example segment one uses total spent > $500 AND the order-count condition you choose. The rule applies its tags only when the complete AND condition set matches, so spend alone cannot qualify the customer for that tier.

Turn on Reset on Mismatch when the tag should follow the rule's current result. Once the customer no longer matches, the app removes the tags that this rule added. That setting supports a VIP tag tied to spending without making the tag permanent.

Add accepts marketing and verified email checks

Accepts marketing and verified email are separate customer conditions. Put both in the same rule when the tag depends on both Shopify fields; use email domain when the address domain is also part of the qualification.

A verified email condition does not replace the accepts marketing condition, and accepts marketing does not verify an address. Select the field that represents the state you need instead of treating the two as one consent signal.

Customer rule conditions work with standard Shopify fields. A value stored in a metafield cannot serve as one of these conditions; that case requires Shopify Flow or a feature request.

Match country, province or city

Country, province and city provide the location conditions. Example segment two uses country = US OR country = CA. Keep it as an OR rule when either listed country should satisfy the location test.

Add province or city when the customer tag needs a narrower geographic boundary. A created date condition can narrow the same customer population by account age, while first name, last name and existing tags remain separate matching inputs.

A rule stores one resource type, its condition set, the selected logic, the tags to apply, an enable flag and a priority. Keep the resource type set to customers for conditions in this list.

Choose AND or OR for the condition set

The logic selector controls how the customer rule evaluates its conditions. Choose it after deciding whether the tag requires the complete set or permits an individual match.

Comparison of AND and OR matching behavior in a customer tagging rule

If several rules apply the same tag, the customer carries that tag once, but each rule trigger counts as an operation against the plan quota. Priority controls evaluation order: lower numbers run first, and the default priority is 10.

Test one customer with Data Reprocess

Use the disabled-rule test path before the rule starts handling new customer events:

Save the customer rule disabled.
Run Data Reprocess against one resource ID.
Check the result in the Activity Log.
Enable the rule after checking that result.

Data Reprocess can then apply a rule to existing data by a specific resource ID, a date range or all resources. Rules themselves are event-triggered. Scheduled batch tagging uses Data Reprocess over a date range or Shopify Flow scheduled triggers.

Check rule results and quota in the app

Every rule trigger appears in the Activity Log with a timestamp, details and a status of Success, Failed or Pending. Filter those entries by category, status or date range when checking how a customer rule ran.

The app counts an operation whenever it modifies a resource, and one tag applied counts as one operation. The quota resets monthly. Billing & Usage shows the current plan, this month's usage against the limit, the last three months of usage and a progress bar.

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