Comparisons in Segment Filters

A comparison is the middle part of a segment rule, such as =, contains or is one of. It decides how a customer’s value is checked against the value you enter.

How It Works

Which comparisons you get depends on the field you pick.

Text Fields

Email, Customer country, Customer state/province, Customer city, the First order and Last order UTM fields, and the discount code fields take =, ≠ and contains.

• = matches the whole value. jane@example.com matches only that address.
• ≠ matches every other value.
• contains matches any part of the value. gmail.com matches every address at Gmail.

Text comparisons ignore capital letters, and spaces at either end. Customer city Toronto and toronto match the same customers.

For the location fields, type the value yourself: the two-letter country code, such as CA, the state or province code, such as ON, or the city name. If you pick one of the suggestions, such as “Canada” or “Toronto, Ontario, CAN”, the rule saves the name shown, and it matches no customers.

Used specific discount code looks at every code a customer has used. = SUMMER10 finds customers who used that code on any order. ≠ finds customers who never used it.

List Fields

Product, tag and lifetime UTM fields hold a list of values for each customer, such as every product tag they’ve bought. Has purchased product, Customer tags and UTM source are examples. They take is one of, is not one of and only includes.

• is one of matches customers who have at least one of the values you enter.
• is not one of matches customers who have none of them, including customers with an empty list.
• only includes takes one value, and matches customers whose list holds only that value. Customer tags only includes wholesale finds customers whose only tag is wholesale.

These match whole values only. Customer tags is one of organic doesn’t match a customer tagged organic cotton. Pick values from the suggestions as you type to get them exactly right.

Choice Fields

Loyalty group (RFM), SMS marketing consent, and the first and last order sales channel and source fields take =, ≠ and is one of. Pick the values from the list.

Numbers, Amounts and Dates

Order counts, amounts, percentiles and dates take =, ≠, <, ≤, > and ≥.

• Amounts are in your store’s currency.
• Dates compare whole days, in your store’s time zone.
• Settled unit return rate is a percentage: enter 40 for 40%.

Yes-or-no fields, such as Accepts email marketing, take = and a switch set to Yes or No.

What It Means for You

• Use contains for a pattern, such as an email domain or a campaign name that starts the same way each season.
• Use is one of with several values in one rule, instead of joining rules with OR.
• Customers who haven’t ordered count as zero in the order-count and money fields, such as Total orders, Total sales and Lifetime value (LTV). Total sales < 50 includes them, so add Total orders ≥ 1 to leave them out.
• Items purchased and its 90, 365 and 730-day versions never match a customer who hasn’t ordered. Items purchased < 3 leaves those customers out.
• Nor do Days since last order, Days since first order (by order date), Tenure in days, First order date, Last order date, the returns fields or the percentiles.
• ≠ on a field that holds one value, such as Email, Customer city or Loyalty group (RFM), also leaves out customers with no value in it.
• First order sales channel and Last order sales channel work the other way: with ≠, they keep customers who haven’t ordered.

Segment rules don’t take regular expressions. In a report’s Filters, the Email field does, with matches (regex).

Related

• How to Create a Custom Segment: building a segment from rules.
• How to Use Advanced Filters: the rules that narrow a report to matching orders.