Postback logs

How to use Axalot postback logs to debug incoming conversions, click matching, statuses, revenue, currency, and outgoing callbacks.

What logs show

Postback logs show raw incoming conversion requests and parsed attribution values. Use them when a partner says a conversion was sent but reports do not show the expected result.

Request data

URI, body, IP, user agent, and source.

Attribution data

Click id used to match the postback to a tracked click.

Commercial data

Status, revenue, and currency sent by the partner.

Debug path

Find whether the issue is URL passing, macro mapping, or event delivery.

Console path

Console / Tracker / Reports / Postbacks

Log fields

Field	Use for
`created_at_utc`	Confirm when the postback arrived.
`uri`	Inspect query string and macro values.
`body`	Inspect payload for partners that send body data.
`ip`	Identify sender network or unexpected source.
`user_agent`	Identify partner sender or bot/tool.
`source`	Partner or integration source context.
`click_id`	Match conversion to the original click.
`status`	Partner conversion status.
`revenue`	Partner payout or event revenue.
`currency`	Currency sent with revenue.

Debug order

Confirm the postback arrived in the selected date range.

Check click_id. If it is empty or unknown, inspect the offer link URL and partner click-id parameter.

Check status. If it is unexpected, update affiliate network status mapping.

Check revenue and currency. If empty, verify partner macros and offer revenue mode.

If the postback is matched but outgoing events are missing, inspect pixel/callback event mapping and stream pixel selection.

Common failures

Symptom	Likely cause	Fix
No log row	Partner did not send the postback, URL is wrong, or date range is wrong.	Check partner setup and postback URL.
Empty click id	Offer link did not pass `{click_id}` or partner used the wrong parameter.	Fix offer URL and affiliate network macro docs.
Unknown click id	Postback click id does not belong to a tracked click.	Send a fresh test click and trigger a test conversion.
Wrong status	Partner status value is not mapped.	Update affiliate network status mapping.
Empty revenue	Partner did not send revenue or macro name is wrong.	Fix revenue macro or use base revenue.
Outgoing event missing	Event mapping or stream pixel selection is incomplete.	Check Postbacks and campaign stream pixels.

Do not debug revenue before matching

Revenue, currency, and outgoing callbacks only matter after the postback matches the original click.