Retries and delivery logs
Outgoing affiliate postbacks include delivery status and attempts. The documented workflow supports automatic retries and manual retry of a failed delivery.
EVENTS & INTEGRATIONS
Connect the data.
Keep the context.
Bring partner events into the programme and send eligible updates to an affiliate’s own tracker. Mapping and identifiers make the difference.
EVENT REVIEWINTERACTIVE EXAMPLE
No simulated events yet.
Source status is APPROVED in this example. No network request is made. Replay uses the same example event ID.
THE DETAILS
Two directions. One attributed journey.
INCOMING
Partner → programme
Map the partner’s macros into the internal click ID, player ID, stable conversion or transaction ID, event and currency. Amount and payout represent different things.
Each partner can use different names and qualification rules. Verify them before enabling traffic.
OUTGOING
Programme → affiliate tracker
Affiliates configure their own eligible destinations and events. Their external click ID is returned along with permitted conversion information and their own payout.
Pending conversions are not sent. Corrections update a conversion rather than representing a new acquisition.
THE DETAILS
Diagnose the missing conversion.
- Check the original click
Confirm that the correct promotion link was used and the partner received the intended click identifier.
- Inspect the partner’s delivery
Ask for the expanded callback URL, event time, transaction ID and HTTP result. A dashboard count alone does not prove delivery.
- Check mapping and review state
A received event can still be pending, unattributed or excluded by a cap or another eligibility rule.
- Reconcile without duplicating
Use stable IDs and preserve event dates. Historical imports require supported formats, explicit amounts and an authorised review.
THE DETAILS
Operational details that matter.
Stable event IDs
Deduplicate by delivery identifier at the receiving tracker. A correction has a new delivery but refers to the same conversion.
Only the right information
Affiliate payout refers to the affiliate’s own commission. A deposit amount is available only if the partner supplied it.
GOOD QUESTIONS
A little more clarity.
Do postbacks work in the current Hub preview?
No. Live incoming callbacks, tracking redirects and outgoing deliveries are intentionally disabled in the current preview. These pages explain the product workflows and use local simulations.
Can every casino provide NGR and individual deposits?
No. Available events, macros, frequency and transaction identifiers depend on the partner. Confirm the specification rather than assuming a registration or FTD callback includes everything.
Does changing a rule send the whole history?
Outgoing affiliate postbacks do not automatically backfill historical conversions. Configuration changes affect the supported future events and updates.
YOUR NEXT CHAPTER