Debug Postbacks and Pixels
Last updated: September 17, 2026
Where to find it
Advertisers > Debug Postback
Two tabs:
- Debug Postbacks — S2S postback logs
- Debug Pixels — browser pixel events
How to use
- Filter by Advertiser, Offers, Affiliates, Date Range or Click IDs
- Click Run Debug
- Read the log
Log column meanings
| Column | What it tells you |
|---|---|
| Request URL | Exact URL fired — shows all parameters passed |
| Server Message | Response body from receiving server |
| Status Code | HTTP response (see below) |
| Latency | Processing time in milliseconds |
Status code reference
| Code | Meaning | Action |
|---|---|---|
| 200 | Success | None needed |
| 400 | Bad Request — invalid parameters | Check Request URL — required parameter missing |
| 404 | Click ID not found | Advertiser not returning the correct click_id |
| 409 | Duplicate — already recorded | Normal for re-fires; investigate if consistent |
| 5xx | Server error | Contact TrackOG support |
| Timeout | No response | Affiliate's server not responding |
Common causes of missing conversions
{click_id}missing from Advertiser Offer URL- Advertiser not storing and returning the exact click_id
- Offer inactive or geo rejected when click came in
- Auto-cancel rule fired (Settings > Tracking)
Frequently Asked Questions
Q: Status 200 but conversion not in reports. Why? A: Postback received but a rule may have cancelled it. Check Settings > Tracking auto-cancel rules and offer status.
Q: No postback logs at all. What does that mean? A: Advertiser hasn't fired the postback yet, or they're using the wrong URL. Re-share the correct postback URL.
Related articles
- Conversions Not Showing? Step-by-Step Checklist
- Postback Logs: Status Codes and Fixes