Condition Categories

Category	What It Filters
Groups	Combine conditions into logical blocks; nest existing segments inside new ones.
Campaigns	Filter by customer reactions to past campaigns: impacted vs. non-impacted, redeemed vs. not redeemed.
Customers	Demographics, location, custom fields, tier, usual store, and calculated attributes.
Coupons	Status of sent coupons (redeemed / not redeemed), number of coupons received in a period.
Consumption	Purchase data: average spend, number of visits, categories purchased, product-level behavior.
SQL	Custom-built conditions for highly specific segmentation needs.

How It Works

The condition builder evaluates these categories against real-time customer data at the moment an audience is used:

1. Groups — logical wrappers combining conditions with AND/OR.
2. Campaigns — filters based on past campaign interactions (was impacted, redeemed, did not redeem).
3. Customers — demographic and profile-level filters.
4. Coupons — filters by sent coupon status (redeemed vs. not).
5. Consumption — purchase data filters (spend, frequency, categories).
6. SQL — raw query for advanced use cases.

Condition Reference

Groups

Condition	What It Does
Group	Wraps multiple conditions into a logical block, allowing mixed AND/OR logic. Drag alongside conditions; combine as many as needed.
Audience	Inserts an existing audience segment as a condition. Supports "Belongs to" / "Does not belong to" operators. Only non-nested segments (those containing no other segments) are available.

note

Audiences in the dropdown are sorted by category — audiences without a category appear first. If you don't see a recently created segment at the top, search by name directly.

Campaigns

Condition	What It Does
Campaigns impact	Filters by whether the customer was impacted (or not) by a specific campaign, including options for last delivery, last delivery -1, some deliveries, or all deliveries.
Email	Filters by email campaign interactions: opened, did not open, clicked, or did not click; filterable by delivery instance.

Customers (23 conditions)

Condition	What It Filters
Available score	Points balance: Equal / Not equal / Less than / Greater than / Between
Best sales	Customers in a best-sales segment during selected months (dynamic or static)
Birthday	Birthday date relative to a selected date (Equal / Less / Greater)
Buyers type	High-buyer or low-buyer segment by product category, per month
Channel status	Whether the customer has SMS, Email, or App channel configured and its status (Active / Pending / Empty / Invalid / Does have App / Does not have App)
City	Registered city: Equal / Not equal / Contains / Starts with / Ends with
Client category	Expenditure tier (Gold / Silver / Bronze) relative to total company revenue; filterable by product or date range
Collective	Customer belongs to (or does not belong to) a retailer-defined collective
Country	Country set in customer profile
Custom fields	Any custom field defined on the customer record (e.g. Language); supports Belongs to / Does not belong to
Customer attributes	Calculated attributes (e.g. Total spending this month); operators vary by attribute type
Email	Customer email address: Equal / Not equal / Contains / Starts with / Ends with
Expenditure	Expenditure segment (segment A, B, etc.) by month
Gender	Masculine or Feminine
ID	Customer ID: Starts with / Ends with / Equal / Contains / Greater / Less
Name	Customer name: Equal / Not equal / Contains / Starts with / Ends with
Phone prefix	Country phone prefix
Postal code	One or multiple zip codes (comma-separated, no spaces)
Purchase	Purchase segment (auto-generated monthly) for a static or dynamic month
Recency	Recency segment: Recovered / Fresh / Usual (purchased in last 2 months)
Registration date	Date the customer enrolled in the loyalty scheme
Registration store	Store where the customer was first registered
State	Registered state/region: Equal / Not equal / Contains / Starts with / Ends with
Unsubscribe/Bounce	Filters by email opt-out (unsubscribed) or delivery failure (bounce); supports filtering by bounce type: generic error, hard bounce, content issues, frequency limits, mailbox unavailable, sender reputation, server technical issues
Usual store	Calculated usual store (based on retailer-configured parameters); supports Belongs to / Does not belong to

Coupons

Condition	What It Filters
Coupons	Customers who received a specific coupon; filterable by status (Pending / Printed / Redeemed / Canceled) and delivery instance
Number of coupons	How many coupons a customer received; filterable by status and date range; supports "Include people without coupon" for less-than operators

Consumption

Condition	What It Filters
Last purchase date	Date of customer's most recent purchase; supports Equal / Less than / Greater than / Between
Number of different categories	How many distinct product categories the customer bought within a taxonomy and date range
Purchase average	Average cart value; filterable by channel, date range, and store
Purchases	Whether the customer has (or has not) bought a specific product, feature, or made any purchase; filterable by channel, date, store, and amount
Margin %	Margin percentage across purchases: (Total cart − tax − cost) / (Total cart − tax); filterable by feature and date range
E-commerce	E-commerce-specific purchases; filterable by checkout date vs. delivery date, shipping cost, and payment cost

tip

Validate SQL conditions with your Customer Success Manager before use in production campaigns.

SQL

Condition	What It Does
SQL	Custom SQL query returning a customer_id column. All table references must be namespaced with their dataset. Use only when other conditions cannot achieve the required segmentation.

Configuration

Conditions are selected in the audience builder at Campaign Personalization → Audiences → New Audience → Add Condition. See Create an Audience for the full step-by-step guide and Dynamic vs. Static Dates for date filter options.