Social Gaming
Required Data Tables
The following data tables describe the content, format, and labels of the required data.
- Customers – Each row describes a player
- Games_Transactions – Daily aggregation for game activity for all players
- Payments_Transactions – Lists all payment transactions that affect a customer's account balance
- Promotions_Collected – Daily aggregation of all promotions players were given
- Promotion_Catalog – Contains a record of all promotion types
Important*:* All monetary figures must be converted into a single consistent currency.
Customers
Key | Field | Data Type | Description |
---|---|---|---|
PK | Player_ID** | string/int | Unique player identifier |
Registration_Date** | date | Date the player registered | |
Email* | string | 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, to allow perfect sync with the daily batch.
*=Mandatory if required for the execution channel integration
**=Always mandatory
Games_Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Player_ID** | string | Unique player identifier |
PK | Game_Date** | date | Date of the game |
PK | Game_ID** | string | Game type identifier |
PK | Platform** | string | Should hold values 'web' , 'mobile', etc. |
Number_of_Games | int | Number of games | |
Total_Bet_Amount | decimal | Total bet amount | |
Number_of_Winning_Games | int | Number of winning games | |
Total_Win_Amount | decimal | Total win amount | |
XP_Points_Collected | int | XP Points Collected | |
Total_Session_Duration | int | Total session duration |
Notes:
- Please include different game metrics based on your game type
**=Always mandatory
Payments_Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Payment_ID** | string | Unique payment identifier |
FK | Player_ID** | string | Unique player identifier |
Payment_Date** | date | Date of payment | |
Platform | string | The platform which the transaction is made from. Should hold values 'web' , 'mobile', etc. | |
FK | Item_ID | string | Unique item identifier |
Payment_Amount** | decimal | The monetary value of the payment | |
Coins_Amount | int | The coin amount that the customer received for the purchase |
Notes:
**=Always mandatory
Promotions_Collected
Key | Field | Data Type | Description |
---|---|---|---|
PK, FK | Promotion_ID** | string | Unique promotion identifier |
PK, FK | Player_ID** | string | Unique player identifier |
PK | Promotion_Date | date | Date of payment |
Number_of_Promotions | int | Number of promotions collected | |
Total_Promotion_Amount | decimal | Coins value of promotions collected |
Note:
**=Always mandatory
Promotion_Catalog
Key | Field | Data Type | Description |
---|---|---|---|
PK | Promotion_ID** | string | Unique promotion identifier |
Promotion_Type | string | Promotion type name | |
Promotion_Category | date | Promotion category name (e.g. Hourly promo, Friend invite promo, etc.) | |
Updated_At | date | Date when the record was last modified or added |
Notes:
**=Always mandatory
Database Schema

Updated 2 days ago