How postbacks work
A practical explanation of incoming postbacks, click id matching, revenue handling, and conversion attribution in Axalot.
Simple model
Postbacks close the loop between a click and a later conversion.
Click -> Campaign -> Stream -> Offer Link -> Partner
Partner -> Postback -> Axalot -> Reports / PixelsSetup checklist
Configure Affiliate Network incoming postback mapping: click id, status, revenue, currency, and external id.
Add {click_id} to the Offer Link URL using the partner's real query key.
Configure outgoing Postbacks only if Axalot must forward matched events to HTTP GET, Telegram, or pixels.
Send a test click and trigger a test conversion.
Check postback logs and reports.
Data carried by a postback
| Value | Why it matters |
|---|---|
| Click id | Matches the conversion to the original click. |
| Status | Determines accept, hold, redep, decline, or trash behavior. |
| Revenue | Used when the offer takes revenue from postback. |
| Currency | Used to interpret dynamic revenue. |
| External id | Helps detect partner-side duplicate or repeated events. |
Outgoing Postbacks templates
Outgoing Postbacks templates use the same Axalot macro format as Offer Links:
https://example.com/pb?clickid={click_id}&sub1={sub1}
{click_id} {sub1} {currency}Only the approved outgoing macros are allowed. {event.*} tokens are not valid in /console/tracker/postbacks.
Postback settings start at the network
Affiliate Network mapping is for incoming partner conversion URLs. /console/tracker/postbacks is for outgoing forwarding after Axalot matches a conversion.