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;

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.

http://click.domain.go2affise.com/ - 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: