Postback Logs: Status Codes, Server Messages and Latency
Every time a postback fires — from advertiser to TrackOG, or from TrackOG to affiliate — a log entry is created.
Where to find it
Reports > Postback Logs (also via Advertisers > Debug Postback)
Log columns
| Column | What it tells you |
|---|---|
| Request URL | Exact URL called — all parameters visible |
| Server Message | Response body from receiving server |
| Status Code | HTTP response code |
| Latency | Processing time (ms) |
| Created | When received |
Status code reference
| Code | Meaning | Action |
|---|---|---|
| 200 | Success | None |
| 400 | Bad request | Check parameters — click_id may be missing |
| 404 | Click ID not found | Advertiser not returning correct click_id |
| 409 | Duplicate | Normal for re-fires; investigate if consistent |
| 5xx | Server error | Contact support |
| Timeout | No response | Affiliate server not responding |
Common error patterns
Many 404s: Advertiser modifying or URL-encoding the click_id. Ask them to return it unchanged.
200 but conversion missing: Postback received but auto-cancel rule fired. Check Settings > Tracking.
No logs at all: Advertiser not firing postback yet. Re-share the correct URL.
Frequently Asked Questions
Q: 200 status means the conversion was recorded? A: 200 means request was received. Check Server Message for any error text — it's possible to receive 200 with an error body.
Q: High latency (>2000ms). Is that a problem? A: High latency means the advertiser's server is slow responding. It does not affect whether the conversion is recorded.
Related articles
- Debug Postbacks and Pixels
- Conversions Not Showing? Step-by-Step Checklist