Free tool
Postback URL Builder
Build a server-to-server conversion postback, check its shape before you hand it to a partner, and see what every macro actually does. Nothing leaves your browser.
The URL your partner will call when a conversion happens.
The parameter that carries back the click identifier. This is the one that must match.
Whatever token the partner substitutes at fire time —
{click_id}, {aff_sub}, #CLICKID#.Approved, pending or rejected. Without it every conversion is treated as final.
Strongly recommended — this is what makes duplicate postbacks harmless.
Optional. Anything else, in
key=value&key=value form.Your postback URL
—
What each parameter is for
Most postback problems are one of four things, and three of them are visible in the URL itself.
| Parameter | Why it matters | What goes wrong without it |
|---|---|---|
| click_id | Ties the conversion back to the exact click that caused it. | Nothing is attributed. This is the single most common cause of "conversions are not showing". |
| payout | What the conversion is worth, so partner payouts can be calculated. | Conversions record with zero value and every revenue report reads as nil. |
| status | Approved, pending or rejected, so reversals can arrive later. | Everything is treated as final, and a refund a week later never reduces the payout. |
| txn_id | Uniquely identifies the order, so a repeated call is deduplicated. | Retries and double-fires become duplicate conversions, and you overpay. |
| currency | Tells the platform how to convert the payout figure. | Mixed-currency programs silently sum unlike numbers. |
| event | Separates a purchase from a signup, install or lead. | Every event type lands in one bucket and per-event payout rules cannot apply. |
