Postback URL Builder & Validator

What a postback URL actually does

A conversion pixel is a snippet on your confirmation page that tells your tracker a sale or lead just happened. A server-to-server (S2S) postback does the same job, except your server (or the affiliate network holding the click) sends the request directly, instead of the visitor's browser. Both arrive at the same conversion endpoint on your tracking domain, and both close the loop that turns a recorded click into attributed, payable revenue. The postback is just a URL with the right parameters, fired at the right moment, so getting the URL right is most of the battle.

The click ID anchors attribution

When a visitor arrives through a tracking link, the platform appends a click ID to the destination URL: ll_cid in LimeliJourney, transaction_id in Everflow and TUNE, cid in Voluum, an s2 sub-ID in CAKE. Carry that value through your funnel and pass it back on the postback. It links the conversion to its original click and back-fills the affiliate, campaign, channel, and creative automatically, so you never name them by hand. Fire without a click ID and the conversion can only fall back to a cookie or land unattributed, which is why this builder treats a missing click ID as a hard error, not a warning.

One transaction ID prevents duplicates

The transaction ID (txn, order_id, or txid depending on the platform) is your unique-per-conversion order or transaction number. It deduplicates: re-firing the same postback with the same transaction ID updates the existing conversion instead of creating a second one, so retries, page refreshes, and revised amounts are all safe. The classic mistake is shipping the placeholder unchanged: leave TRANSACTION_ID or {order_id} in the live URL and each fire is recorded on its own, quietly doubling your numbers. Replace it with a real value.

Leave macros raw, encode everything else

A macro like {transaction_id} or #s2# is a token the platform swaps for a real value at fire time. It must stay un-encoded: percent-encode the braces or hashes and the platform can no longer recognise the token, so the substitution silently fails. Everything that is a literal value, though, must be URL-encoded: a stray space, ampersand, or equals sign in a raw value breaks the query string. This tool encodes your literal values for you and leaves recognised macros alone, then flags any value that still looks unsafe.

Read the response, and always use HTTPS

A server fire (a POST, or a GET with format=json on platforms that support it) returns a small JSON acknowledgement you can store and reconcile against: an ok flag, a minted conversion ID for your CRM, and a status naming the real outcome. Fire over https:// every time; an http:// postback can be stripped, downgraded, or blocked, and a lost postback is a lost commission. Want to see a postback land and attribute on your own numbers? Book a demo and we will wire it up with you.