Data Integration Guide - Getting Started

Overview

This guide will clarify the data requirements and integration options for a seamless, efficient setup with Amplifier AI, answering common FAQs to streamline onboarding.

To take full advantage of the Anthem product suite Real Time data is best, however most aspects of the product also work well with batch data.

 

Integration with Amplifier AI in 3 simple steps

Future Anthem will guide you through three steps to unlock the power of Amplifier AI

Step 1: Data Sample

• Review data requirements
  • Casino
    

• • Sports
  • Bingo
• Provide data sample (e.g. 1 hour or 1k records)
• Anthem platform will validate sample against requirements, raise any questions or missing items

 

Step 2: Data Connection

• Select integration pattern
  • Real Time 
  • Batch
• Create connection stream or regular uploads
• Once data flowing, Anthem platform will create a data validation report, summarising kpi’s on data received
• You will validate this report against your internal data, or identify any anomalies

 

Step 3: Product Deployment

• Models will be trained and product deployed for testing, then production
• There are a number of deployment integration patterns for each product, linked below:
  • Content Personalisation
  • Real time Experiences
  • Dynamic Audiences 

 

Data Requirements

Casino Data

Future Anthem’s flexible data structure ensures seamless integration for casino data. Essential and desirable data requirements are as follows:

1. Anonymised Transactional Data (Essential) – Ideally real-time spin level activity from your gaming platform, otherwise batch data from your cloud storage or data warehouse 
2. Game Metadata  
   1. Essential – Mapping of game id’s to game and supplier names 
   2. Desirable – Additional metadata held on games, whether from suppliers or internally created
3. Player Attributes (Desirable, not essential)  
   Contextual, non-personal data to enhance personalisation logic. No personal data is required. Only unique player identifiers are used to maintain privacy. 

 

Anonymised Transactional Data

Granular, event-level data is the foundation of casino integration. Each gameplay event must include:

Field	Type	Description	Example
player_id	integer	Unique ID for the player/account	47
player_site_code	string	Brand/site identifier	PrizePalace
game_id	integer	Unique ID for the game	6999
game_name	string	Game name per gaming platform	Eye of Horus
game_provider	string	Game vendor	Blueprint Gaming
transaction_id	string	Unique bet/spin ID to link stake with payout	63675868846
event_time	datetime	Timestamp of the spin/bet	2025-07-12T14:03:55Z
stake	number	Amount wagered	19.56
payout	number	Amount returned (zero if a loss)	507.55
balance_type	string	Free spin, promo, or real money	Promo Spin
currency	string	ISO code	USD

N.B: game_name and game_provider can be provided separately, and will be mapped in our platform.

 

Recommended enrichment fields

Field	Type	Description	Example
platform	string	Device used	MOBILE
balance	number	Post-spin balance	2478.33
jackpot_payout	integer	Jackpot amount	507
site_area	string	Area of app/site where spin occurred	Games
Anthem_Bonus	Integer	Identify that a spin used an Anthem issued bonus	1

 

Game Metadata

Metadata allows Future Anthem to categorise games and model performance:

Field	Type	Description	Example
game_id	integer	Unique ID for the game	6999
game_name	string	Game name per gaming platform	Eye of Horus
game_provider	string	Game vendor	Blueprint Gaming
game_type	string	Type of Game Like Table or Slot	Slot

 

Recommended enrichment fields:

Field	Type	Description	Example
release_date	date	Launch date	2017-11-02
rtp	number	Return-to-Player %	96.50
volatility	string	Win dispersion	High
theme	string	Game category	Adventure
reels	integer	Spinning reels	5
paylines	integer	Active paylines	40
layout	string	Reel layout (e.g. 5x3)	5x3
jackpot_type	string	Type of jackpot	Progressive
other		Any other metadata held

 

Player Metadata

Optional enrichment fields that enhance personalisation:

