Binom Postback: Conversion Delivery to Ad Platforms

The Binom postback contour runs on one simple contract: a unique click token travels out with every visitor, and the affiliate network returns that token in a postback when the visitor converts. Everything else - statuses, payouts, currencies, the delivery hop to the Conversions API - hangs off that exchange. This guide walks the contour end to end: the token mechanism, the postback v2 URL parameter by parameter, the status and upsell behavior, and the final hop that turns matched conversions into platform events.

Meta-specific wiring for Binom - the integration that posts into Meta's dataset - has its own deep dive in Binom and Facebook CAPI; the Keitaro version of the same contour is compared in the network postback to CAPI guide.

The Token: Out With the Click, Back With the Postback

Token mechanics are the foundation of the contour:

1. Your offer link carries the {clickid} token - appended as a sub parameter, for example &sub1={clickid}.
2. At click time, Binom replaces the token with a unique click ID and records the click.
3. The affiliate network stores that ID and returns it inside its postback when a conversion happens.
4. Matching follows: the tracker pairs the returned ID against the original click, and the conversion becomes visible in reports (Binom postback v2 documentation).

The same pattern as every tracker's subid echo, under Binom's names. It also fails the same way: if the offer link was saved without the token - or the network drops the parameter - the postback arrives with nothing to match, and the fix lives at the offer link, not in the tracker.

The Postback v2 URL, Parameter by Parameter

The base URL comes from the Tracking links tab of the tracker settings and follows this documented pattern:

https://your-tracker.example/click?cnv_id={sub1}&payout={sum}&cnv_status={status}

Two parameters deserve a second look. The status fields are deliberately open - cnv_status accepts any value and cnv_status2 adds a second one - which makes Binom's status vocabulary whatever your networks send. And disable_postback=1 is the per-conversion mute button: the conversion registers, but the tracker holds its outgoing postback to the source.

Statuses, Upsell Sums, and Currency

Binom does not ship a fixed status list - cnv_status carries whatever the network sends, which moves the status-to-event mapping fully into your delivery policy. For multiple conversions per click - an add-to-cart at zero payout followed by a purchase, or recurring payments - the Upsell option changes the arithmetic: the tracker sums payouts across postbacks for the same click ID instead of overwriting (postback v2). That switch is the difference between a rebill stream that adds money and one that silently replaces the first sale.

cnv_currency sets the payout currency per postback, keeping mixed-currency networks honest inside one tracker and protecting the value signal - the same currency-edge discipline as the payout value guide.

Where a network cannot send postbacks at all, Binom documents a conversion pixel placed on the success page as the alternative registration path.

The Delivery Hop: From Matched Conversion to CAPI Event

A matched Binom conversion is ready for the last hop: delivery to the ad platform's server-side endpoint. Meta's leg - token, required fields, dedup against the pixel - is documented in the Binom Facebook integration guide, and the platform's own acceptance rules are the ones every server event must respect: required fields, the seven-day event_time window, cross-channel deduplication (Conversions API parameters).

What Binom contributes to the event is the match: the returned cnv_id ties the conversion to a stored click, which supplies the identifiers and context the platform event needs. Upstream discipline - token present, postback echoing it, status vocabulary agreed - is what the postback troubleshooting checklist verifies, because a delivery layer can only forward what the contour matched correctly.

Binom Postback: Frequently Asked Questions

Sources