Conditions in IZI Automation Rules
Conditions in IZI Automation Rules
Section titled “Conditions in IZI Automation Rules”A condition is a filter that determines which clients the rule fires for. If there are no conditions, the rule runs for all clients who triggered the event. If conditions are set, only clients who match them.
Conditions are configured when creating a rule → Create an automation rule.
Condition structure
Section titled “Condition structure”Each condition has three elements:
[What to check] [Operator] [Value]For example: Hours played ≥ 50
Parameters available for checking
Section titled “Parameters available for checking”Accumulated client metrics
Section titled “Accumulated client metrics”Check the client’s historical data — values accumulate over all time.
| Parameter | What it means |
|---|---|
| Hours played | Total play time across all sessions |
| Session count | Total number of completed sessions |
| Amount spent | Total amount spent by the client over all time |
Current account balance
Section titled “Current account balance”| Parameter | What it means |
|---|---|
| Real balance | Client’s current monetary balance |
| Bonus balance | Client’s current bonus balance |
Group membership
Section titled “Group membership”| Parameter | Operators | Use case |
|---|---|---|
| Player group | = (member), ≠ (not a member) | Apply rule only to VIP, only to new clients, exclude a specific segment |
Current event parameters
Section titled “Current event parameters”Available only for specific events — checks characteristics of the current operation, not the client’s history.
| Parameter | Event | What it means |
|---|---|---|
| Top-up amount | Balance top-up | Amount of the specific top-up |
| Session duration | Session completed | Duration of the current session in seconds |
| Order amount | Order payment | Amount of the specific order |
Operators
Section titled “Operators”| Operator | When to use |
|---|---|
≥ | Greater than or equal to (for thresholds: “from 300”, “from 10 hours”) |
> | Strictly greater than |
≤ | Less than or equal to |
< | Strictly less than |
= | Equal to (for group membership, exact values) |
≠ | Not equal to (for exclusions) |
Combining multiple conditions
Section titled “Combining multiple conditions”Multiple conditions are joined with AND or OR:
- AND — all conditions must be met simultaneously
- OR — at least one must be met
Condition grouping
Section titled “Condition grouping”Conditions can be nested in groups for complex logic. Example:
(Hours played ≥ 10 AND Hours played < 50)OR(Player group = VIP)This rule fires for clients with 10–50 hours or for VIP clients regardless of their hours.
Practical examples
Section titled “Practical examples”Bonus only on large top-ups
Section titled “Bonus only on large top-ups”Top-up amount ≥ 500The rule fires only when a client tops up 500 or more. Smaller top-ups get no bonus.
Rule for VIP clients only
Section titled “Rule for VIP clients only”Player group = VIPAdd this to a higher cashback rule so the VIP segment earns more.
Transition to “Silver” rank (hours in range)
Section titled “Transition to “Silver” rank (hours in range)”Hours played ≥ 36000 (in seconds)ANDHours played < 180000Full rank system example using conditions like these → Client rank system.
Exclude clients from “Blocked” group
Section titled “Exclude clients from “Blocked” group”Player group ≠ BlockedAdd this condition to any bonus accrual rule to exclude unwanted segments.
New clients only (first event)
Section titled “New clients only (first event)”Session count ≤ 1For a welcome bonus on the first session.
When conditions are not needed
Section titled “When conditions are not needed”If the rule should apply to everyone — leave the conditions section empty. This is fine for:
- Basic cashback on every bar purchase
- Notification on every top-up
- Fixed bonus for any completed session
See also
Section titled “See also”Frequently asked questions
What happens if I don't add conditions to a rule?
The rule will fire for all clients who triggered the event — with no filtering. This is fine for rules like 'bonus for everyone who completed a session'. For targeted scenarios (VIP only, new clients only, large top-ups only) conditions are required.
Does the 'Player group' condition work with AND or OR logic?
It checks whether the client belongs to that group. If you add two group conditions with OR, the rule fires for clients in either of the two groups.
Can I check the amount of a specific top-up rather than total spending?
Yes. The 'Top-up amount' parameter (for the 'Balance top-up' event) checks the current top-up specifically. The 'Amount spent' parameter reflects the client's cumulative historical spending.
How do I make a rule that only fires on a client's first top-up?
Add a condition: session count = 0 (client has never played) or use the event-specific parameter. Another option — create a dedicated 'New client' group and check membership in it.