Trading

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 as 4.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.

1. Customers – Each row describes the attributes of a single customer
2. Assets – Assets IDs and their associated textual names and category
3. Trade – Each row describes trading activity made by the customer
4. Positions – Each row describes a single position
5. Transactions – Each row describes a financial transaction

Customers

Notes:

• IsOptinEmailTimeStamp* - In case Optimove will manage the “unsubscribe” for the Opti-Mail integration please include 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

Note:

• **=Always mandatory

Positions

Note:

• **=Always mandatory

Trade

Note:

• **=Always mandatory

Transactions

Note:

• Any other transaction dimension available can be added if needed.
• **=Always mandatory

Database Schema

Batch-Data Process

Once Optimove successfully receives all historical data, a batch-data update process is required to ensure that Optimove’s data warehouse is updated every day, with the latest available data.

This data extraction process is similar to the method used for the initial historical data delivery, but will include only incremental (new/changed) data.

For additional details about the batch-data process, see Batch data process.

Ensuring Data Integrity

The following points will help ensure the integrity of the data you provide to Optimove:

1. The primary keys (unique identifiers) that were initially defined for each table must remain present and consistent in files delivered daily, without Null values. Please avoid duplications on the primary key level.
2. When providing historical data, ensure that data for the entire date range is provided. If this is not possible, inform Optimove in advance of any dates missing from the date ranges provided in each table.
3. It is important that all identifiers in all transactional tables exist in the relevant DIM table. For example, all game IDs in the Games table must appear in the Game Types and Categories table, or all product IDs in the Orders table must appear in the Catalog table.
4. It is important that all customer IDs that appear in the transactional and fact tables also appear in the Customers table. Only customer IDs appearing in the Customers table will be included in Optimove.
5. Every change made to the data schema must be brought to Optimove’s attention in advance. Uncoordinated schema changes will cause the batch-data process to fail.
6. Do not include any retroactive data (older than initially agreed upon) in the batch-data tables. If you feel it is necessary to do so, coordinate with Optimove in advance.
7. Do not use any default dates such as ‘1900-01-01,’ instead please use Null (blank in files) as default.

For further explanation see Data QA Processes.

Questions?

We are here to help! Please contact us with any questions, and we will be happy to assist you. Email us at [email protected] or call us (seven days a week from 5:00 am to 8:00 pm GMT) at +972-3-672-4546.