Reporting and analytics

Trace programme performance back to durable source events.

Inspect attribution, conversion and commission activity through operational views backed by retained event identities and exportable evidence.

01ReferralLink or code
02ConversionStable event
03CommissionRule evidence
Event-backed metricsEnvironment filtersRetained history

Built for operating reality

Clear contracts at every boundary.

01

Measure from canonical events

Metrics are derived from accepted conversion and commission events rather than browser-only counters.

02

Keep environments separate

Sandbox activity can be explored without contaminating production programme reporting.

03

Investigate the underlying record

Operational summaries connect back to stable conversion, commission and affiliate identities for review.

Operational reporting

Answer what happened before asking why a chart moved.

Stable source identities let operators move from an aggregate change to the conversions and commission decisions underneath it.

Analytics boundary

Export retained events without putting reporting on the write path.

Incremental data exports support analytical workloads separately from the transactional path that records attribution and money state.

Questions, answered

Know where the boundaries are before you integrate.

Does sandbox activity appear as live performance?

No. Environment scope remains part of the reporting contract so test and production activity can be separated.

Can a reported conversion be traced?

Operational records retain stable identities that connect conversion, attribution and commission decisions.

How are analytical workloads isolated?

Incremental exports feed the analytics layer so large reporting queries do not become part of the transactional money path.

Build the reliable path

Make every referral decision traceable from click to payout.

Request sandbox access