AXAffilinext Help Center

Postbacks

Send your conversions to your own tracker with global postbacks, test them and read the delivery logs. For publishers.

A postback is a URL the platform calls on your server whenever one of your conversions is recorded, so your own tracker or ad platform learns about it in real time. Set it up once here and it fires for every offer you run.

What you can do here

  • Global Postbacks — Add up to 10 postback URLs. Each can be switched on or off and sent as GET or POST.
  • S2S Tester — Paste any postback URL with macros and fire a test to see the final URL and your server's response.
  • Postback Logs — Every postback sent to you: time, URL, event, status and your server's response. Failed ones can be retried.
  • Macro Reference — Every value you can put in your URL, such as {click_id}, {payout}, {status} and {sub1}–{sub5}.

Fields and settings

FieldWhat it does
Postback URLYour endpoint with macros in braces. It must be a valid URL and include {click_id} or {conversion_id} so you can tell conversions apart. Values: {click_id} the click that converted; {payout} your payout for this conversion; {status} approved, pending or rejected; {sub1}…{sub5} the sub IDs from your link; {transaction_id} the advertiser's order ID.
HTTP methodGET calls your URL with the values in the query string. POST sends them as a JSON body to the URL.
Fire on eventSaved with the postback for your reference. Limits: Postbacks you add here fire for every conversion whatever is chosen. Your account manager can restrict a postback to selected events or offers; otherwise filter by {status} on your side.

How to use it

  1. On Global Postbacks, add your URL with the macros you need, e.g. https://tracker.example.com/pb?cid={click_id}&payout={payout}&status={status}.
  2. Save it and make sure it's active.
  3. Use S2S Tester to fire a test and check your tracker received it.
  4. After real conversions, check Postback Logs for your server's responses.

Examples

Keitaro / Binom style tracker

Pass your own click ID in a sub parameter on the tracking link, then send it back.

  • Tracking link: …&sub5={your_tracker_clickid}
  • Postback: https://tracker.example.com/postback?subid={sub5}&payout={payout}&status={status}

Limitations

  • Restricted: Up to 10 global postbacks per account.
  • Not supported: The Fire on event choice doesn't filter deliveries yet — every conversion fires every active postback.
  • Depends on: Conversions hidden by a campaign's Silent continue fallback rule (for example after a cap) don't fire your postback.

Common mistakes

  • Misspelled macro — Your tracker receives a literal {clickid}. Copy names from the Macro Reference tab.
  • Slow endpoint — Respond immediately and process afterwards; slow responses are logged as failures.

Troubleshooting

  • “URL should contain {click_id} or {conversion_id} macro” — Add one of them to the URL so each postback is identifiable.
  • Logs show 401/403 — Your server needs a token or IP allow-list — allow these requests.
  • Nothing in the logs — No conversion has been recorded yet, or the postback is switched off. Check Reporting → Conversion Report.