Postbacks
Configure a postback URL per event under Postbacks in the portal. When a matching conversion happens on your traffic, we make a server-side HTTP GET to your URL with the macros expanded. Deliveries are logged (status code, success/failure) so you can debug.
Events
| Event | Fires when |
|---|---|
REGISTRATION | A new player registers on your domain. |
DEPOSIT | A player's deposit is approved. |
Macros
Any of these tokens in your URL are replaced at delivery time:
| Macro | Value |
|---|---|
{clickid} | Your click/sub id captured at landing (empty if organic). |
{event} | registration | deposit |
{amount} | Deposit amount (deposit events). |
{currency} | Deposit currency. |
{txid} | Deposit transaction id. |
{userid} | Our internal lead id. |
{domain} | The domain host the player registered on. |
{geo} | Player country (ISO-3166 alpha-2). |
{promo} | The campaign code the player registered with. |
Example
Postback template (configured in portal)
https://track.youraffiliate.com/postback?cid={clickid}&type={event}&payout={amount}&cur={currency}&txid={txid}
What we call on an approved deposit
GET https://track.youraffiliate.com/postback?cid=abc123&type=deposit&payout=50&cur=USDT&txid=dep_9f2c
Delivery semantics
- Delivery is
GET, retried with backoff on failure; a2xxresponse marks it delivered. - All macro values are URL-encoded by us — never pre-encode them in the template.
- Your endpoint must be on a public host — private/internal addresses are rejected.
- Postbacks are fire-and-retry best-effort and never block the player flow. For reconciliation or backfill, pull the same events from
GET /v1/conversions.
tip
Only need a real-time signal for CAPI? Postbacks deliver {clickid} + value + currency — enough to fire a server-side conversion from your own backend, where you already hold the visitor's fbp/fbc.