Definition
A postback testing tool is a small utility for verifying that server-to-server conversion tracking is wired correctly before a campaign spends real money. It lets an integrator fire a sample postback with a chosen click ID and parameters, inspect exactly what URL the offer or tracker received, check that the conversion registered against the right click, and confirm that payout value, currency, event type and security parameters pass through intact.
Many trackers include a built-in version; standalone tools and request-inspection endpoints do the same job.
The reason it exists is that S2S tracking fails silently. If the postback URL is slightly wrong, a parameter is misnamed, the click ID macro is not being replaced, or the offer only sends postbacks from an IP the tracker rejects, conversions simply never arrive - and the buyer discovers it only after spending, when revenue looks like zero or is badly understated.
In context
In iGaming, where the tracked events (registration, FTD, qualifying deposit, sometimes revenue-share settlement) carry real money and arrive with a delay, testing the postback chain end to end is standard onboarding for any new operator or network integration. The integrator confirms each event type maps correctly, that the FTD postback carries the deposit amount where a value-based bid depends on it, that duplicate postbacks are de-duplicated, and that the operator's postbacks are signed or IP-whitelisted so conversions cannot be spoofed by a third party.
Post-launch, the same tooling supports discrepancy investigation: when the tracker's FTD count and the operator's reported count diverge, replaying and inspecting postbacks isolates whether the loss is at the click stage, the redirect, the postback firing, or attribution-window mismatch. Getting this right protects both sides - the affiliate is paid for conversions actually delivered, and the operator is not billed for conversions that its own logs do not support.
A clean postback test at integration time prevents most later reconciliation disputes.
Worked example
Onboarding a new operator, an affiliate manager fires test postbacks for registration and FTD with a known click ID. The registration event maps fine, but the FTD postback arrives without the deposit amount, which the buyer's value-based bidding needs.
The operator adds the amount macro before launch, avoiding weeks of mis-optimised spend.
Related terms
Frequently asked questions
Browse more iGaming terms in our glossary.
← Back to glossary