S2S postbacks: how to set them up between advertiser, network and partner
How a conversion travels from the advertiser to your partner, which macros to use and how to test everything before launch.
What an S2S postback is
A postback is a request one server sends to another when an event happens: a sign-up, a deposit, a sale. Unlike a pixel, it does not depend on the user's browser, so ad blockers and cookie limits do not lose it.
How a conversion travels
- 1A partner sends a click to your tracking link, and PrimeTrack creates a click_id.
- 2The click_id goes to the advertiser inside the offer link.
- 3When the player deposits, the advertiser sends a postback to PrimeTrack with that click_id.
- 4PrimeTrack records the conversion and sends a postback on to the partner.
Advertiser postback
Give the advertiser a URL like this one. Their system replaces the macros in curly braces with real values:
https://track.your-network.com/api/postback?click_id={click_id}&status={status}&payout={payout}PrimeTrack also accepts the click ID under the names other trackers use, such as clickid, subid or sub1, so Keitaro, Binom and Voluum setups work without rewriting.
Partner postback
The partner adds their URL in the dashboard and chooses which events to receive. For example:
https://partner-tracker.com/pb?clickid={sub1}&sum={payout}&status={status}&geo={geo}Common mistakes
| Mistake | What happens | Fix |
|---|---|---|
| click_id is not passed to the advertiser | Conversions cannot find the click | Add {click_id} to the offer link |
| The partner's server does not return 200 | The partner does not see the conversion | Check the delivery log and retries |
| Duplicate postbacks | Double payouts | Deduplicate by transaction_id |