Postback setup checklist for iGaming affiliate teams

Start with the event map

Write down the events you expect before touching the tracker UI. Most teams need at least register and deposit; some also track first_wager and wager. Keep the event names stable across the operator portal, tracker, and BetLink. If one system calls an event ftd and another expects deposit, map that difference before traffic starts.

The event map should also say which events affect commercial decisions. A registration may help quality review, while a deposit often affects CPA, RevShare forecasting, and payout follow-up.

Confirm the click identifier

The click ID is the thread that ties the journey together. Confirm where it is created, which URL parameter carries it, and how the operator returns it in the postback. Do not start a campaign until you can follow one test click from link creation to postback receipt.

Useful checks:

• the click ID survives redirects and landing pages,
• the operator stores the same value it receives,
• the postback sends the value in the agreed field,
• the receiving system can find the original click.

Validate one payload before launch

Use a realistic sample, not a toy value. Include the source, event type, click ID, transaction ID, currency, amount, and timestamp when available. Then open the postback payload checker and confirm the shape is valid before anyone sends live traffic.

The validation step does not replace an end-to-end test. It catches simple format problems early so the live test can focus on routing and evidence.

Keep a launch note

When the test succeeds, save the event name, endpoint, sample payload, test click ID, and the date of the check. If a payout number later differs between systems, this launch note gives the team a starting point for reconciliation.