Sweepstakes Casino
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.
Required Data Tables
The following data tables describe the content, format, and labels of the required data.
- Customers – each row describes a player
- Transactions – each row describes a financial transaction
- Games – Each row describes a daily aggregation of a specific game played, player, and platform
- Game_Types_and_Categories – Game IDs and their associated types and categories
Customers
Key | Field | Data Type | Description |
---|---|---|---|
PK | Player_ID** | string/int | Unique player 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 | |
GC_Balance | Decimal/int | The value of a player’s current gold coins balance in gold coins currency | |
SC_Balance | Decimal/int | The monetary value of a player’s current sweep coins balance | |
Casino_Name | string | When multiple casino platforms exist | |
Alias | string | User name | |
Currency | string | Player’s fiat 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 approva |
Note:
- Please include any additional information that you find helpful
- IsOptinEmailTimeStamp* - In case Optimove will manage the “unsubscribe” for the Opti-Mail integration please include additional column to describe when the customer opt 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
Games
Key | Field | Data Type | Description |
---|---|---|---|
PK | Game_Date** | Date | Date of the game |
PK | Player_ID** | string | Unique player identifier |
PK | Game_ID** | string | Game type identifier |
PK | Platform | string | Should hold values 'web' or 'mobile' |
Sweep_Coins_Bet_Amount** | decimal | Monetary real value that was wagered according to sweep coin conversion | |
Sweep_Coins_Win_Amount | decimal | Monetary real value that was won according to sweep coin conversion | |
Gold_Coins_Bet_Amount | decimal | Total GC amount that was wagered | |
Gold_Coins_Win_Amount | decimal | Total GC amount that was won | |
Net_Gaming_Revenue** | decimal | Total revenue (after bonuses deduction) from daily sessions, in case of daily aggregation | |
Number_of_Sweep_Coins_Bets | int | Total amount of sweep coin bets played | |
Number_of_Gold_Coins_Bets | int | Total amount of gold coin bets played | |
Number_of_Sessions | int | Total number of sessions played | |
Number_of_Sweep_Coins_Wins | int | Total amount of sweep coin bets won | |
Number_of_Gold_Coins_Wins | int | Total amount of gold coin bets won |
Notes:
- Any other gaming dimension available can be added if needed.
- Attach a description of your Net-Gaming revenue calculation methodology
- If the platform field is not available, keep the first 3 fields as PK
**=Always mandatory
Game_Types_and_Categories
Key | Field | Data Type | Description |
---|---|---|---|
PK, FK | Game_ID** | string/int | Game unique identifier |
Game_Name | string | Game name (e.g. Blackjack, Silver Dollar) | |
Game_Category | string | Division of games into major categories (e.g. Slots, Roulette, Table, etc.) | |
Update_At | date | Date when the record was last modified or added |
Note:
- Any other gaming dimension available can be added if needed, as our proposition is relatively lean.
**=Always mandatory
Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Transaction_ID** | string/int | Unique transaction identifier |
Player_ID** | string | Unique player identifier | |
Transaction_Date** | date | Transaction date | |
Transaction_Timestamp | timestamp | Transaction Timestamp | |
Transaction_Type** | string | Transaction type. Should hold values 'PURCHASE', 'REDEEM', 'BONUS_GC', or ‘BONUS_SC’ | |
Transaction_Amount | decimal | Monetary value of the transaction after conversion | |
Platform | string | Platform from which the transaction 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:
**=Always mandatory
Database Schema

Updated about 13 hours ago