Data Transfer Methods
Overview
Future Anthem ingests customer data using real-time event streaming. This enables low-latency personalisation, faster model learning, and real-time decisioning across the platform.
The platform supports two supported ingestion methods:
-
REST Proxy – HTTP-based event ingestion
-
Kafka Native – Direct Kafka producer integration
Both methods write to the same underlying event pipeline and support identical data models. The choice of method depends on your technical architecture, throughput requirements, and operational preferences.
This guide explains:
-
How real-time ingestion works at a high level
-
The available ingestion methods
-
Data requirements
Detailed data requirements, schemas, and FAQs are covered in our Knowledge Base.
How Real-Time Ingestion Works
At a high level, the data flow is:
-
Your platform emits player or transactional events
-
Events are sent via REST Proxy or Kafka Native
-
Events are validated and persisted in real time
-
Future Anthem products consume the data immediately
There is no difference in downstream processing once data is ingested.
Data Requirements
The data required by Future Anthem varies by product and vertical.
In particular, casino and sports products require different event types and attributes to support modelling and personalisation.
Full details are documented in the Knowledge Base including:
-
What data needs to be sent
-
Required vs optional fields
-
Casino vs sports data requirements
→ View data requirements in the Knowledge Base
Environments and Access
Both REST Proxy and Kafka Native are available per environment, typically:
-
Staging
-
Production
Each environment has:
-
Separate credentials
-
Separate topics
-
Isolated data processing
Environment setup and access details are provided during onboarding.
