Basics of Integration

Integration rules described in this section are intended to achieve the following goals: 

  • set up the affiliate network to keep track of all actions performed by advertisers;
  • ensure campaign is set up to work correctly in Post-Click period;
  • monitor all the actions between our clients and their advertisers;
  • provide advertisers with full data which helps to avoid bad quality traffic.

Basic Principles

Basic workflow consists of three parts and can be used for most campaigns. 

Typical example of such workflow is the online store campaign. However, individual peculiarities and technical constraints may affect the workflow. In case the standard workflow cannot be used, technical specialist from both sides must work in close cooperation to provide conditions for achieving the goals described above.  

Integration consists of the following parts:

  • processing of click-through from affiliate network to advertiser's site;
  • notifying affiliate network on an action; 
  • notifying affiliate network on action status change.


s2s Integration (Postbacks)

You can also use postback queries to notify on an action.



  • http://postBack.url/ - PostBack address (provided by manager)
  • clickid - click id parameter

  • {clickid} - should be replaced with advertiser’s macro for click id

Additional parameters:

  • &action_id= - unique request ID in the advertiser's system
  • &goal= - goal number or goal value
  • &sum= - payout for conversion
  • &ip= - IP address of visitor who made a request (partially hidden in accordance with GDPR policy)
  • &status= - request status (the default value is '1' - "approved" if a conversion meets all the restrictions set in the offer's settings)
  • &referrer= - referrer (additional information on traffic and deeplinks)
  • &comment= - comment
  • &secure= - hash password generated on offer, advertiser level
  • &custom_field1= - custom field 1
  • &custom_field2= - custom field 2
  • &custom_field3= - custom field 3
  • &custom_field4= - custom field 4
  • &custom_field5= - custom field 5
  • &custom_field6= - custom field 6
  • &custom_field7= - custom field 7


JS and Image pixel Integration

The system uses tracking pixel (later referred as "pixel") to notify affiliate network on an action performed on advertiser's website. 

In lay terms, when an action is performed, the code of the page that visitor is loading includes the code that loads a transparent 1x1 pixel size image from the Affise server which is invisible for visitor. This image is used to execute a request to the affiliate network server and transfer the required parameters.

<script language="javaScript" type="text/javascript" src=""></script>

where - is a tracking domain specified when creating the application.

If the advertiser assigns unique ID for every action to make it possible to easily find additional information for each action, such ID must be transferred to pixel by the "afid" parameter. Below are ID examples:

  • request number;
  • visitor ID;
  • payment number;
  • the ID of an object created in advertiser's system;
  • and so on.

Any sequence of numbers, letters, and characters without spaces can serve as an ID. The afid parameter is transferred to pixel in the following way: 

<script language="JavaScript" type="text/javascript">
var afid='11111';
var afprice=202.75;
<script language="javaScript" type="text/javascript" src=""></script>


Another way to establish js integration is to send a postback through the image.

Additional parameters you may add to GET request, for example:



afid - unique request ID on advertiser's side

afprice - payout for conversion

afgoal - goal ID

afua - user-agent

afcomment - comment

afstatus - status of the conversion (status '2' by default)

afsecure - hash password generated on offer, advertiser level

custom_field1 = - custom field 1

custom_field2 = - custom field 2

custom_field3 = - custom field 3

custom_field4 = - custom field 4

custom_field5 = - custom field 5

custom_field6 = - custom field 6

custom_field7 = - custom field 7

The script is intended for transferring visitor's action and must be installed on the page that confirms this action.   

Lead Statuses:

  • 1 – action is «approved» (paid by advertiser);
  • 2 – action is «pending» (decision in process, request status later);
  • 3 – action is «declined» (not paid by advertiser);
  • 4 – requested action «does not exist» (requested ID is not registered on advertiser's site);
  • 5 - action is «approved» and put on Hold (will be paid by advertiser at a certain amount of time - the period of hold is taken from the offer settings).
Was this article helpful?
18 out of 25 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.