Recruiting affiliates is only half the job. The other half is proving which of the affiliates you recruited actually bring players who deposit. Most operators already have the data in their affiliate platform, but it sits there, disconnected from the recruitment work. Postbacks are the simplest way to connect the two.
What is a postback?
A postback, also called S2S (server-to-server) tracking, is a message one system sends to another when something happens. In iGaming, the affiliate platform sends a postback when a player tracked to an affiliate:
- registers,
- makes a first deposit (FTD),
- deposits again,
- or generates revenue.
Technically, a postback is just a web address that the platform calls with the details filled in, for example:
https://example.com/postback?event=ftd&aff=12345&amount=50¤cy=EUR&txid=98765The parts in that address are placeholders the platform replaces with real values: the affiliate’s ID, the deposit amount, a unique transaction ID and so on. Each platform has its own names for these placeholders (often called tokens or macros), but the idea is the same everywhere.
Why postbacks beat spreadsheets
Most teams start with monthly CSV exports: download the affiliate report, paste it into a spreadsheet, match the rows to your list of recruited affiliates. It works, but:
- data is weeks old by the time anyone looks at it,
- matching affiliates by name is error-prone,
- nobody does it consistently once the team is busy.
Postbacks arrive within seconds of the event and carry the platform’s affiliate ID, so matching is exact.
How the main platforms handle postbacks
Cellxpert, Income Access, MyAffiliates and NetRefer all support outgoing postbacks or pixels, though the menu names and placeholder names differ. Two practical points apply to all of them:
- Global vs per-affiliate postbacks. Affiliates usually set postbacks for their own traffic. As an operator you want one postback for all affiliates. On some platforms you can set this yourself; on others your platform account manager has to enable an operator-level (global) postback.
- One postback per event. Set separate postbacks for registrations, first deposits and, if you want them, deposits and revenue, so each event type is clearly labelled.
If postbacks are not available on your plan, every platform can export affiliate and performance reports as CSV, which is a reliable fallback for historical data.
Privacy: send amounts, not people
Postbacks should carry the affiliate ID, the event type, amounts, currency and country. They should never carry player names or email addresses. If the platform sends a player ID, the receiving system should only use it (ideally hashed) to avoid counting the same first deposit twice.
Measuring the ROI of affiliate recruitment
Once postbacks flow, you can answer the questions that matter:
- Which affiliates recruited this quarter have sent a first deposit?
- What is the net revenue per recruited affiliate after three months?
- Which markets and channels produce the best recruits?
That last question feeds back into recruitment: if Portuguese-language Telegram tipsters produce twice the FTDs of English review sites, that is where next month’s outreach should go.
Setting it up in AffiliateIQ
AffiliateIQ gives each workspace a secret postback address, with ready-made versions for registrations, first deposits, deposits and revenue. You paste it into Cellxpert, Income Access, MyAffiliates, NetRefer or any platform that supports postbacks, add each affiliate’s platform ID once (or import your affiliate list), and results appear per affiliate and in your performance reports. Events for an ID you have not linked yet are kept until you link it, so nothing is lost. Historical results come in through CSV import, with columns matched automatically.
Connect your affiliate platform on a paid AffiliateIQ plan, or start with a free account.
Share via:


