Prove a partner regression
Replay yesterday's payload and screenshot the empty field the partner returned today.
Postback Debugger
Troubleshoot failing callbacks by resending the exact payload you received from partners.
When conversions stop reporting, the postback debugger gives you a forensic view of each callback. Inspect the response body, status code, and latency to see whether the network rejected your request or authentication failed.
Log each debug session so finance, engineering, and compliance teams know exactly when a payout was fixed.
Replay a partner payload
Drop in the URL plus parameters you received and capture the success or failure response.
Related tools
How this postback tester works
The tester constructs an HTTP request using your callback URL and any custom parameters you add.
- Fill in tokens such as {clickid}, payout amount, and status.
- Send the request and read the raw body, headers, and status code.
- Iterate until the network returns the success message you expect.
Troubleshooting failed callbacks
Use this view when payouts stop, conversions misfire, or macros arrive empty.
Why analysts keep it open
Reproduce failures
Replay the broken payload and log the error for engineers.
Validate forwarding
Confirm the callback still contains the fields you plan to pass to Meta or Google.
Escalate faster
Share the logged response so partners fix issues quickly.
Debug a failed payout
Replay the exact callback from your logs, swap in known-good values, and prove where the error occurs.
- Paste the raw URL you captured from the network when conversions stopped.
- Replace only the suspect parameters (like payout or status) to isolate the failure.
- Share the side-by-side success vs failure logs with engineering or the affiliate manager.
Use this workflow once conversion gaps show up.
Replay failing callbacks with evidence
Resend the exact payload you supply and capture the error or success message.
- Paste the callback exactly as you received it from the partner.
- Reproduce 4xx/5xx responses and capture the body for engineers.
- Document the working payload once the issue is resolved.
Use it when
-
•
Payouts stop after a new macro rollout.
-
•
BI teams question missing conversion values.
-
•
You forward callbacks into Meta CAPI or Google and need to ensure data survived.
Practical examples
Keep CRM notes tidy
Attach the failing and passing payloads to your CRM ticket so future owners know the history.
Forward into automation
Once the debugger shows correct values, use the same payload in webhook or Zapier tests.
Contextual resources
Fix postback not received
→
Run this playbook if callbacks never reach your endpoint.
Facebook CAPI Test
→
Forward the same payload to Meta after debugging.
FAQ
Postback debugging FAQ
Help when callbacks fail or return partial data.
Should I include sensitive tokens?
Only include what you are comfortable sharing in your documentation; the tool shows responses in your browser.
Can I chain this into CAPI tests?
Yes—once the postback payload is correct, feed the same values into the Facebook CAPI Tester.
Need help fixing tracking or attribution?
If you're struggling with tracking issues, attribution problems, or broken postbacks, I offer professional tracking setup and audits.
Fix your tracking issues → Request free auditTools for Affiliate Tracking Debugging
Related tools
Related Tracking Tools
UTM Builder
Create campaign tracking URLs with UTM parameters.
Open tool →URL Parameter Debugger
Decode long tracking links and spot missing macros or blank values.
Open tool →Click ID Extractor
Extract click IDs and tracking parameters from URLs instantly.
Open tool →