Prepare Your Data for Optimove- Poker
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
- Poker_Game_Details – Each row describes one poker game details
- Poker_Game_Sessions – Each row describes one poker game session
- Transactions – Each row describes one financial transaction
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 from 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
Poker_Game_Details
Key | Field | Data Type | Description |
---|---|---|---|
PK | Game_ID** | string | Unique game identifier |
Game_Type | string | Game type (e.g. Cash, Tournament, SitnGo, Ring) | |
Sub_Game_Type | string | E.g. Omaha, Hold’em, etc. | |
Game_Name | string | Name of game | |
Number_of_Players | int | How many possible seats in the game | |
Jackpot_Prize | decimal | Tournament prize | |
Jackpot_Name | string | Name of the jackpot prize | |
Tournament_Buy_In_Cost | decimal | Minimum buy-in for entering the game |
Notes:
**=Always mandatory
Poker_Game_Session
Key | Field | Data Type | Description |
---|---|---|---|
PK | Session_ID** | string | Unique session identifier |
FK | Player_ID** | string | Unique player identifier |
Session_Platform | string | Platform which the session was made from. Should hold values ‘WEB’ or ‘MOBILE’ | |
FK | Game_ID | string | Unique game identifier |
Session_Start_Date** | date | Session start date | |
Session_End_Date | date | Session end date | |
Session_Type | string | Name of the type of session | |
Session_Duration_Minutes | int | Session duration in minutes | |
Total_Buy_Ins | decimal | Total buy-ins the player wagered in the game | |
Total_Payout | decimal | The monetary value that was won | |
Total_Rake | decimal | Total rake for the company | |
Currency | string | Type of currency | |
Net_Revenue** | decimal | Actual revenue from the session | |
Last_Updated_Date | date | Date when the record was last modified or added (Mandatory in case of DB to DB connection) |
Notes:
**=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 'DEPOSIT', 'WITHDRAWAL', or 'BONUS' | |
Transaction_Amount** | decimal | Monetary value of the transaction | |
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:
- Any other gaming dimension available can be added if needed.
**=Always mandatory
Database Schema
Updated 3 days ago