Postback Tester

Fire sample conversion callbacks and read the raw response before launch.

Use Postback Tester when you need to confirm that a callback actually works before launch, reproduce a partner-side failure with proof, or validate Keitaro and Binom postbacks before real conversions arrive.

The goal is to see the raw response early, catch broken macros or rejected requests, and move from guesswork to a reproducible callback QA workflow.

Treat the page as the postback control center inside the wider tracking cluster: resolve the landing path first, confirm the click ID that should come back later, then use the first replay to decide whether you should rebuild the URL, validate the template, inspect a failing response, or move into the right fix guide.

A useful first replay should also answer a routing question, not just a transport question: do you need the broader Knowledge Base runbook, the narrower Fix Tracking Issues library, or the wider Tools hub because the callback is only one symptom in a larger launch failure.

The strongest recovery workflow keeps one incident thread from first click to final payout lookup. That means saving redirect proof, browser-side click-ID proof, the exact callback payload, and the partner-side credit result in one handoff pack instead of letting each owner debug a different transaction.

Send a sample callback

Paste the network or tracker postback URL to capture the raw response before launch. If the callback is not final yet, start with Postback URL Builder or Postback URL Checker first.

Example

Example test URL: https://tracker.example/postback?click_id=demo123&status=approved&payout=1.50. Use a test endpoint and compare the returned HTTP status and body with the receiver log.

Send a test callback to a staging or test endpoint before launch. Check the response here, then confirm the receiver stored the expected click ID and conversion in its own logs.

This tool sends an HTTP request and displays the response. A 200 status alone does not prove the receiver stored a conversion, and the tool cannot validate a network's private macros.

Troubleshooting guide