Data Flow and System Model

This page explains how data moves through CasinoFlux.

You do not need to understand this to get started.
You do need it to trust your numbers.

Canonical Data Flow (Conceptual)

At a high level, CasinoFlux processes data in two parallel layers:

A real-time event layer handling user interaction and conversions
A delayed revenue layer handling monetary truth from casino operators

These layers are merged at the reporting level to provide a complete performance view.

Real-Time Layer

The real-time layer handles immediate user interaction and conversion signals.

This layer is powered by postback tracking. Without postback enabled, only Site Analytics data is available in real time.

This includes:

Clicks
Registrations
Deposits (when supported by the casino affiliate platform)
Site Analytics (on-page behavior, traffic, engagement)

Real-time data is used for:

Campaign monitoring
Traffic source optimization
Early performance validation

This data is accurate in event timing, not in final revenue value.

Delayed Revenue Layer

Delayed data includes:

Revenue
Rev-share
NGR
Lifetime metrics (when available)

This data is:

Pulled via API
Normalized across casino affiliate platforms
Merged into existing campaigns and sites

Delays of approximately 24 hours are normal.

This delayed data is surfaced in the Site Overview and Site Report pages. These are the primary reporting views for affiliate revenue data.

The reporting page found under Postbacks is not delayed — it reflects real-time conversion events. Site Analytics is also real-time, not delayed.

How CasinoFlux Merges These Layers

CasinoFlux combines:

Fast conversion signals from the real-time layer
Slower but authoritative revenue data from the delayed layer

This enables:

Early decision-making without premature conclusions
Accurate profitability analysis over time
Reduced false negatives on campaigns that monetize later

CasinoFlux does not attempt to force revenue into real time when the data source does not support it.

Why Discrepancies Happen

You may see differences between:

Casino affiliate platforms
CasinoFlux
Traffic source dashboards

Common causes include:

Timezone differences
Data delays on the operator side
Event eligibility or qualification rules
API update frequency

CasinoFlux prioritizes consistency and traceability over illusionary real-time accuracy.

Advanced: Why CasinoFlux Is Designed This Way

Most tracking tools optimize for speed.

CasinoFlux optimizes for truth over time.

In iGaming, assuming revenue is real-time leads to:

Incorrect bid optimization
Premature campaign shutdowns
Misjudging long-term value of traffic

CasinoFlux intentionally separates:

Signal (what is happening now)
Outcome (what the traffic is worth over time)

This separation is critical for sustainable scaling.

Data Flow