Postback Tester
Saves the exact request/response for partner escalations.
Open tool >Postback troubleshooting
Postback Not Working
Networks show zero conversions because callbacks never trigger or fail validation.
Introduction
Postback Not Working appears when trackers register conversions yet affiliate dashboards stay flat. Callbacks either never leave your infrastructure or arrive missing authentication, goal IDs, or payout data.
Treat postback debugging like a forensic exercise: capture the click ID, rebuild the callback, log the response, and confirm whether the tracker even attempted delivery.
Why the problem happens
Postbacks close the loop between media spend and payouts. When they fail, ad platforms lose optimization signals, finance cannot match revenue, and partner trust erodes.
- Offer templates change macro names but teams keep using the previous callback.
- Partners tighten security (HTTPS, signatures, allowlists) without warning.
- Tracker job queues pause during deployments and no one notices until the queue overflows.
Common causes
Group incidents into delivery (callback never sent), transport (blocked), and payload (rejected). Knowing the bucket speeds resolution.
- Background workers crashed or credentials expired so nothing leaves the queue.
- Firewall or TLS mismatches block the connection.
- Missing goal IDs, currency, or payout fields make partners drop the event.
Step-by-step troubleshooting
Work outward from the tracker: prove the conversion exists, rebuild the callback, replay it, and inspect automatic delivery logs.
-
Capture a fresh conversion
Pull click ID, goal, payout, and timestamp from the tracker or CRM.
-
Rebuild the template
Use Postback Builder or your snippet to insert the captured values and verify encoding.
-
Run Postback Tester
Send the callback manually and archive the headers, body, status code, and latency.
-
Check automatic delivery
Review queues and logs to ensure callbacks are leaving the tracker without errors.
Tools that help solve the problem
Postback URL Builder
Keeps macro names and auth parameters consistent.
Open tool >Redirect Checker
Confirms the original click still carried identifiers.
Open tool >Conclusion
Document the root cause, update the template or credentials, and add monitoring so future outages trigger alerts instead of payout disputes.