Connect Your Platform to Track360
Technical guides for exposing customer, transaction, and activity data from your platform so Track360 can ingest, process, and report on your affiliate program.
How It Works
Three steps from scoping to production.
Define Scope
Determine which entities are in scope: customers, transactions, and activity data. Agree on required fields and data contract.
Choose Pattern
Select integration method: Track360 pulls data from your API, your platform pushes events to Track360, or a hybrid approach.
Test & Launch
Validate in staging, reconcile data between systems, and cut over to production with monitoring.
What You Need to Provide
A comparison of what each vertical requires.
| Entity | iGaming | Forex | Prop Trading |
|---|---|---|---|
| Customers | Registration + KYC | Registration + Account Type | Registration + Challenge Phase |
| Transactions | Deposits, Withdrawals, Bonuses | Deposits, Withdrawals, IB Rebates | Challenge Fees, Payouts, Resets |
| Activity Data | Gaming Activity (GGR/NGR) | Trading Activity (Lots/Volume) | Trading Activity (PnL/Drawdown) |
| Authentication | OAuth 2.0 / API Key | OAuth 2.0 / API Key | OAuth 2.0 / API Key |
Integration Patterns
Choose the data exchange pattern that fits your architecture.
Pull — Track360 Retrieves Your Data
Track360 periodically pulls data from your API or database
You expose a REST API (or database replica / DWH view) and Track360 retrieves data on a scheduled cadence. This is the most common pattern — it keeps control on your side and requires no outbound connectivity from your systems.
- Partners with existing internal APIs or reporting endpoints
- Stable, batch-oriented data (daily gaming activity, transaction history)
- Reconciliation and backfill workflows
- Systems behind firewalls with no public webhook endpoint
- —Real-time event delivery (sub-second latency)
- —High-frequency updates where polling creates overhead
Push — You Send Data to Track360
Your platform sends events to Track360 endpoints in real time
Your system pushes events (registrations, deposits, conversions) to Track360 ingestion endpoints as they occur. This gives the lowest latency but requires your platform to handle delivery, retries, and idempotency.
- Real-time customer registration and attribution
- Instant deposit and conversion tracking
- Event-driven architectures with message queues
- Platforms that prefer to control outbound data delivery
- —Aggregated daily data (gaming/trading activity summaries)
- —Historical data migration or backfill
Hybrid — Combine Both Patterns
Push real-time events + pull batch data for reconciliation
The recommended approach for production integrations. Push time-sensitive events (registrations, deposits) for real-time attribution, while Track360 pulls aggregated data (activity, revenue metrics) on a daily schedule. This gives you speed where it matters and reliability everywhere else.
- Production environments that need both speed and accuracy
- Different entities with different freshness requirements
- Data reconciliation between real-time and batch sources
- High-volume integrations with complex data models
- —Simple integrations with a single entity type
Quick Comparison
| Pull | Push | Hybrid | |
|---|---|---|---|
| Latency | Minutes to hours | Seconds | Seconds (events) + daily (batch) |
| Complexity | Low — expose API | Medium — handle retries | Medium — both patterns |
| Data freshness | Scheduled cadence | Real-time | Real-time + reconciled |
| Backfill support | Built-in | Requires replay | Built-in |
| Best entity fit | Activity, reports | Events, registrations | All entity types |