Segment Targeting in Bonuses
A segment is the condition IZI uses to select which clients a bonus rule applies to. Without a segment, a rule fires for everyone. With a segment, it fires only for the right group — newcomers, birthday clients, regulars, or dormant accounts. Segments are evaluated in real time at the moment of each transaction, so the check is always current. No manual list updates are needed: clients move in and out of segments automatically as their data changes.
Built-in segments
Section titled “Built-in segments”IZI ships with five ready-to-use segment types that cover the most common loyalty scenarios:
Newcomers — clients registered within the last N days. Use this for welcome programs: the first one or two top-ups from a new client receive an elevated bonus percentage.
Birthday clients — clients whose birthday falls today or within the next N days. Lets you run automatic birthday bonuses without any manual work. See Birthday bonus for a dedicated setup guide.
Regulars — clients whose visit frequency exceeds a threshold over the last N days. Designed for loyalty programs targeting your core audience — the clients who already visit often and notice when their conditions improve.
Dormant — clients who have not visited in N days. Re-engagement bonuses give them a reason to return.
All clients — the default: no segment filter, the rule applies to everyone.
How segment evaluation works
Section titled “How segment evaluation works”When a qualifying event fires (a top-up, a purchase), IZI runs this check:
- Does the bonus rule have a segment condition?
- Does this client currently meet that condition?
- If yes — accrue the bonus. If no — skip.
Because the check happens at operation time, a client who became a “regular” yesterday is already eligible. One who lapsed and re-entered dormancy is caught immediately.
Example configurations
Section titled “Example configurations”Welcome program for newcomers
- Segment: Newcomers (registered in the last 30 days)
- Event: Balance top-up
- Bonus: 15% of the top-up amount
- Limit: 2 uses per client
A new client’s first two top-ups carry a higher bonus rate, encouraging them to invest in more than a single visit.
Re-engagement for dormant clients
- Segment: Dormant (no visits in 45+ days)
- Event: Balance top-up
- Bonus: fixed 200 units
- Limit: 1 use per client
The client sees in the app that their bonuses are expiring (or receives a push notification), returns, and collects 200 units on their first top-up back.
Loyalty upgrade for regulars
- Segment: Regulars (3+ visits in the last 30 days)
- Event: Balance top-up
- Bonus: +5% stacked on top of the standard tier
Regulars receive slightly better conditions than the base rate — a difference they notice and value.
How to configure a segment on a rule
Section titled “How to configure a segment on a rule”- Go to Bonuses → Create rule (or open an existing rule).
- In the Conditions section, select Client segment.
- Choose the segment from the list, or configure its parameters (N days, visit threshold).
- Save the rule.
The rule becomes active immediately. Existing clients who already meet the condition are eligible on their next qualifying event.
See also
Section titled “See also”- Bonus rule conditions — full list of conditions available on a rule
- Birthday bonus — birthday segment in action
- Goal: newcomer trial pack — newcomer segment in action
- Bonus engine overview — full architecture of the IZI bonus system
Frequently asked questions
Are segments static lists or dynamic?
Segments in IZI are dynamic. A client enters and exits a segment automatically as their parameters change — visit frequency, registration date, birthday. No manual list management needed.
Can one rule target multiple segments at once?
One rule works with one segment. To cover different segments, create separate rules with the required conditions for each.
How do I know how many clients are in a segment before activating a rule?
In the Clients section, apply the same filter conditions you plan to use in the rule and check the result count before creating or enabling the rule.