Welcome Bonus for First-Time Players in IZI
Este conteúdo não está disponível em sua língua ainda.
Welcome Bonus for First-Time Players — Set It Up Without Double-Paying
Section titled “Welcome Bonus for First-Time Players — Set It Up Without Double-Paying”A welcome bonus is a classic way to introduce a new player to the club’s loyalty system and give them a reason to come back. IZI has no dedicated “First Visit” or “Registration” trigger: the automation engine reacts to concrete events — session completed, balance topped up, and others.
For this reason, the welcome bonus is built on the «Пополнение баланса» (Balance topped up) event with a sentinel group preventing double-paying. This is the only reliable way to pay the bonus exactly once.
Why checking “Sessions count = 0” does not work
Section titled “Why checking “Sessions count = 0” does not work”Intuitively it seems simple: the player has not played yet — they must be new, check “Sessions count = 0”. In practice this fails.
Consider the scenario: a player registers and tops up — sessions count is zero, the rule fires, bonus credited. They immediately top up again before playing — sessions count is still zero, the rule fires again, bonus credited again. The player receives the welcome bonus twice before their first session.
The reliable solution is a sentinel group: a utility group called “Bonus given” that is assigned to the player at the moment of the first credit. The “does not include” condition blocks every repeat firing.
How the sentinel group works
Section titled “How the sentinel group works”The logic is straightforward:
- Event «Пополнение баланса» fires → check whether the player is in the “Bonus given” group.
- Not in the group → first time: assign the sentinel + credit the bonus + send notification.
- In the group → condition fails, rule skips this player.
On every subsequent top-up the player is already in “Bonus given” → condition “does not include” fails → no bonus is credited. Once, and done.
Step 1 — Create the sentinel group
Section titled “Step 1 — Create the sentinel group”Club → Settings → Player Groups («Группы игроков») → Add group.
Create a group with a clear internal name: “Bonus given”, “Welcome”, or any name you prefer. This is a utility group — the player never sees it, it exists only for the automation logic.
Step 2 — Create the rule in Automation
Section titled “Step 2 — Create the rule in Automation”Organization → Marketing → Automation («Автоматизация») → Create rule.
Fill in the rule:
Event: «Пополнение баланса» (Balance topped up)
Condition: «Группы пользователя» (Player’s groups) «не включает» (does not include) “Bonus given”
Actions (order matters):
- «Присвоить группу» (Assign group) → “Bonus given” ← first action, set sentinel immediately
- «Начислить бонусы» (Add bonuses) with formula, e.g.
{{topupAmountMajor}} * 0.20(20% of first top-up amount) - «Отправить push» (Send notification) → welcome message
Why the sentinel must be the first action. If “Add bonuses” is first and “Assign group” is second, and the rule is interrupted between them for any reason — the bonus is credited but the sentinel is never placed. The rule will fire again on the next top-up. Sentinel first is the safety net against that scenario.
For more on bonus formulas see How to configure top-up bonus percentage.
Honest limits
Section titled “Honest limits”- No “Registration” or “First Visit” trigger exists. IZI automations fire on events that happen in the system. There is no dedicated new-customer event — hence the sentinel pattern.
- Bonus is tied to first top-up, not first visit. If a player walks in and starts a session immediately without a prior top-up, the rule will not fire at that session — only on the next top-up. In practice most players top up at registration or before playing, so these coincide.
- The sentinel stays permanently. A player with “Bonus given” will not receive the welcome bonus again — even after a long break. Reactivating lapsed players is a separate scenario with a different sentinel group.
- Per-club accumulation. In a multi-club network, groups and rules are configured per club independently. A sentinel from club A has no effect in club B.
How to measure it is working
Section titled “How to measure it is working”Open Analytics → Bonus on top-up. The “By rules” section shows firing count and amounts per active rule. After the first new players come through, the row for your welcome rule will appear in the table.
Additional check: Organization → Marketing → Automation → your rule → History tab. A Completed entry means the rule fired. “Skipped” means the player was already in “Bonus given”.
See also
Section titled “See also”Perguntas frequentes
Is there a 'Registration' or 'First Visit' event in IZI?
No. Automations fire on concrete system events: session completed, balance topped up, purchase made, group assigned or unassigned. There is no 'new customer' event. That is why the welcome bonus is built on the 'Balance topped up' event with a sentinel group preventing repeat firing.
Why can't I just check 'Sessions count = 0'?
It is not reliable. If a player tops up twice before their first session, the sessions count at both top-ups is 0 — so the rule fires twice and the player gets a double welcome bonus. The sentinel group 'Bonus given' solves this: it is assigned on the first firing and blocks all subsequent ones.
What is a sentinel group and why is it needed?
A sentinel group is a utility group (e.g. 'Bonus given') that the automation assigns to the player at the moment of the first bonus. The condition 'Player's groups does not include Bonus given' is checked on every top-up: a new player doesn't have the group → rule passes; on the next top-up the group exists → rule skips. One bonus, once.
Why must 'Assign group' be the first action in the rule?
If 'Add bonuses' is first and 'Assign group' is second, and the rule is interrupted between the two actions for any reason — the bonus is credited but the sentinel is never set. The rule will fire again on the next top-up. Sentinel first is the safeguard: if something fails after the first action, no bonus is credited and no repeat can happen.
Can a returning player after a long break get the welcome bonus again?
No. The 'Bonus given' group stays in the player's profile permanently — the automation never removes it. If you want to reward returning players after a break, that is a separate scenario with a different sentinel group and a separate rule.
Does the rule fire regardless of how the player topped up — app, card, or cash?
Yes. The 'Balance topped up' event fires on any top-up method: mobile app, card at the terminal, or cash at reception. You can add an extra condition to restrict by top-up source if needed.
How do I verify the bonus was not paid twice?
Open Analytics → Bonus on top-up → 'By rules' section. The table shows firing count and amounts per active rule. Also check the player's profile: if the 'Bonus given' group is present, the rule fired exactly once. Subsequent entries in the rule's History will have status 'Skipped'.