Skip to content
DocsGet startedClick IDs & SubIDs

Click IDs & SubIDs

Follow one click from the ad to the offer and back. Keep the click's identity separate from the labels you use to analyze it.

Where each id goes

Offer URL, saved in Capve: subid1={click_id}. That is Capve's id, clk_….

Postback saved in the affiliate network: the network's own macro. YesPlay uses ${subid1}. The network fills it. Pasting {click_id} or {external_id} there sends the braces as text.

Adcash pixel, saved on the traffic source in Capve: cid={external_id}. Required. That is the click id Adcash created. cid={click_id} sends Capve's id, and the conversion does not show in Adcash.

Three identifiers, three jobs

IdentifierWho creates itWhat it answers
click_idCapve, per tracked visitWhich exact click converted? Example: clk_…
external_idThe traffic sourceWhich ad click should the source credit? Captured from clickid or a mapped token.
sub1 to sub10You or the source's macrosWhich placement, creative, or experiment performed best? Many clicks can share a SubID.

An affiliate code identifies a partner, and a campaign key identifies a campaign link. Neither identifies an individual click. A click ID is an attribution token, not a person's identity or an authentication secret.

A click's round trip

  1. The traffic source sends its ID

    The source replaces its own macro before sending the visitor here. In this worked example, its click ID is src_789.

    https://capve.app/c/your_campaign_key?clickid=src_789&sub1=zone_42&sub2=creative_07
  2. Capve creates a different ID

    Capve stores src_789 as external_id and creates its own click_id. Configure the offer URL with the Capve macro below. The network's aff_sub parameter is an example; use the field your network supports.

    https://merchant.example/offer?aff_sub={click_id}

    After expansion, aff_sub contains the Capve ID, such as clk_example.

  3. The network returns the stored Capve ID

    The network must substitute its stored aff_sub value into cnv_id. Configure its postback with its own documented return macro. This is an example of the resulting request, with illustrative values:

    https://capve.app/click?cnv_id=clk_example&event=ftd&payout=80&cnv_status=approved&key=YOUR_POSTBACK_KEY

    Use a real click from your test visit and the account key from the campaign's Tracking & postback card. Keep the key on the network's server, away from visitor-facing URLs.

  4. Capve reports back to the traffic source

    If the source supports S2S postbacks, use {external_id} in its outgoing postback URL. Capve substitutes src_789, so the source can match its own ad click. A source with no postback API needs its own supported conversion integration.

Why clickid can be confusing

On an incoming tracking link, ?clickid=src_789 stores the source's ID. In an offer URL macro, {clickid} and {click_id} both expand to Capve's ID. The two directions use different macros:

  • Offer URL, Capve to the network: {click_id}.
  • Traffic-source pixel, Capve to Adcash: cid={external_id}. Adcash matches the click id it created. cid={click_id} is Capve's id and will not show as a conversion in Adcash.

Choose a stable SubID taxonomy

Start with one meaning per slot. For example, use sub1 for placement, sub2 for creative, and sub3 for experiment. Keep those meanings consistent across sources you compare. Built-in templates can use different mappings, so check their named tokens before combining reports.

sub1=zone_42
sub2=creative_07
sub3=welcome_test_b

Use stable IDs rather than changing labels. URL-encode values, avoid personal information, and group reports by the relevant sub field. A SubID is a reporting dimension; it does not replace the click ID in a postback.

Registration, FTD, and repeat deposits

Send event=registration and event=ftd against the same click to record separate funnel events. FTD means first-time deposit. Without a transaction ID, a repeat postback for the same click and event updates that conversion's status or payout.

For multiple deposits, send event=deposit with a distinct tx_id for each transaction. Reuse that transaction ID when retrying or updating the same deposit. Use unique transaction IDs across your campaign. Capve records events and revenue; it does not calculate affiliate commissions or make payouts.

Check a missing conversion

  • Inspect the actual offer redirect. The network's tracking field must contain a resolved Capve ID (clk_…). The source's id stays on the Adcash pixel as cid={external_id}.
  • Check that every lander and redirect preserves that ID. For a lander CTA, use {lp_click_url} so Capve keeps the selected offer.
  • 400 means a required ID is missing or a value is invalid. 404 means Capve cannot find the click. 403 means the enforced postback key did not match.
  • If revenue differs, verify the payout, currency, status, event, and key. Keyless payouts can be capped to the offer payout.

Continue with multi-provider campaigns or the complete postback reference.