Bingo
General Data Requirements
Before preparing your data tables, please review the following universal formatting rules.
The below represents Optimove's required data schema. If you are unable to provide your data in the requested schema, you will be requested to supply a clear mapping from your schema to the Optimove standard schema as part of the onboarding process. This ensures a smooth data integration and avoids delays.
Data Formatting
- Decimal Precision: All decimal-type attributes must be rounded to a maximum of four decimal places. For example, a value of
4.56789
must be formatted as4.5679
. This applies to all monetary fields and other decimal values. - Currency Conversion: All monetary figures must be converted into a single, consistent currency across all tables.
Required Data Tables
The following data tables describe the content, format, and labels of the required data.
- Customers – Each row describes the attributes of a single customer
- Wallet_Transactions – Each row describes a financial transaction
- Bingo_Games_Transactions – each row describes a daily aggregation of specific bingo rooms, player, and platform
- Bingo_Rooms_Catalog – bingo room IDs and their associated names and categories
Customers
Key | Field | Data Type | Description |
---|---|---|---|
PK | Player_ID** | string/int | Unique customer identifier |
Registration_Date** | date | Date the player registered | |
Email* | string (max 250) | Mandatory when using Optimail or if required by external ESP | |
Mobile_Number* | string | Mandatory if required by external service provider | |
Date_Of_Birth | date | Player's date of birth | |
Is_OptIn | string | Determines whether it is acceptable to send promotional messages to the specified player. Should hold the values 'Yes' or 'No'. | |
Allow_Email* | string | Determines whether sending promotional Email messages to the specified email address is acceptable. Should hold the values 'Yes' or 'No'. | |
Allow_SMS* | string | Determines whether sending promotional SMS messages to the specified mobile address is acceptable. Should hold the values 'Yes' or 'No'. | |
Allow_Push* | string | Determines whether sending promotional Push messages to the specified mobile number is acceptable. Should hold the values 'Yes' or 'No'. | |
Is_Email_Verified | string | Determines whether the email address is verified. Should hold the values 'Yes' or 'No'. | |
Is_SMS_Verified | string | Determines whether the mobile number is verified. Should hold the values 'Yes' or 'No'. | |
Is_Blocked | string | 'No’ = regular player; 'Yes’ = blocked player (e.g. fraud) | |
Is_Test | string | 'No’ = regular player; 'Yes’ = test player | |
Gender | string | Player’s gender. Must hold values ‘Male’, ‘Female’, ‘Unknown’ | |
Country | string | Player’s country | |
City | string | Player’s city | |
Address | string | Player’s address | |
First_Name | string | Player’s first name | |
Last_Name | string | Player’s last name | |
Language | string | Player's language | |
Balance | Decimal/int | The monetary value of a player’s current balance | |
Casino_Name | string | When multiple casino platforms exist | |
Alias | string | User name | |
Currency | string | Player’s currency | |
Referral_Type | string | The method by which the player was referred to your site (e.g., SEO, Affiliate, Advertising, Marketing, etc.). | |
Affiliate_ID | string | Affiliate identifier or name | |
Registered_Platform | string | The platform the player had registered with (e.g. Web, Android App, iOS App, etc.) | |
Last_Login_Date | date | The date of the player’s last login to the website | |
Allow_Whatsapp | string | Determines whether sending promotional WhatsApp messages to the specified mobile number is acceptable. Should hold the values 'Yes' or 'No'. | |
LastUpdated | date | Date when the record was last modified or added (Mandatory in case of DB to DB connection) | |
Is_Optin_Email_Time_Stamp* | Timestamp | Determines when it is acceptable to send promotional Email messages to the specified email address in case of approval |
Notes:
- Please include any additional information that you find helpful
- IsOptinEmailTimeStamp* - In case Optimove will manage the “unsubscribe” for the Opti-Mail integration please include an additional column to describe when the customer opts in \ out, in order to allow perfect sync with the daily batch.
- The email field must not exceed 250 characters (varchar(250)). This constraint is required to ensure compatibility with database and external ESP systems.
*=Mandatory if required for the execution channel integration
**=Always mandatory
Wallet_Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Transaction_ID** | string/int | Unique transaction identifier |
FK | Player_ID** | string | Unique customer identifier |
Transaction_Date** | date | Transaction date | |
Transaction_Timestamp | timestamp | Transaction Timestamp | |
Transaction_Type** | string | Transaction type. Should hold values 'DEPOSIT', 'WITHDRAWAL', or 'BONUS' | |
Transaction_Amount** | decimal | Monetary value of the transaction | |
Platform | string | Platform from which the transaction is made (e.g. Web, Mobile, Download) | |
Status** | string | Transaction status (e.g. Approved, Rejected, Pending). Must have status ‘Approved’ for approved transactions. | |
Last_Updated | Date | Date when the record was last modified or added (Mandatory in case of DB to DB connection) |
Note:
- Any other transaction dimension available can be added if needed.
**=Always mandatory
Bingo_Games_Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | PlayerID** | string | Unique player identifier |
PK | GameDate** | date | Date of game |
BrandName | string | When multiple bingo brands exist | |
PK, FK | RoomID | string | Bingo room identifier |
Platform | string | Platform from which the Bingo game was played. Should hold values 'WEB' or 'MOBILE' | |
TotalRealWager** | decimal | Monetary real value that was wagered | |
TotalRealWin | decimal | The monetary real value that was won | |
NetGamingRevenue** | decimal | Total revenue (after bonuses deduction) from daily sessions, in case of daily aggregation | |
NumberOfRealGames | decimal | Total amount of real games played | |
NumberOfRealWins | decimal | Total amount of real games won | |
NumberOfBonusWins | decimal | Total amount of bonus games won | |
NumberOfBonusGames | decimal | Total amount of bonus games played | |
TotalBonusWin | decimal | Total bonus amount that was won | |
TotalBonusWager | decimal | Total bonus amount that was wagered |
Note:
- Any other dimension available can be added if needed.
**=Always mandatory
Bingo_Rooms_Catalog
Key | Field | Data Type | Description |
---|---|---|---|
PK | Room_ID** | string | Unique room identifier |
Room_Name | string | Name of room | |
Updated_Date | date | Date when the room was last modified or added |
Note:
- Any other dimension available can be added if needed.
**=Always mandatory
Database Schema

Updated 1 day ago