The Postback Log records every postback received by Swaarm - both attributed (successfully matched to a click) and unattributed. It's primarily a troubleshooting tool for diagnosing advertiser-side integration issues, particularly when conversions are missing from the Conversion Report.
ℹ️ Unattributed postbacks are still tracked by Swaarm and count towards your organisation usage.
How to use the Postback Log
Go to Reports → Postback Log
Select a date range
Add filters if needed (see below)
Click Search
Filters
Filter | What it does |
Attribution Status | Filter by Passed (attributed) or Failed (unattributed) |
Click ID | Look up postbacks associated with a specific click ID |
Errors | Filter by the specific error that caused attribution to fail |
Offer | Filter by offer |
Postback ID | Look up a specific postback by its ID |
Publisher | Filter by publisher |
Query String | The parameters passed after the domain in the postback URL |
Server IP | The IP address the postback was sent from |
Server UA | The user agent of the server that sent the postback |
ℹ️ To see only unattributed postbacks, add the filter Attribution → Failed.
Common attribution errors
Error | What it means | What to do |
Missing Click ID | The postback was received but no click ID was passed | Ask the advertiser to check your postback URL - the click ID macro is likely missing or misconfigured |
Invalid Click ID | A click ID was passed but Swaarm couldn't find a matching click | Check the click ID format with the advertiser. It may have been altered or truncated |
Failed to decode click ID | Swaarm couldn't parse the click ID | Check for special characters or encoding issues in the postback URL |
Failed to decode PEA Chain | Issue with the privacy-enabled attribution chain | Relevant for privacy/iOS 14.5+ setups — check the advanced privacy integration configuration |
Failed to decode SKAd Postback | Issue decoding an SKAdNetwork postback | Check the SKAd campaign configuration |
Invalid Click Time | The click timestamp is invalid or missing | Verify the advertiser is passing a valid click timestamp |
ℹ️ Missing Click ID is the most common error, but attribution can fail for several reasons - check the Errors column first to understand the specific cause before investigating. To identify which advertiser is sending unattributed postbacks, match the Server IP against a successful postback from the same advertiser in the Conversion Report.
Common use cases
Conversions missing from the Conversion Report
Go to Postback Log, filter by Attribution → Failed, and check the Errors column. The error type will tell you what went wrong - see the table above for what each one means and what to do.
Identifying which advertiser is sending unattributed postbacks
Filter by Attribution → Failed. Note the Server IP of the unattributed postback, then cross-reference it against a successful postback in the Conversion Report from the same date - the matching IP will tell you which advertiser it is.
Conversion report:
Verifying a specific postback was received
Filter by Click ID and enter the click ID you're investigating. If the postback appears with Attribution = Successful, it was received and matched. If it doesn't appear at all, the advertiser hasn't fired the postback.
Export
Click the Download CSV to export the current Postback Log view to CSV:
