Prepare Your Data for Optimove- Forex
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
- Assets – Assets IDs and their associated textual names and category
- Positions – Each row describes a single position
- Transactions – Each row describes a financial transaction
Important*:* All monetary figures must be converted into a single consistent currency.
Customers
Key | Field | Data Type | Description |
---|---|---|---|
PK | Customer_ID** | string/int | Unique customer identifier |
Registration_Date** | date | Date the customer 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 | Customer’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 customer; 'Yes’ = blocked customer (e.g. fraud) | |
Is_Test | string | 'No’ = regular customer; 'Yes’ = test customer | |
Gender | string | Customer’s gender. Must hold values ‘Male’, ‘Female’, ‘Unknown’ | |
Country | string | Customer’s country | |
City | string | Customer’s city | |
Address | string | Customer’s address | |
First_Name | string | Customer’s first name | |
Last_Name | string | Customer’s last name | |
Language | string | Customer’s language | |
Balance | Decimal/int | The monetary value of a customer’s current balance | |
Brand_Name | string | When multiple brand platforms exist | |
Alias | string | User name | |
Currency | string | Customer’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 customer had registered with (e.g. Web, Android App, iOS App, etc.) | |
Last_Login_Date | date | The date of the customer’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.
*=Mandatory if required for the execution channel integration
**=Always mandatory
Assets
Key | Field | Data Type | Description |
---|---|---|---|
PK | Asset_ID** | string | Unique asset identifier |
Asset_Name | string | Asset name (e.g. USD/EUR, Gold, Apple) | |
Asset_Category | string | Asset category (e.g. Currencies, Indices, Commodities, etc.) | |
Update_At | date | Date when the record was last modified or added (including status changes) |
Note: Please include any additional information that you find helpful.
** Always Mandatory
Positions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Position_ID** | string | Unique position identifier |
Customer_ID** | string | Unique customer identifier | |
Investment_Amount** | decimal | The amount invested in the position by the customer | |
FK | Asset_ID | string | Unique asset identifier |
Position_Open_Date** | date | Position open time | |
Position_Close_Date | date | Position close time | |
Leverage | decimal | Customer Leverage. Shouldn’t be negative. | |
Customer_Profit | decimal | The amount won (Positive) amount lost (negative) | |
Net_Revenue | decimal | Customer net revenue | |
Position_Status | string | Indication of position status (e.g. Open, Closed,) | |
Platform | string | The platform used to open the position. Should hold ‘Web’, ‘Mobile’, other Forex possible platforms. |
Note: Please include any additional information that you find helpful.
** Always Mandatory
Transactions
Key | Field | Data Type | Description |
---|---|---|---|
PK | Transaction_ID** | string/int | Unique transaction identifier |
FK | Customer_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
Database Schema
Updated 3 days ago