Postback Tester
Fire sample conversion callbacks and read the raw response before launch.
Open tool >Postback QA
Dry-run Binom callbacks and confirm every macro resolves before traffic scales.
Binom gives performance teams total control, but that freedom means you are responsible for every token, macro, and firewall rule. The fastest way to keep partners happy is to capture a clean request/response log before you send paid traffic. This playbook walks through the click-to-postback workflow, shows where Redirect Checker, Click ID Extractor, and UTM Builder slot in, and explains how to package the evidence for affiliate managers or finance teams.
Self-hosted setups can drift without anyone noticing: an engineer migrates servers, a partner rotates payout macros, or an account manager adds SSL enforcement. When you own the tracker, you also own the investigation. Logged mock conversions give you a baseline so disputes turn into quick screenshots instead of week-long Slack threads.
Use Redirect Checker to fire a preview click through the exact flow (domains, cloaker branches, offer path) and store the resulting click ID or sub_id.
Cross-reference the offer's documentation with your Binom template, making sure payout, currency, goal, and optional tokens exist in both places.
Open Postback Builder or manually assemble the callback URL, inserting the captured click ID and sample payout figures.
Send the URL through Postback Tester. Capture headers, body, response code, and latency. Annotate whether the partner echoed the data back.
Forward the tester log to your affiliate manager and drop a copy into your runbook so finance and engineering can verify the payload later.
Schedule recurring checks (weekly or before every new offer) and keep a changelog of endpoints, tokens, and responses.
Run Postback Tester every time you tweak Binom flows, migrate servers, or onboard a new offer. Pair it with Redirect Checker and Click ID Extractor so you always test with real IDs, and keep UTM Builder handy if you need to recreate the full journey. Having a clean Binom log makes support tickets painless and keeps partners confident that your tracker is production-ready.
Open Postback TesterUse this diagnostic stack whenever you need to capture evidence or verify that a fix worked.
Fire sample conversion callbacks and read the raw response before launch.
Open tool >Generate correct postback URLs for trackers and affiliate networks.
Open tool >Check HTTP redirect chains and status codes.
Open tool >Create campaign tracking URLs with UTM parameters.
Open tool >Pair these workflows with deeper troubleshooting guides for redirects, postbacks, and UTMs.
Tracking bugs rarely travel alone. Explore these related guides to build a full remediation plan.
Networks show zero conversions because callbacks never trigger or fail validation.
View guide >Callbacks arrive but contain literal {clickid} or {payout} strings because the template never swapped values.
View guide >Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.
View guide >Need deeper theory? These long-form KB articles expand on the concepts touched in the troubleshooting guide.
Use a structured checklist to diagnose silent postback failures, missing payouts, and inconsistent partner logs.
Read article >Build a repeatable QA routine for postbacks before launching campaigns or onboarding new partners.
Read article >