Automation — Overview
Ce contenu n’est pas encore disponible dans votre langue.
The automation system lets you set up rules that react to player events and automatically execute actions — accrue bonuses, send push notifications, manage groups. Rules are configured at the organization level and apply to all clubs or selected ones.
Where to find it
Section titled “Where to find it”In the left sidebar, select your organization, then go to the Automation section. The page shows a list of all rules with name, active status, and creation date.
Creating a rule
Section titled “Creating a rule”Click Create rule. A dialog with all settings will open.
General settings
Section titled “General settings”| Field | Description |
|---|---|
| Rule name | Required. A short label for identification. Example: “5% cashback on order” |
| Description | Optional notes for the team |
| Rule active | On/off toggle. An inactive rule is saved but not executed |
| Clubs | Empty = applies to all clubs; select specific ones to limit scope |
Trigger
Section titled “Trigger”The trigger is the event that fires the rule. One rule — one trigger.
| Trigger | When it fires |
|---|---|
| Session completed | A player ends a gaming session |
| Balance top-up | A player tops up their gaming balance |
| Order payment | A player pays for an order (bar, shop) |
| Balance withdrawal | Funds are deducted from a player’s balance |
| Group assigned | A player is added to a group |
| Group unassigned | A player is removed from a group |
If you need different actions for different events — create separate rules.
Conditions (optional)
Section titled “Conditions (optional)”Filter which players the rule fires for. Without conditions, the rule runs for every player who triggers the event.
Each condition: what to check → operator → value.
| Condition | What it means |
|---|---|
| Hours played | Total accumulated play time |
| Amount spent | Total amount spent by the player |
| Session count | Total number of completed sessions |
| Player group | Membership in a specific group |
| Real balance | Current gaming balance |
| Bonus balance | Current bonus balance |
Operators: ≥ > ≤ < = ≠
Multiple conditions are joined with AND or OR. Condition groups can be nested.
Actions
Section titled “Actions”What happens when the rule fires. You can add multiple actions — they execute in order.
Accrue bonuses
Section titled “Accrue bonuses”Adds to the player’s bonus balance. The amount is defined by a formula using event variables.
Available variables depend on the trigger:
| Trigger | Variables |
|---|---|
| Session completed | {{session_duration}} — session duration in seconds |
| Balance top-up | {{topup_amount}} — top-up amount |
| Order payment | {{order_total}}, {{paid_with_bonuses}}, {{paid_with_real}} |
| Balance withdrawal | {{withdrawal_amount}} |
| All triggers | {{total_hours}}, {{visit_count}}, {{total_spent}} |
Formula examples:
| Goal | Formula |
|---|---|
| Fixed 50 bonuses | 50 |
| 5% cashback on order amount | {{order_total}} * 0.05 |
| 10 bonuses per hour of session | {{session_duration}} / 3600 * 10 |
| 100 bonuses for every 10 hours total | {{total_hours}} / 10 * 100 |
Send push notification
Section titled “Send push notification”Sends a push notification to the player’s IZI mobile app.
- Title — up to 40 characters
- Message — up to 120 characters
Assign group
Section titled “Assign group”Adds the player to the selected group.
Unassign group
Section titled “Unassign group”Removes the player from the selected group.
Execution statuses
Section titled “Execution statuses”| Status | What it means |
|---|---|
| Completed | Trigger fired, conditions met, all actions finished successfully |
| Error | An error occurred while executing one of the actions |
| Skipped | Trigger fired, but conditions were not met — the rule intentionally did not run |
If a bonus was not accrued or a push was not received — check the execution status in the rule’s history.