Affiliate Postback Log

Every conversion notification you sent out to affiliates, with the URL called and the response their server returned. This is the evidence when a partner says your postbacks are not reaching their tracker.

What This Log Is For

Find it under Reports → Delivery Logs, on the Affiliate Postbacks tab. See Delivery Logs for how the three tabs fit together.

Affiliates run their own tracking. When a conversion is recorded, AffClix calls the postback URL they configured so their platform learns about it too. This log records every one of those outbound calls.

AffClix affiliate postback log showing click ID, campaign, affiliate, position, the postback URL called and the response received
Affiliate Postback Log — outbound calls and the responses received.

Direction Matters

Two postback logs exist and they point opposite ways. Mixing them up wastes a lot of time:

LogDirectionQuestion it answers
Advertiser Postback LogInbound — advertiser to youDid the advertiser tell us about this conversion?
Affiliate Postback LogOutbound — you to affiliateDid we tell the affiliate about it, and did their server accept it?
A conversion can exist with no outbound postback

If the affiliate never configured a postback URL, there is nothing to call and no row here. That is normal — they will still see the conversion in their portal and be paid for it.

Column Reference

ColumnMeaning
Click IDThe click the conversion belongs to.
CampaignWhich campaign the conversion was on.
AffiliateWho the postback was sent to.
Postback URLThe exact URL called, with all macros substituted.
ResponseThe HTTP status and body their server returned.
PositionWhich configured postback fired, when an affiliate has more than one.

Reading Failures

ResponseMeaningWhose problem
200Their server accepted it.Nobody. Delivered.
404The endpoint does not exist.Affiliate — their postback URL is wrong or stale.
403 / 401Rejected on authentication or IP.Affiliate — they need to whitelist your servers.
500Their server errored.Affiliate — transient or a bug on their side.
TimeoutNo response in time.Affiliate — usually a slow or overloaded endpoint.
200 with an error bodyAccepted at HTTP level, rejected by their application.Affiliate — read the body; it usually names the missing parameter.
A 200 is not proof their tracker recorded it

Many platforms return 200 regardless and put the real outcome in the body. If a partner insists conversions are missing while every row here shows 200, read the response bodies before escalating.

Answering Affiliate Questions

"Your postbacks are not reaching us." Work through this, in order:

  1. Filter this log to that affiliate and period

    No rows means no postback was configured, or no conversions were recorded to send.

  2. Check the response codes

    Anything other than a clean 200 is on their side, and the code tells them what to fix.

  3. Send them the exact URL from the log

    They can replay it against their own endpoint and see the failure themselves.

  4. Confirm their macros are right

    A postback missing {aff_click_id} will fire successfully and still be unmatchable on their side. See the macro reference.

Rate this article
★★★★★
Thanks for rating!

Was this article helpful?