Recommended Real-Time Events
In addition to Optimove's out-of-the-box (OOTB) events, we strongly recommend implementing a set of custom events to enable richer segmentation, more advanced real-time use cases, and improved compliance coverage.
The events on this page are based on common requirements across multiple operators and are designed to support marketing, product, and regulatory use cases.
Terminology and must-have requirements may differ by market. Adapt event names and properties to your local operating region where needed.
Out-of-the-Box (OOTB) Events
Before implementing custom events, ensure you have integrated Optimove's standard OOTB events. These provide the baseline data required for segmentation and campaign targeting.
For the full OOTB event schema, see the Mandatory Properties for Standard Events, General Events, and Gaming & Sports Events references.
Additional Recommended Events
| Event Name | Description |
|---|---|
| Balance Update | Triggered whenever a player's balance changes (deposit, bet, withdrawal). |
| Bonus Opt-in | Fired when a player opts into a bonus or tournament. |
| Big Win/Loss | Fired when a player wins or loses above a defined threshold. |
Player Behavior
These custom events enable advanced segmentation and personalisation:
- Session start / Session end (include device and channel)
- Game launch / Game exit
- Bet placed (game, amount, currency)
- Win / Loss (amount, RTP context if available)
- Deposit initiated / Deposit completed / Deposit failed
- Withdrawal initiated / Withdrawal completed / Withdrawal failed
- Bonus opted in / Bonus redeemed / Bonus expired
- Promo page viewed / CTA clicked
- Favourite game added / Favourite game removed
Compliance & Responsible Gaming (RG)
These events are critical for regulatory compliance and proper communication controls. Implement these early in the integration process.
| Event Name | Description |
|---|---|
| Self Exclude (Set/Update) | Player chooses to block access, betting, and communications. |
| Self Exclude (Remove) | Self-exclusion is lifted (IsRemoving = true). |
| Player Break | Temporary restriction from accessing the platform and communications. |
| Blocked | Operator blocks the player from accessing the platform. |
| Bonus Abuser | Player flagged as ineligible for promotional communications. |
| Failed ID Checks | Player failed KYC and cannot transact or receive communications. |
| Reality Check Set | Player enables session time notifications. |
| Deposit Limit Set | Player defines a deposit limit (daily/weekly/monthly). |
| Deposit Limit Reached | Player reaches their defined deposit limit. |
| Deposit limit changed / removed | |
| Loss limit set / changed / removed | |
| Session limit set / changed / removed | |
| Self-exclusion initiated / confirmed | |
| Cool-off period activated | |
| Reality check triggered / acknowledged | |
| RG assessment score updated | |
| Account verification status change (KYC) | |
| Account blocked / reinstated | |
| Email Verified | |
| Consent Update |
Several of the RG events above overlap with Optimove's OOTB Self-Exclusion events (Initiated, Activated, Updated, Violation Attempt, Lifted). Where an OOTB event covers the same scenario, use the OOTB schema. Custom events are only needed where no OOTB equivalent exists.
For OOTB self-exclusion schemas, see the Gaming & Sports Events reference.
Best Practice Recommendations
- Start with high-impact events. Focus first on deposits, bets, sessions, and bonuses.
- Prioritise RG and compliance events early to ensure proper communication governance.
- Align with business use cases. Implement events that directly support clients campaign strategies and segmentation needs.
- Iterate over time. Event coverage can expand as new use cases emerge. Implementing these events will significantly enhance clients ability to leverage Optimove's capabilities, enabling more effective campaigns, better player insights, and full compliance coverage.