Technical Overview
Technical overview
Understand the integration before you buy.
A practical map for operators, affiliate managers, developers and security reviewers.
Event path
A traceable flow, not a black box.
Clicks, conversion events, partner context and commission rules move through an agreed boundary before reporting, review and payout.
event_type: ‘conversion’,
partner_id: ‘partner_204’,
campaign_id: ‘spring_launch’,
occurred_at: ‘2026-04-18T10:42Z’,
value: 120.00,
currency: ‘EUR’
}
Public integration vocabulary
| Field | Role in the workflow |
|---|---|
event_type |
Separates click, registration, deposit, conversion, chargeback and adjustment events. |
partner_id |
Connects activity to the affiliate or network relationship. |
campaign_id |
Preserves campaign and creative context for analysis. |
occurred_at |
Provides an unambiguous timestamp for reconciliation. |
value / currency |
Supports commission calculation and finance review. |
Connect
REST API & webhooks
Use the agreed API and event model to connect the systems that matter to your programme.
Track
Server-side & postback flows
Choose the integration pattern that fits the browser, privacy and data-quality requirements of the deployment.
Review
Evidence pack
Request current endpoint references, authentication details, retention questions and the security questionnaire.
Technical workspace views
The evidence layer is visible in the interface.
Illustrative screens show the boundary between attribution, event quality, integrations and the review queue. Figures are demonstration data.
Signals, alerts, webhooks, API and postbacks in one view.
Clicks, registrations, FTDs, EPC, GGR and NGR by segment.
Prepared for evaluation; live data depends on the operator’s tracking and reporting configuration.