Bonus Rule Conditions
Bu içerik henüz dilinizde mevcut değil.
Bonus Rule Conditions
Section titled “Bonus Rule Conditions”Bonuses in IZI are credited by automation rules: event → conditions → the «Add bonus» action. Conditions decide who gets the bonus; the action formula decides how much. Below — what can be limited and how.
Amount threshold
Section titled “Amount threshold”A bonus only for a top-up or purchase above an amount — a condition on an event variable:
| Event | Condition |
|---|---|
| Balance topped up | «Top-up amount» ≥ 500 |
| Purchase made | «Order total» ≥ 1000 |
| Purchase made | «Tariffs paid with real» ≥ 300 |
How to pick the threshold: from the average top-up (how to find the average check) — the first tier is usually the baseline × 1.2–1.3. For a ladder create several rules with non-overlapping ranges: ≥ 500 AND < 1000, ≥ 1000.
Client group
Section titled “Client group”A rule for one group: «User groups» «Includes» VIP. To exclude a group: «Does not include». Groups are filled manually or by the «Assign group» action of another rule — they do not change on their own. More — Bonus targeting.
Client history
Section titled “Client history”The client’s accumulated figures in the club: «Play time (sec)», «Sessions count», «Total spent», «Spent (real)», «Spent (bonus)», the current «Gaming balance» and «Bonus balance», and «Gender». For example, a newcomer bonus — «Sessions count» = 0 in a top-up rule.
The rule’s active period
Section titled “The rule’s active period”The rule form has an Active period field — start and end, both optional. Outside the period the rule does not fire: handy for dated promotions, no need to switch off by hand. There are no weekday or time-of-day limits.
One-time bonuses
Section titled “One-time bonuses”There is no «at most N times per client» limit. One-time behaviour is built like this:
- with a counter — «Sessions count» = 1 in a «Session ended» rule;
- with a group — the rule assigns a marker group, and «User groups» «Does not include» it prevents repeats.
Birthday is one-time by design: a rule fires for a client once a year.
Credit size
Section titled “Credit size”The size is set by the «Add bonus» formula:
| Type | Formula example | When to use |
|---|---|---|
| Percentage | {{topupAmountMajor}} * 0.1 | Top-up ladders, cashback |
| Fixed amount | 200 | Welcome bonus, birthday bonus |
The result is rounded to whole units. There are no min or max functions; cap the bonus with a separate fixed-amount rule for large operations.
Combining conditions
Section titled “Combining conditions”Conditions combine with AND or OR and nest in groups. Example: «10% on top-ups from 300, only for the Newcomers group, in January» — event «Balance topped up», conditions «Top-up amount» ≥ 300 AND «User groups» «Includes» Newcomers, active period — January.
All operators and variables — in Conditions in automation rules.
Related pages
Section titled “Related pages”- Bonus engine in IZI — how the system processes rules
- Segment targeting in bonus rules — working with client groups
- Top-up bonus — conditions in a real scenario
Sık sorulan sorular
Can I set multiple conditions on a single rule?
Yes. Conditions combine with AND (all must be met) or OR (at least one), and condition groups can be nested.
What happens if a client qualifies under several rules at once?
Bonuses are credited under every matching rule. Rules do not know about each other — separate them with conditions so the client does not get two credits for one event.
How do I credit a bonus to a client only once?
There is no separate credit limit. One-time behaviour comes from conditions: «Sessions count» = 1 for a first-session bonus, or a group — the rule assigns a «Got bonus» group and the condition «User groups» «Does not include» it blocks repeats.
Can I limit a bonus to weekdays or hours?
No. A rule can be limited only by its active period — start and end date and time.
IZI LLC (ООО «ИЗИ»), TIN 7842227686, OGRN 1257800012249, office 1, premises 3-N, lit. A, 15-17 Perekupnoy lane, Saint Petersburg, 191024, Russia, admin@izi.is · Cookie settings