Field	Type	Description	Example
country	string	Jurisdiction/locale	Italy
registration_date	date	Player join date	2021-03-15
acquisition_channel	string	Marketing source	Affiliates
first_play_date	date	First gameplay date	2021-03-16
first_game_played	string	Initial game title	Book of Gold

 

 

Sports Data

Amplifier AI’s flexible data structure ensures seamless integration for sports betting data. Data requirements are outlined below:

1. Anonymised transactional data – ideally a stream of betslip events from you sports platform, otherwise similar batch data from your cloud storage or data warehouse
2. Bet Metadata - detailed information on markets and outcomes, used to understand transactional data
3. Player Metadata (Desirable, not essential) - Contextual, non-personal data to enhance personalisation logic. No personal data is required.

 

Transactional Data

Granular, event-level data is the foundation of sports integration.

Mandatory fields (per bet event):

Field	Type	Description	Example
player_id	integer	Unique ID for the player/account	981
bet_id	string	Unique bet identifier	B12345678
bet_placement_time	datetime	When the bet was placed	2025-07-12T14:03:55Z
bet_settlement_time	datetime	When the bet was settled	2025-07-12T16:42:12Z
bet_type	string	Market type (e.g., pre-match, in-play, accumulator)	Pre-match
sport_id	integer	Unique ID for the sport	1001
sport_name	string	Name of the sport	Football
bet_amount	number	Stake amount	50.00
currency	string	ISO code	GBP
odds	number	Decimal odds offered	2.75
outcome	string	Result of the bet (Win/Loss/Pending)	Win
event_id	integer	Unique ID of the sports event	77701
competition	string	Competition or league	Premier League
market	string	Specific bet market	Both Teams to Score
channel	string	Acquisition channel or source	Affiliates
platform	string	Device used	MOBILE

 

Bet Metadata

Metadata allows Amplifier AI to categorise bets and markets, improving recommendation models. Each bet_id should include:

Field	Type	Description	Example
market_name	string	Market description	Match Result
selection	string	Selected outcome	Team A
odds_format	string	Format of odds provided	Decimal
event_start_time	datetime	Scheduled start of the event	2025-07-12T15:00:00Z
event_location	string	Location of the event	Old Trafford

 

Player Metadata

Optional enrichment fields that enhance personalisation:

Field	Type	Description	Example
country	string	Jurisdiction/locale	Spain
registration_date	date	Player join date	2021-04-22
acquisition_channel	string	Marketing source	Direct
first_bet_date	date	First betting activity	2021-04-23
favourite_sport	string	Sport most frequently bet on	Football

Bingo Data

Future Anthem’s flexible data structure ensures seamless integration for bingo data. Essential and desirable data requirements are as follows:

1. Anonymised Transactional Data  (Essential)
   1. Essential – Ideally real-time bingo draw level activity from your gaming platform, otherwise batch data from your cloud storage or data warehouse
   2. Desirable – Additional data helps improve the model including platform, balance and free ticket values
2. Game Metadata  (Essential)
   Mapping of game id’s to game and game types
   
   
3. Player Attributes (Desirable, not essential)  
   Contextual, non-personal data to enhance personalisation logic. No personal data is required. Only unique player identifiers are used to maintain privacy. 

 

Anonymised Transactional Data

Granular, event-level data is the foundation of bingo integration. Each bingo draw event must include:

 

Recommended enrichment fields:

 

Game Metadata

Metadata allows Future Anthem to categorise games and model performance:

 

Player Metadata

Optional enrichment fields that enhance personalisation:

 

Sending data to Future Anthem

Real Time data connection

A rest API is provided where you can stream your events.

• Sending Events via REST API 
• Real Time Push Ingestion Client 

 

Batch data connection

Sending files via SFTP: 

All you need to connect to our SFTP server is  

• A SSH key pair file (usually named id_rsa or similar). You only need to share the public key with the Anthem team 

• The SFTP server address/host (e.g., sftp.casinomagic.future-anthem-lz-pr.com) which we will share 

• Your SFTP username which we will share 

 

How do I get support or make a feature suggestion?

Visit our 'here to help' form and we will respond accordingly.