Company logoHelp Center
Visit aretonet.com

Manual Data Upload

4 min. readlast update: 03.12.2025

Manual data upload allows users to import historical or recent data into the system via CSV files. This method is recommended for:

  • Historical data imports
  • Situations where alternative methods of integration is not possible

Key Considerations

  • File Format: Ensure CSV files are saved in Unicode encoding to preserve accents and non-standard Latin characters.
  • File Size Limit: Maximum 100MB per file.
  • Data Overwriting: If a record with the same Player ID exists, it will be automatically overwritten.
  • Data Mapping:
    • Without data mapping: CSV files should not include headers.
    • With data mapping: Headers must be present.
  • Facts Data: Facts refer to transactional data (e.g., wagers, deposits, free spins).
  • Error Handling: If required fields are missing or there are invalid columns, the system will reject the file, and an error message will appear under Notifications.
  • Duplicate Facts: If a fact is uploaded twice, both instances will be stored.

 

Uploading Data: Step-by-Step Guide

Step 1: Prepare Your CSV File

Users can either:

  • Use the default CSV format required by the CRM (detailed in sections below).
  • Define custom CSV formats using Data Mapping.

Step 2: Upload Customer Data

  1. Navigate to Customer Upload and upload the CSV file.
  2. If using Data Mapping, upload the source CSV file in the Data Mapping section before proceeding. This step is required once per file type and only needs updating if the CSV format changes.

Step 3: Upload the Data File

  1. In the Upload section, select the CSV file by clicking Browse.
  2. Once selected, the Upload option will appear. Click to begin the upload process.

Step 4: Processing & Notifications

  • Processing time depends on file size and typically takes a few seconds to a few minutes.
  • Upload status and error notifications appear in the Notifications panel (top-right of the screen).
  • Users can continue working while the file is being processed. Multiple files can be uploaded simultaneously.

Step 5: Upload Facts & Transactional Data

  • Once customer data is successfully uploaded, proceed with Facts Upload (transactional data).

 

Data Policy

Refer to the Data Policy section before proceeding with data uploads.

 

Uploading Historical Data

For historical data uploads prior to system launch, it is recommended to include at least six months of historical transactional data. This data is used to:

  • Train necessary models
  • Define lifecycle stages
  • Segment customers
  • Generate analytics and clustering insights

 

Customer Data Upload

Required Parameters

Parameter Type Description Max Length Mandatory
Player ID string Unique customer identifier 40 ✓
Name string Customer's first name 50 x
Surname string Customer's last name 50 x
Zip Code string Customer's postal code 25 x
State string Customer's state 40 x
Gender string M (Male) / F (Female) 1 x
City string Customer's city 50 x
Country Code string 2-letter ISO country code 2 ✓
Email Address string Customer's email address 100 ✓
Date of Birth date Format: YYYY-MM-DD - x
Mobile Number string Include country code (e.g., 0044123456789) 50 x
Signup Date datetime Format: YYYY-MM-DD HH:mm:ss - ✓
Language Code string 2-letter ISO language code 2 x
Timezone integer Minutes offset from GMT - x
Account Balance decimal Positive numeric value 12 x
Account Currency string 3-letter ISO currency code 3 x
Custom Fields

string/

integer

 Optional custom attributes 40 x
Opt-out Flags boolean Opt-out from email, SMS, push notifications - x

 

 

CSV Format Example

CSV Structure:

 {Player ID},{Name},{Surname},{Zip Code},{State},{Gender},{City},{Country Code},
{Email Address},{Date of Birth},{Mobile Number},{Signup Date},{Language Code},
{Timezone},{Account Balance},{Account Currency},{Custom Int 1},{Custom Int 2},
{Custom Int 3},{Custom Int 4},Custom String 1},{Custom String 2},{Custom String 3},
{Custom String 4},{Btag},{Opt-out Email},{Opt-out SMS},{Opt-out Push},{Opt-out Mobile Push}
 

CSV Example:

918281820,Jack,Brown,W1S 1DW,,M,London,GB,j.b@areto4bet.com,1976-12-24,0044000000000,2017-12-05 11:56:31,EN,0,250.00,GBP,540,0,,1,vip,,,,SOURCE_1,true,false,true,false

918281821,James,White,,AL,F,,US,j.w@areto4bet.com,,,2017-12-21 10:00:00,,,10.50,EUR,,,,,,,,,SOURCE_1,true,false,false,true

 

 

 

Facts Upload

Facts represent transactional data such as bonuses, free spins, wagers, deposits, withdrawals, and payouts.

Example Categories of Facts Data:

  • Bonus Facts (e.g., deposit bonuses)
  • Free Spins Facts (e.g., promotional spins)
  • Game Session Facts (e.g., session tracking)
  • Casino Wager Facts (e.g., bet amounts)
  • Sports Wager Facts (e.g., bet placements)
  • Lottery Wager Facts (e.g., ticket purchases)
  • Deposit & Withdrawal Facts (e.g., cashier transactions)

 

General Transaction CSV Format Example

{Player ID},{Currency},{Amount},{Transaction Date},{Additional Fields}

 

Data Mapping

To simplify CSV uploads, users can define data maps, which match source file columns to the expected format.

Steps to Configure Data Mapping

  1. Upload the source CSV file with headers (unaltered).
  2. Map source columns to the expected fields.
  3. Save the data map.
  4. Future CSV uploads will automatically align based on the saved mapping.

Data Mapping Considerations

  • Ensure the CSV file is saved in Unicode encoding to retain special characters.
  • If the CSV format changes, the data mapping must be updated.
  • If data mapping is disabled, remove the specific mapping configuration.

 

By following these guidelines, users can efficiently upload, process, and manage customer and transactional data within the CRM.

Was this article helpful?