fr | en | es | de

Affiliations (SiteLinker)

Discover the latest tools in the
Analytics Suite, thanks to our new online help.

Contents: Hide

An advertiser attributes an ID to a partner site (affiliate). The advertiser will then pay the affiliates commission as a result of the audience and sales that they generate on the advertiser’s site. This principle is similar to the advertising principle (with the notion of display, creations, position etc). What makes affiliation different from advertising is the notion of the partner ID. Generally speaking, an advert runs for a fixed duration of time whereas an affiliation depends on the affiliate. In theory, the more an affiliate displays a banner for an advertiser’s site, the more sales the affiliate will generate for the site, and in return the affiliate will receive more commission

Main definitions

Declaring a marketing campaign


We strongly recommend that you declare your own campaigns. However, you can automate your campaigns. In practical terms, you have to specify an xtor data interval, we will automatically record all of the campaigns which are encountered in this parameter. These campaigns are called "Automatically generated campaigns" which you can rename depending on the ID that is then given to them.

Measuring links


If your measurement is based on a First-party cookie, the DIRECT METHOD (described below) must be used (with xtor in the url).

Direct method

For the purposes of visits, this method will only count one click per URL containing an identical xtor.

Place the xtor variable in the advertisement link that directs traffic to your website. This xtor will be similar to the one used to measure impressions.

Several cases are possible:





- Using # avoids having these xtor variables referenced in search engines.
- Using a tool which does not accept the character "#" implies that you replace "#" with "?" (or "&", depending on the location of the variable).

Redirection method

This method makes it possible to measure the clicks in a more precise fashion.

While the “direct” method considers any URL containing an xtor as a click (with the risk of overestimation due to the use of the “Back” button, or bookmarking), the redirection method is more precise in guaranteeing the click count, only counting when redirection occurs on our server.

The principle of such tagging involves changing the link’s URL to a URL that directs traffic to our server (which is in charge of the final redirection).


This method uses only 3rd party cookie technology to link information from our redirection server with the server hosting your destination site.
This method should not be used if your measurement relies on the use of first-party cookie technology.
If you use version 4.2.001 (or later) of the xtcore.js file this method will not work for Safari browsers which use first-party cookie technology by default.




What is the URL composed of?

Logxxxx: sub-domain in charge of the redirection and measurement of the click (xx should be replaced with the digits you received for your subscriber space).

go.url: address which allows for a “strict” redirection to your website (without changing the URL contained in the url variable. This method doesn’t allow “post click” measurements (remanence) because the destination URL does not contain the xtor variable.

xts: the xts variable contains the AT Internet ID of your website (xtsite in the tag code).

xtor: the xtor variable must contain at least a prefix indicating the type of campaign as well as a campaign ID.

url: the URL variable contains the precise destination URL.


If you wish to track remanence, then you should replace the go.url with gopc.url. This will allow the user to arrive on your website with the xtor variables included at the end of the URL when they click on the link. If the URL of your site contains the character "&" (but no "?"), you should use another method. Please contact our Customer Department (via the Support centre) to get more information.

Structure of the xtor variables

The different parameters in the xtor are as follows:



What makes the source type “Affiliation” unique is the fact that it is possible to add customised variables to the variables which have already been defined. The different sets are separated by "|" whose keyboard shortcuts are as follows:

The rules indicated below must be respected:



A (source): AL prefix.

B: campaign ID (according to ID format [label] or id[label]).


C: type of affiliate partner (according to ID format [label] or id[label]).

D: affiliate partner ID (according to numeric or ID format [label] or id[label]).

E: affiliation ad format (according to predefined ID. You can also specify any other format by using the following nomenclature: "[label]". For example:you can specify either a name [button], or a size [120x40])

F: creation ID (according to ID format [label] or id[label])

G: variant (according to ID format [label] or id[label])


The variable D (affiliate partner ID) depends on the variable C (type of affiliate partner). The same value of D for 2 values of C creates 2 affiliate partners.   


C1: custom variable to be declared in the Interface (according to the format id[libelle]).

C2: custom variable to be declared in the Interface (according to the format id[libelle]).

C3: custom variable to be declared in the Interface (according to the format id[libelle]).






* The names in the square brackets ([ ]) must be indicated as page names: with no special characters (accents, spaces or others).
* If we find [xxxxx] and id[xxxxx], they are considered as 2 different ITEM (even if the name is the same).
If we find the same ID with 2 different names (for example 23[creation] and 23[creations]), only the first name will be kept and associated with the ID.