Skip to content
DocsTracking & attributionPostback URL

Postback URL (S2S)

Capve uses a Binom-style server-to-server postback model. Every click gets a unique click_id. When a conversion happens on the affiliate network or merchant side, the network fires a postback to Capve with that click ID — not just an affiliate code.

Follow the Click ID round trip first. The offer and the postback saved in the affiliate network carry Capve's click id (clk_…). In the network, use the network's macro. YesPlay uses ${subid1}.

Some networks name their own return macro {external_id}. That name is theirs, and the value they send is still the clk_… from the offer. Capve's {external_id} macro is a different token: the click id the traffic source sent in. On the Adcash pixel, saved on the traffic source, the parameter is cid={external_id}.

Setting up a network for the first time?

Connect an affiliate network walks one click through the offer URL and postback with real values, with a cheat sheet per network and a 5-minute test.

Incoming postback (network → Capve)

Configure this URL in your affiliate network as the conversion postback:

https://capve.app/click?cnv_id={click_id}&payout={payout}&cnv_status={status}&key=YOUR_POSTBACK_KEY

Replace {click_id}, {payout} and {status} with your network's macros, e.g. cnv_id={aff_sub} on TUNE. The network fills them, not Capve.

Postback key

Click IDs end up in visitors' URLs, so anyone could call the postback with one. Each account has a postback key, shown in the campaign's Tracking & postback card (owners and admins), where you can also rotate it. Pass it as key:

  • Without a valid key, the payout is capped to the clicked offer's payout (when the offer has one).
  • Turn on Reject postbacks without the key once every network URL includes it: postbacks with a missing or wrong key then get 403.
  • Rotating the key invalidates the old one immediately.

Parameters

ParamRequiredDescription
cnv_idYesClick ID from the tracking link (clk_…). Also accepted as click_id.
keyRecommendedAccount postback key. Required when key enforcement is on; without it payouts are capped to the offer payout.
payoutNoRevenue amount in dollars (e.g. 49.99). Also accepts amount as an alias. Defaults to the clicked offer payout, or 0 when an event is set. Unreplaced macro placeholders (e.g. {payout}, ${amount}) are treated as missing and use the default.
cnv_statusNoLead status: lead, sale, rejected. Defaults to lead. Unreplaced macro placeholders (e.g. {status}) are treated as missing and use the default.
eventNoConversion event: registration, ftd, deposit… (a-z, 0-9, _ . -). Each event is a separate conversion. See below.
order_idNoTransaction ID (also tx_id). Distinct IDs create separate conversions. Without it, repeated postbacks for the same click and event update status and payout (e.g. lead → sale); identical repeats are ignored.

Example

https://capve.app/click?cnv_id=clk_a1b2c3d4&payout=99&cnv_status=sale&order_id=txn_123

Events: registration, FTD, …

One campaign can report several events. Give the network one postback URL per event, each with its own event value:

Registration postback

https://capve.app/click?cnv_id={click_id}&payout={payout}&cnv_status={status}&key=YOUR_POSTBACK_KEY&event=registration

FTD postback

https://capve.app/click?cnv_id={click_id}&payout={payout}&cnv_status={status}&key=YOUR_POSTBACK_KEY&event=ftd

A registration and an FTD for the same click are two conversions. Reports, campaign stats and CSV exports show one column per event (Registrations, FTD, …) next to the total.

Outgoing postbacks (Capve → traffic source)

Add as many outgoing postbacks as you need to a campaign, a traffic source or an affiliate network. Each postback can be limited to one event, so a source can get one pixel for registrations and another for FTDs. Leave the event empty to fire on every conversion.

https://your-source.com/postback?click={external_id}&payout={payout}&goal={event}

Adcash pixel, saved on the traffic source

https://www.pixelhere.com/et/event.php?advertiser=YOUR_ADVERTISER&cid={external_id}&id=YOUR_GOAL&value={payout}

cid={external_id} is required on this pixel. Capve fills it with the click id Adcash sent on the campaign link. Keep advertiser and id as Adcash gave them, and add value={payout} for revenue. cid={click_id} sends Capve's clk_… id, and Adcash does not match it, so the conversion stays at zero there.

The warning about pasting {click_id} is only for the postback saved in the affiliate network. On this pixel, {external_id} is the macro you write.

Attached toFires for
CampaignEvery new or updated conversion of the campaign, including rejections
Traffic sourceOnce, when a conversion of a campaign using the source becomes approved, sampled by its postback %
Affiliate networkOnce, when a conversion of a click sent to one of the network's offers becomes approved

Approved means not rejected and not pending or hold. A conversion that arrives as pending fires source and network postbacks when a later postback moves it to an approved status (e.g. sale). Later payout or status updates of an already approved conversion do not fire them again.

Macros: {click_id} (also {clickid}), {external_id} = the source's click ID captured from clickid / external_id on the tracking link, {payout}, {status}, {status2}, {event}, {currency}, {order_id}, {affiliate_code}.

Reports count conversions whose status is not rejected, declined, reversed, refunded, chargeback, canceled, trash or fraud, attributed to the click's time.

When the network names its macro {external_id}

Paste this in the affiliate network only when their docs use that name for the value you sent them on the offer. The value that arrives is still Capve's clk_…. This URL is not the Adcash pixel. The Adcash pixel is saved in Capve, on the traffic source, and Capve fills cid={external_id} with Adcash's click id.

https://capve.app/click?cnv_id={external_id}&payout={sum}&cnv_status=approved&key=YOUR_POSTBACK_KEY

Attribution flow

  1. Visitor clicks tracking link → Capve records click, appends click_id
  2. Visitor converts on offer/merchant
  3. Network sends GET postback to Capve with cnv_id=click_id
  4. Capve attributes conversion, updates stats, fires matching outgoing postbacks

For merchant-hosted checkouts without a network, use server-side conversions with click_id from the landing URL.