Skip to content
DocsGet startedMulti-provider campaigns

Campaigns with multiple providers

Buy traffic from one source, route it to offers from several networks, and keep each conversion tied to the offer that received the click.

What does provider mean?

A traffic source sends visitors, such as an ad platform. An affiliate network supplies offers and returns conversions. An offer is the destination you promote. A lander is an optional page before an offer. These are separate entities in Capve.

One source per campaign, several offers

A campaign has one traffic source. To buy traffic from multiple ad platforms, create one campaign per source and put them in the same group. Each campaign can route to multiple offers, including offers from different networks.

Example: compare two networks

You buy traffic from Adcash and want to compare two welcome offers. Create Network A and Network B, then an offer for each network. The following is a sample setup, not a preconfigured integration.

Traffic sourceAdcashSource click ID + cost
Capve campaignWelcome offersWeighted rotation
Offer destinationsNetwork A · 70 weightNetwork B · 30 weight
  1. Create a traffic source from its template. Check the external click ID, cost, and named-token mappings.
  2. Create both affiliate networks. Add an offer for each, select its network, set its URL and payout, and pass {click_id} in the network's supported tracking parameter.
  3. Create a campaign and select the traffic source. Add two offer paths, one for each offer. With weighted rotation, assign weights 70 and 30. These are relative weights, not an exact split for a small sample.
  4. Alternatively, use one path with multiple weighted offers when they share the same lander setup. See routing rules for geo-specific paths and rotation modes.
  5. Configure an incoming conversion postback in each network, using that network's macro for the stored Capve click ID. Include your account postback key.
  6. Copy the campaign's generated traffic source link into the ad platform. Test a click and conversion through each offer before buying traffic.

Map each network separately

Two networks can use different names for the same tracking field. The offer URL uses a Capve macro. The incoming postback uses the network's macro. Never assume the names are interchangeable.

Example networkOffer URL you configureValue returned as cnv_id
Network Ahttps://a.example/offer?aff_sub={click_id}The stored aff_sub value
Network Bhttps://b.example/offer?subid={click_id}The stored subid value

These parameter names are illustrative. Use each provider's current integration settings or Capve's network template, and verify the resulting request. Both networks must return Capve's ID. The click already stores its selected offer and path, so you do not need to send an offer ID back to choose attribution.

Send conversions to the right recipients

Incoming postbacks report a conversion to Capve. Outgoing postbacks notify other systems from Capve. Configure outgoing callbacks at the scope you need:

  • Campaign: for callbacks on that campaign's conversion statuses.
  • Traffic source: for an approved conversion, using the source's original {external_id}. Source postback percentage settings apply.
  • Affiliate network: for an approved conversion on an offer belonging to that network. Capve uses the clicked offer's network, not every network in the campaign.

Each callback can be limited to an event such as ftd. Avoid configuring the same recipient at several scopes unless it should receive multiple requests. Inspect delivery history when a recipient does not receive a callback.

Add a second traffic source

For example, create “Welcome offers / Adcash” and “Welcome offers / TrafficStars” in the same group. Reuse your offers and landers, but select the matching source and check its tokens and outgoing postback in each campaign. Use the source link generated for that campaign, rather than sending both sources to one campaign URL.

Groups organize related campaigns; they do not merge source settings or turn a campaign into a multi-source router. Keep SubID meanings consistent if you want to compare placements or creatives across sources.

Verify before sending paid traffic

  • Check the redirect for each offer and confirm it contains a fresh Capve click ID.
  • Ask each network to send a test postback with the ID it received. Confirm the conversion appears against the correct campaign and offer.
  • Compare reports by offer, path, country, and SubID. Check registration and FTD event counts separately.
  • Confirm source cost and outgoing callback IDs. Do not count the same revenue once as an unnamed conversion and again as FTD.
Traffic source ID → Capve stores external_id
Capve click_id → chosen offer → incoming cnv_id
Approved conversion → source callback with external_id

Next: understand Click IDs & SubIDs, configure source tokens, or set up postbacks.