Affiliate networks

Integration with affiliate networks requires an agreement with your personal manager. You may need identifiers of offers or products on the side of the affiliate network. Some networks require streams to be created and their IDs to be specified. If the utility does not show a list of postbacks at the time of configuration, you do not need to add postbacks - statuses are loaded via API.

AdBees (ZCPA)

You need to get access to the API from your personal manager, he will provide you with a key. For each offer, you need to create a flow and add postbacks to all events except for the conversion generation.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • zcpa - flow ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid=[sub_id1]&status=[status]&sta=11&stc=12&stt=13

AdCombo

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • adcombo - offer ID.

Aff1

For each offer, you need to create a flow. In the flow settings, by the API button, get the value target_hash.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • aff1 - flow ID target_hash.

AffbayAsia

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • affbay - offer ID.

Creating postbacks in this network by simply setting a URL is not supported, thus you will have to set all parameters separately:

  • Protocol: HTTP or HTTPS depending on your server settings
  • Domain: your control panel domain like site.com
  • Path: /api/sale/status.json

Additional parameters:

  • id - static value: 123-abcde, where 123 and abcde - accordingly, API ID and user API-key, connected to Affbay Asia company on your platform
  • oid - parameter from list: Click ID
  • status - static value: accept for approved orders postback, cancel for denied orders postback, trash for trash orders postback
  • comment - parameter from list: Comment

AffStar

For each offer, you need to create a flow. In flow settings get it's UUID.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • affstar - flow ID.

ApiLeads

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • apl - offer ID.

ArbitPro

For each offer, you need to create a flow. In the flow settings get the hash.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • arbitpro - flow hash.

CPAgetti

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • cgt - offer ID.

CTR

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • ctr - site ID.

DottPro

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • dott - offer ID.

DrCash

For each offer, you need to create a flow. In flow settings get it's hash.

Settings for the integration utility:

  • API: bearer token from the personal account.

Parameters used:

  • drcash - flow ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={sub1}&status={status}

Everad

For each offer, you need to create a flow. In flow settings get it's ID.

Parameters used:

  • everad - flow ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={sid1}&status={status}&pay={payout}&cc={currency}

HotPartner

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • hotpartner - product ID.

IKON

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • ikon - offer ID.

Add postbacks to the following statuses with these "tails":

  • Approve: &oid={aff_sub1}&status=approve&comment={message}
  • Trash: &oid={aff_sub1}&status=trash&comment={message}
  • Cancel: &oid={aff_sub1}&status=cancel&comment={message}
  • Duplicate: &oid={aff_sub1}&status=cancel&reason=7&comment={message}

KMA

For each offer, you need to create a flow. In flow settings get it's ID.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • kma - flow ID.

Lead-R

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • leadr - offer ID.

LeadReaktor

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • leadreaktor - offer ID.

LeadRock

For each offer, you need to create a flow. In flow settings get it's URL.

Settings for the integration utility:

  • API: main token from the personal account.
  • Key: key to generate the request signature.

Parameters used:

  • leadrock - full stream URL like https://leadrock.com/URL-XXXXX-XXXXX.

Add postbacks to the following statuses with these "tails":

  • New: leave the first postback blank
  • Approve: &oid={sub1}&status=approve
  • Cancel: &oid={sub1}&status=cancel
  • Trash: &oid={sub1}&status=trash

LeadTrade

For each offer, you need to create a flow. In flow settings get it's hash.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • leadtrade - flow ID.
  • leadaim - goal ID if required.

LimonAD

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • limonad - offer ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={clickid}&status={status}

Enable in global postback and specify status names:

  • Approved leads status - approve
  • Cancelled leads status - cancel
  • Trash leads status - trash

LuckyOnline

For each offer, you need to create a flow. In flow settings get it's hash.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • lucky - flow ID.

M1 Shop

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • m1 - offer ID.

MetaCPA

For each offer, you need to create a flow. In flow settings get it's ID. In a special section, get the identifier of the country to which you will upload traffic.

Parameters used:

  • meta - flow ID.
  • metageo - geo ID.

Add postbacks to the following statuses with these "tails":

  • Approve: oid={sub1}&status=approve&pay={payout}&cc={currency}
  • Upsell: oid={sub1}&status=approve&pay={payout}&cc={currency}
  • Cancel: oid={sub1}&status=cancel

Money4Leads

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • m4l - offer ID.

MonsterLeads

For each offer, you need to create a flow. In flow settings get it's ID.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • monster - flow ID.

Offerrum (AD1)

For each offer, you need to create a flow. In flow settings get it's ID.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • ad1 - flow ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={sub1}&status={status}

OmniCPA

Settings for the integration utility:

  • API: token from the personal account.
  • Ключ: секретный token from the personal account
  • Flow: your traffic stream ID

Parameters used:

  • omni - offer ID
  • omnisp - special price, optional parameter
  • omnitype - work model (paid, confirmed or static), optional parameter.

PladoMarket

Settings for the integration utility:

  • API: bearer token from the personal account.

Parameters used:

  • plado - offer ID.

ReklPro

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • reklpro - offer ID.

RocketProfit

For each offer, you need to create a flow. In flow settings get it's ID.

Parameters used:

  • rocket - flow ID.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={sid1}&status={status}&pay={payout}&cc={currency}

Shakes

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • shakes - offer ID.
  • shakesurl - link to landing page.

Add postbacks to the following statuses with these "tails":

  • Global: &oid={sub1}&status={status}&stt=reject

Starway

For each offer, you need to create a flow. In flow settings get it's hash.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • starway - offer ID.
  • starflow - flow ID (hash).

TerraLeads

Settings for the integration utility:

  • User: user ID.
  • API: token from the personal account.

Parameters used:

  • terra - offer ID.

Traffic Light (T-Ligth, CPA.tl)

For each offer, you need to create a flow. In flow settings get it's ID.

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • cpatl - offer ID.
  • cpatls - flow ID.

WebVork

Settings for the integration utility:

  • API: token from the personal account.

Parameters used:

  • webvork - offer ID.

WhoCPA

Settings for the integration utility:

  • User: affiliate ID.
  • API: token from the personal account.

Parameters used:

  • whocpa - offer ID.