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.
{click_id}, {aff_sub}, #CLICKID#.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. |
How to build a postback URL
- 1
Enter the postback endpoint
The URL your partner will call when a conversion happens, such as your tracker's postback address.
- 2
Map the click ID
Name the parameter that carries the click ID and the macro the partner fills in, such as {click_id} or #CLICKID#.
- 3
Add payout, status and transaction ID
Payout gives the conversion a value, status allows later reversals and the transaction ID stops duplicate conversions.
- 4
Copy and send it to the partner
Check the filled example first; it shows exactly what your server will receive.
How an S2S postback works
When a visitor clicks an affiliate link, the tracker creates a click ID and passes it to the advertiser in the landing URL. The advertiser stores it with the visit.
When that visitor converts, the advertiser's server calls the postback URL with the stored click ID in place of the macro. The tracker matches it to the original click and credits the affiliate.
No cookies or browser pixels are involved, which is why server-to-server tracking keeps working with ad blockers, Safari ITP and in-app browsers.
More free affiliate tools
Postback URL Builder FAQ
What is a postback URL?
A postback URL is the address an advertiser's server calls to report a conversion to a tracker. It carries the click ID of the visit that converted, plus optional payout, status and order details.
What is the most common postback mistake?
A missing or wrong click ID macro. If the value the tracker receives does not match a click it issued, the conversion cannot be attributed.
Why include a transaction ID?
Servers retry. With a unique order or transaction ID, a repeated postback is recognised as the same conversion instead of being counted and paid twice.
Does this tool send the postback?
No. It builds and explains the URL in your browser only. Use your tracker's postback test to fire a test conversion.
