Bonus Expiration Policy
เนื้อหานี้ยังไม่มีในภาษาของคุณ
Bonus Expiration Policy
Section titled “Bonus Expiration Policy”Bonus expiration is debiting bonuses the client has not spent for a long time. It is not a penalty but a reason to come back while the bonuses are still there. In IZI credited bonuses have no built-in expiry: expiration is set up with an automation rule with the «Debit bonuses» action.
Why expiration matters
Section titled “Why expiration matters”Without expiration bonuses pile up for years and do not drive visits. A client with 5000 bonuses and no deadline is in no hurry. The same client, warned that bonuses burn after a month unspent, is more likely to come.
Two expiration schemes
Section titled “Two expiration schemes”| Scheme | Rule event | When it fires |
|---|---|---|
| Bonuses not spent | «Bonuses not spent» | For N days the client has bonuses but paid for nothing with them |
| No visits | «No visits» | For N days the client had no game session; with «Debit bonuses» in the rule, it fires only when the bonus balance is not zero |
Both events repeat every N days until the client pays with bonuses (or comes). N is from 1 to 365 days. Counting starts no earlier than the rule was switched on, so nobody’s bonuses burn on launch day. If the client has several wallets in the network, the rule works in each separately. Exact counting rules — in the triggers catalog.
Recommended periods
Section titled “Recommended periods”Pick the period by visit frequency:
| Average visit frequency | N for «Bonuses not spent» |
|---|---|
| Several times a week | 30–60 days |
| Once every 1–2 weeks | 60–90 days |
| Once a month or less | 90–180 days |
Too short — clients cannot spend in time and lose trust in the program. Too long — no incentive to return.
Prerequisites
Section titled “Prerequisites”- The «Automation» role permission in the organization.
- Clients know about the burn rule — for example, from the club’s loyalty program terms.
Step 1. Create the rule
Section titled “Step 1. Create the rule”In the organization menu open Marketing → Automation and click Create rule.
| Field | Value |
|---|---|
| Rule name | «Bonus burn — 60 days unspent» |
| Trigger type | Date |
| Client event | Bonuses not spent |
| Days without paying with bonuses | 60 |
| Clubs | Empty — all clubs, or selected ones |
Step 2. Set the debit
Section titled “Step 2. Set the debit”Add the Debit bonuses action with a formula:
| How to burn | Formula |
|---|---|
| All bonuses at once | {{bonusBalanceMajor}} |
| 20% per period N | {{bonusBalanceMajor}} * 0.2 |
If the client has fewer bonuses than the formula gives, only what is available is debited.
Step 3. Warn the client
Section titled “Step 3. Warn the client”Add Send push as the second action: title up to 40 characters, text up to 120. For example: «Bonuses expired» — «Your bonuses burned after 60 days unspent. New ones come with your next top-up». The notification goes out only after a successful debit.
To warn in advance, create a separate «Bonuses not spent» rule with a smaller N (e.g. 50) and only «Send push». Note: both rules repeat every own period, and from the second cycle their days drift apart.
Step 4. Enable and check
Section titled “Step 4. Enable and check”Turn on Rule is active and save. The first debits come N days after enabling. Check them in Marketing → Automation → Run history: a run shows its variables — «Days without paying with bonuses» and the bonus balance — and the client card shows the bonus debit.
Common errors
Section titled “Common errors”| Symptom | Fix |
|---|---|
| Nothing burned on the day of enabling | Expected: days count from when the rule was enabled |
| A client’s bonuses did not burn | Check: they paid with bonuses in the last N days; the rule is enabled and in its active period |
| A run with the «Failed» status | Open the run: a common cause is that the client is banned in the club, so their balance cannot be debited |
Related pages
Section titled “Related pages”- Client bonus account — how bonuses are stored
- IZI bonus engine — the full system architecture
- Automation actions catalog — the «Debit bonuses» action
- Top-up bonus — the main bonus credit scenario
คำถามที่พบบ่อย
Do bonuses in IZI expire on their own?
No. Credited bonuses have no expiry — without a burn rule they are kept indefinitely. Expiration is set up with an automation rule with the «Debit bonuses» action.
Does the client get a notification about burned bonuses?
If you add the «Send push» action to the burn rule — yes, at the moment of the debit. There is no separate «bonuses expiring soon» event.
Does a manual debit reset the day count?
No. For the «Bonuses not spent» event only paying for games, the bar or combos with bonuses resets the count. Manual debits by an administrator and burns by rules do not.
Can I extend bonuses for a specific client?
No. If the client already has bonuses, a new credit does not extend the count — only a bonus payment resets it. The count starts from a credit only if there were no bonuses before it. You can exclude a client from the rule with a group: the condition «User groups» «Does not include» an exclusion group.
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