Skip to content
DocsGet startedConnect an affiliate network

Connect an affiliate network

You added an offer from a network and pasted a postback URL. How do you know a sale on the network will land on the right click in Capve? This page follows one click with real values and shows exactly what to check.

The whole idea in one sentence

Capve gives the network a click ID on the way out; the network must give that same ID back on the postback. Everything below is about which field carries it.

clk_… Capve click IDaff_sub network's field / macro{click_id} Capve macro, filled by Capve[clickid] traffic source macro

Already sending ads straight to the network?

Many people start like this: in the traffic source (here Adcash), the ad points directly at the network link, with the source's macro in the network's sub ID.

Before: ad URL in Adcash, no tracker

https://goyesplay.com/ysrbgh8c2?subid1=[clickid]

Capve sits in the middle, so that one URL becomes two. Copy the network link into Capve as an offer and keep the link code (ysrbgh8c2 is your network's code). [clickid] can stay: Capve fills it with its own click id, the same value as {click_id}. Swapping to {click_id} is the same result, and reads more clearly.

A · Ad URL in Adcash
capve.app/c/YOUR_CAMPAIGN_KEY?zoneid=[zone]&clickid=[clickid]&…

Copy it from the campaign's Traffic source link card. Adcash fills its […] macros.

B · Offer URL in Capve
https://goyesplay.com/ysrbgh8c2?subid1={click_id}

[clickid] or {click_id}. Capve fills either one with its own ID.

  • Do not recreate the network's link code or campaign name in Capve. Your Capve campaign has its own key; the network link stays exactly the same inside the offer.
  • The offer URL and the Adcash pixel take different macros.
    • Offer URL (Capve → YesPlay): subid1={click_id}. A pasted [clickid] is filled with that same Capve id.
    • Adcash pixel (Capve → Adcash, on the traffic source): cid={external_id}. This is Adcash's own click id. cid={click_id} sends Capve's id, and Adcash cannot match it.
  • In the network's postback, use the macro that returns subid1: /click?cnv_id={subid1} (check the exact name in the network).

Follow one click

Example: a TUNE / HasOffers network whose tracking field is aff_sub. Your network may call it sub1, subid, s2… (see the cheat sheet below). The mechanics are identical.

  1. VisitorClicks your campaign link
    capve.app/c/welcome?clickid=src_789&sub1=zone_42

    Capve stores src_789 as external_id. The offer leaves it off the network link. The Adcash pixel sends it back as cid={external_id}.

  2. CapveCreates a click ID and fills the offer URL

    Offer URL you saved in Capve

    https://network.example/aff_c?offer_id=12&aff_sub={click_id}

    What the visitor is actually sent to

    https://network.example/aff_c?offer_id=12&aff_sub=clk_8f2a91&velo_ref=…&click_id=clk_8f2a91

    Capve replaced {click_id} with clk_8f2a91. It also appends click_id= and velo_ref= on its own, but networks ignore parameters they don't know. Only aff_sub is saved by this network, so the macro must be there.

  3. NetworkStores the ID with its own click
    Network click #55120aff_sub = clk_8f2a91

    The visitor reaches the merchant. Days later they sign up and deposit.

  4. NetworkFires your postback, filling its macro

    Postback URL you pasted in the network

    capve.app/click?cnv_id={aff_sub}&payout={payout}&event=ftd&key=YOUR_POSTBACK_KEY

    Request Capve receives

    capve.app/click?cnv_id=clk_8f2a91&payout=80&event=ftd&key=YOUR_POSTBACK_KEY
  5. CapveFinds clk_8f2a91 and records the conversion
    {"ok":true,"status":"created","conversion":{"click_id":"clk_8f2a91","event":"ftd","amount":80,…}}

    The click already knows its campaign, offer, lander, country and SubIDs, so the FTD shows up on all of them in reports. If the traffic source has a postback, Capve now reports back to it with src_789.

Two URLs, one matching pair

You configure two URLs, in two different places. Each one contains a placeholder that the other side fills in:

1 · Offer URL — set in Capve (Offers)
…?aff_sub={click_id}

Network's field name = Capve macro.
Capve fills {click_id}.

2 · Postback URL — set in the network
/click?cnv_id={aff_sub}

Capve's parameter = network macro.
The network fills {aff_sub}.

Check: the field name in URL 1 and the macro in URL 2 must be the same network field (aff_sub ↔ {aff_sub}). If they match, the round trip works.

Most common mistake

Putting cnv_id={click_id} in the network's postback. The network does not know Capve's macro, so it sends the text {click_id} (or nothing) and Capve answers 404 click not found. In the network, always use the network's macro, for example ${subid1}. This warning is only about the URL saved in the affiliate network. The Adcash pixel is the opposite: there you do write a Capve macro, and it is cid={external_id}.

Cheat sheet by network

These match the built-in templates in Affiliate networks → Create from template, which print both URLs for you. Macro names can change; check your network's postback settings. Always add &key=YOUR_POSTBACK_KEY to the postback.

NetworkAdd to offer URL (in Capve)Postback (in the network)
Genericclickid={click_id}/click?cnv_id={clickid}&payout={payout}
TUNE / HasOffersaff_sub={click_id}/click?cnv_id={aff_sub}&payout={payout}
Everflowsub1={click_id}/click?cnv_id={sub1}&payout={payout_amount}
CAKEs2={click_id}/click?cnv_id=#s2#&payout=#price#
Affisesub1={click_id}/click?cnv_id={sub1}&payout={sum}
Cellxpertsubid={click_id}/click?cnv_id={subid}&payout={commission}
Affilka / SOFTSWISSvar={click_id}/click?cnv_id={var}&payout={commission}
MyAffiliatespayload={click_id}/click?cnv_id={payload}&payout={amount}

Your network is not listed? Find in its docs the “sub ID”, “aff_sub”, “click ID” or “tracking parameter” you can pass on the offer link, and the macro that returns it in postbacks. Use the parameter in the offer URL and the macro after cnv_id=.

Set it up

  1. Create the network

    Affiliate networks → Create from template, pick the platform. Copy the postback URLs it shows (one default, one per event).

  2. Create the offer

    Paste the offer link from the network and add the tracking field with Capve's macro. Keep the network's own parameters:

    https://network.example/aff_c?offer_id=12&aff_id=345&aff_sub={click_id}
  3. Paste the postback in the network

    Add your account key from the campaign's Tracking & postback card. For several funnel steps, add one postback per event:

    Registration postback

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

    FTD postback

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

Prove it works (3 checks, 5 minutes)

  1. Check the outgoing click

    Open your campaign link in a private window. In the network's click log (or the browser's address bar before the merchant redirect), look for aff_sub=clk_….

    aff_sub=clk_8f2a91Good. Copy this ID for check 2.
    aff_sub={click_id}Typo in the macro (Capve leaves unknown macros untouched).
    aff_sub= missing or emptyThe field is not on the offer URL, or a lander dropped it.
    aff_sub=src_789The offer is sending Adcash's id to the network. The offer wants Capve's {click_id}. {external_id} belongs on the Adcash pixel: cid={external_id}.
  2. Send a test postback yourself

    Replace the ID with the one from check 1. Use event and payout you expect:

    curl "https://capve.app/click?cnv_id=clk_8f2a91&payout=1&event=test&key=YOUR_POSTBACK_KEY"

    {"ok":true,"status":"created",…} means Capve accepts the URL. Then use the network's own “test postback” button: it should also return ok. If it fails there but your curl worked, the network's macro or URL is wrong.

  3. See it in the dashboard

    Open the campaign stats or Reports grouped by offer: the conversion (and its event column) appears on the offer you clicked. The test event gets its own column, so it never mixes with real registrations or FTDs.

When a conversion is missing

What you seeCauseFix
400 cnv_id requiredNetwork sent an empty macroOffer URL is missing the field, or the macro name in the postback is wrong.
404 click not foundValue is not a Capve click ID (literal {click_id}, source ID, or the network's own transaction ID)Use the network macro that returns the field you set on the offer URL.
403 invalid postback keyKey enforcement is on and the key is missing or oldCopy the current key from Tracking & postback; it changes when rotated.
Conversion recorded, wrong amountNo key (payout capped to offer payout) or wrong payout macroAdd the key; check the payout macro in the cheat sheet.
Network shows a sale, Capve received nothingPostback not set for that offer or eventCheck the postback is global or attached to this offer in the network.

Next: Click IDs & SubIDs, several networks in one campaign, or the full postback parameter reference.