Postback Tester
Captures the exact payload and response, proving what left your tracker.
Open tool >Postback troubleshooting
Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.
Postback Not Received surfaces when your tracker reports success but partners deny seeing callbacks. The split usually hides between your infrastructure and theirs: blocked IPs, TLS mismatches, or payload validation errors.
You win these disputes by showing evidence from each hop-what left your tracker, how the partner responded, and whether they acknowledged the request.
Networks juggle anti-fraud and availability. When their defenses misclassify your callbacks, conversions vanish and payout disputes begin.
Analytics platforms that ingest postbacks also reject malformed payloads without warnings.
Diagnose where the callback died: on your tracker (delivery), in transit (network), or at the partner (validation).
Mirror the tracker's delivery record with your own tests, then sync timelines with partner monitoring.
Grab the delivery report with timestamps, endpoints, response codes, and any body snippets.
Send the same payload manually and capture the full transcript.
Confirm outbound IPs, TLS versions, and firewall rules match the partner's allowlist.
Share your logs and request theirs for the same timeframe. Highlight discrepancies.
Schedule Postback Tester pings or lightweight partner endpoints to alert you when delivery stops.
Captures the exact payload and response, proving what left your tracker.
Open tool >Keeps macro mappings accurate when replaying payloads.
Open tool >Regenerates clean campaign URLs so you can produce new click IDs for testing.
Open tool >Add delivery monitors to every scaled offer. Once you know callbacks failed, your logs do the convincing for you.
Capture a change log for partner credentials, IP allowlists, and endpoint migrations so you can pinpoint which change triggered the outage.
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 >TikTok click IDs fall out across translation layers or smartlinks, leaving Events API payloads without match keys.
View guide >Use this diagnostic stack whenever you need to capture evidence or verify that a fix worked.
Check HTTP redirect chains and status codes.
Open tool >Extract click IDs and tracking parameters from URLs instantly.
Open tool >Create campaign tracking URLs with UTM parameters.
Open tool >Fire sample conversion callbacks and read the raw response before launch.
Open tool >Verify Meta, TikTok, and Google tags fire on any landing page instantly.
Open tool >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 >Learn how server-to-server callbacks replace fragile pixels, what payloads should include, and how to keep networks, trackers, and CRMs aligned.
Read article >