The filters and thresholds available to refine a segment
A single condition already gives you a usable segment: “customers who have completed at least one mission”. Thresholds and filters are there to narrow that condition down — how many missions, which ones, over which period. They are always optional, and they differ for every type of condition.
💡 The list of thresholds and filters depends on the BASED ON field. If you cannot find the criterion you are looking for, first check that you started from the right event.
Threshold or filter: which one should you use?
Both refine a condition, but not at the same level.
A threshold (the THRESHOLD field) applies to a cumulative total, calculated over the whole period: “more than €300 spent”, “at least 3 missions completed”.
A filter (the FILTERS field) applies to each event taken separately: “orders over €100”, “orders delivered to Lyon”.
Careful: several labels are exactly the same in the two menus without meaning the same thing. Total amount, Total discounts, Total taxes, Number of products, Number of variants, Total quantity, Points earned and Total points exist as a threshold and as a filter alike. As a filter, Total amount means “orders over €100”. As a threshold, it means “more than €300 accumulated over the period”. You can also combine one threshold and several filters within the same condition.
💡 If you are looking for an average — average basket, average points per mission — look at the thresholds: the “average” metrics only exist there.
Choosing the period
The PERIOD field sets the window over which the condition is evaluated. Five options, the same for all eleven events: All time (the entire history, the default value), Last 7 days, Last 30 days, Last 90 days and Last 365 days.
The seven comparison operators
A threshold is built from three parts: a metric, an operator and a value. The table below lists the seven available operators, common to every threshold, with a sample setting for each.
Operator | What it means | Sample setting |
Is equal to | Strictly equal to. The default value. | Number of orders / Is equal to / 1: customers with a single order |
Is not equal to | Not equal to. | Tiers reached / Is not equal to / 0: customers who have reached at least one tier |
Is greater than | Strictly greater than. | Total amount / Is greater than / 300: more than €300 accumulated |
Is greater than or equal to | Greater than or equal to. | Number of missions / Is greater than or equal to / 3: at least 3 missions |
Is less than | Strictly less than. | Number of orders / Is less than / 2: one order at most |
Is less than or equal to | Less than or equal to. | Average amount / Is less than or equal to / 30: small average baskets |
Is between | Between two values. | Total points / Is between / 500 and 1,000: a points balance bracket |
Adding a threshold or a filter
In your condition, find the THRESHOLD or FILTERS row.
Click + Add a threshold or + Add a filter.
Choose the metric or the filter from the list, then set the operator and the Value field.
Repeat as many times as needed to add several filters to the same condition.
At any point, the Segment preview section and its Calculate button count the customers matched. Use it after every addition: it is the fastest way to spot the criterion that empties your segment.
The Completed orders event is the richest in the builder: eleven threshold metrics and seventeen filters. The table below lists the thresholds, which all apply to a cumulative total calculated over the period.
Threshold metric | What it aggregates, and a sample setting |
Number of orders | The number of orders over the period. Number of orders / Is greater than or equal to / 3: at least 3 orders. |
Total amount | The amount accumulated over the period. Total amount / Is greater than / 300: more than €300 spent. |
Average amount | The average basket over the period. Average amount / Is greater than / 150: an average basket above €150. |
Total quantity | The total quantity of items bought over the period. |
Average quantity | The average number of items per order. |
Number of products | The number of products bought over the period. |
Total discounts | The total amount of discounts. Total discounts / Is greater than / 100: the customers most sensitive to promotions. |
Average discount | The average discount per order. |
Number of variants | The number of variants bought over the period. |
Total taxes | The total amount of taxes. |
Average taxes | The average amount of taxes per order. |
The seventeen filters below apply order by order, not to a cumulative total.
Filter | What it does, and a sample setting |
Purchase window (days) | Restricts the condition to the orders of the last X days, as a rolling window. Purchase window (days) = 30: the orders of the past month. |
Order date | Restricts the condition to a fixed date or date range. Useful for a one-off campaign. |
Has claim code | Indicates whether the order included a discount code issued by Loyoly. |
Channel | The sales channel the order was placed on. |
Shipping country | The country of the shipping address. Shipping country = Spain: your customers on the Spanish market. |
Carrier identifier | The identifier of the carrier selected for the order. |
Shipping city | The city of the shipping address. Shipping city = Lyon: the customers shipped to Lyon. |
Tags | The tags attached to the order. |
Products | The orders containing one or more specific products. Select the product: the buyers of that item. |
Variants | The orders containing one or more specific variants — a size, a color. |
Collections | The orders containing products from one or more collections. |
Number of products | The number of products in the order. Number of products / Is greater than / 3: the well-filled baskets. |
Number of variants | The number of variants in the order. |
Total amount | The amount of the order. Total amount / Is greater than / 100: keeps only the orders over €100. |
Total quantity | The total quantity of items in the order. |
Total discounts | The amount of the discounts applied to the order. |
Total taxes | The amount of the taxes on the order. |
Completed missions
The Completed missions event targets customers based on what they have actually done in your program. Three threshold metrics and seven filters.
Threshold or filter | What it does, and a sample setting |
Threshold — Number of missions | The number of missions approved over the period. Number of missions / Is greater than or equal to / 5: your most engaged customers. |
Threshold — Points earned | The total points earned through the missions matched. |
Threshold — Average points earned | The average number of points earned per mission. |
Filter — Completion window (days) | The missions approved in the last X days, as a rolling window. |
Filter — Completion date | The missions approved on a fixed date or within a fixed range. |
Filter — Mission type | The type of mission. Select the type matching reviews, or the one for photo and video content. |
Filter — Mission | One or more specific missions from your program. |
Filter — Mission template | The mission template used. |
Filter — Validation status | The validation status of the mission. |
Filter — Points earned | The points earned on a given mission. |
Points transactions
The Points transactions event targets points movements rather than where they come from. It is the building block of dormant points segments.
Threshold or filter | What it does, and a sample setting |
Threshold — Number of transactions | The number of points movements over the period. |
Threshold — Total points | The total points of the transactions matched. Total points / Is greater than / 500: more than 500 points accumulated. |
Threshold — Average points | The average number of points per transaction. |
Filter — Transaction window (days) | The transactions of the last X days. |
Filter — Transaction date | The transactions of a fixed date or range. |
Filter — Transaction type | The type of transaction. |
Filter — Event type | The type of event behind the transaction. |
Filter — Total points | The number of points of a given transaction. |
Rewards used and Rewards earned
Two separate events, not to be confused. Rewards used targets the customers who have redeemed a reward; Rewards earned targets those who have earned one, whether they used it or not.
Threshold or filter | What it does, and a sample setting |
Used — Order amount threshold | The total amount of the orders on which a reward was used. |
Used — Average order amount threshold | The average amount of those orders. |
Used — Discount amount threshold | The total amount of the discounts obtained through those rewards. |
Used — Average discount threshold | The average amount of those discounts. Careful: the same label exists under Completed orders, where it means the average discount per order. |
Used — Rewards used threshold | The number of rewards redeemed over the period. |
Used — Usage date filter | The rewards used on a fixed date or within a fixed range. |
Used — Usage window (days) filter | The rewards used in the last X days. |
Used — Reward filter | One or more specific rewards from your catalog. Select free shipping: the customers who used it. |
Used — Order amount and Discount amount filters | The same amounts, applied reward by reward instead of being accumulated. |
Earned — Rewards earned threshold | The number of rewards earned over the period. It is the only threshold of this event. |
Earned — Earned date and Earned window (days) filters | A fixed date range, or a rolling window of the last X days. |
Earned — Reward type and Reward filters | A family of rewards, or a specific reward from your catalog. |
Earned — Points cost filter | The number of points the reward cost. Useful to isolate the customers who redeem your most expensive rewards. |
Earned — Reward status filter | The state of the reward earned. This is the filter to use to tell apart a reward that was earned and never redeemed. |
Referrals (referrer) and Referrals (referee)
Two symmetrical events: Referrals (referrer) targets the referrer, Referrals (referee) targets the referee. Each one has a single threshold.
Threshold or filter | What it does, and a sample setting |
Referrer — Number of referrals threshold | The number of people referred. Number of referrals / Is greater than or equal to / 2: your active referrers. |
Referrer — Date filter | The referrals of a fixed date or range. |
Referrer — Window (days) filter | The referrals of the last X days. |
Referrer — Referrer reward type filter | The type of reward earned by the referrer. |
Referee — Referee order amount threshold | The amount of the order placed by the referee. |
Referee — Date and Window (days) filters | A fixed date range, or a rolling window of the last X days. |
Referee — Referee order amount filter | The same amount, applied referral by referral. |
Tiers, automations and notifications
Four events with simple thresholds — a single metric each — but whose filters allow precise targeting, on tiers in particular.
Event | Available threshold | Available filters |
Tier reached | Tiers reached — the number of tiers reached over the period. | Date, Window (days), Tier. To target a specific tier, use the Tier filter — here or in the Profile condition. |
Tier downgraded | Tiers downgraded — the number of tiers lost. Tiers downgraded / Is greater than or equal to / 1 over Last 30 days: the customers who have just lost their status. | Date, Window (days), Previous tier, New tier. The last two let you target a specific drop — from Gold to Silver, for example. |
Automations triggered | Number of automations — the number of automations triggered for this customer. | Date, Window (days), Automation, Trigger type. The Automation filter targets a specific journey: useful to exclude the customers who have already been followed up. |
Notifications sent | Number of notifications — the number of notifications sent. | Date, Window (days), Notification type. Handy to avoid over-contacting a customer who has already been notified recently. |
The Profile condition
The Profile condition works differently: it has no event, no period and no threshold. It describes who the customer is, not what they have done — so you go straight to a list of seven filters.
Filter | What it does, and a sample setting |
The customer's email address. | |
Age | The customer's age, to target an age bracket. |
Gender | The gender recorded on the customer profile. |
Language | The customer's language. Language = Spanish: communicate in the right language on a multi-market program. |
Tier | The customer's VIP tier. Tier = Silver, Gold: all the customers of those two tiers. |
Customer creation window (days) | The customers created in the last X days. Customer creation window (days) = 7: the week's new sign-ups. |
Customer creation date | The customers created on a fixed date or within a fixed range, to work on a sign-up cohort. |
Start with a single condition and a single criterion, then refine. A segment that is too constrained from the start often returns zero customers, with no way of telling which rule is to blame.
Use Calculate after every addition: it is the fastest way to see which criterion empties your segment.
The … window (days) filters are rolling windows: the segment recalculates on its own. The … date filters are fixed ranges, best kept for one-off campaigns.
Before choosing a threshold metric, check that a filter of the same name does not exist: the label is sometimes identical while the calculation is not.
If a filter does not behave the way you expected, contact our support team via the chat.





