If your measurement is based on first-party cookies, you MUST use the DIRECT METHOD (with xtor in the URL) described below.
In the context of a visit, this method only considers one click per URL containing a strictly identical xtor.
Add the xtor variable in the links directing to your site:
- If the link directs to the root of the site or a directory: >> enter http://www.site.com/#xtor=...
- If the link directs to a file without a transmitted variable: >> enter http://www.site.com/index.php#xtor=...
- If the link directs to a file with a transmitted variable: >> enter http://www.site.com/index.php?other_variable=2#xtor=...
- The use of # allows you to avoid indexing these xtor variables in search engines.
- If you use a tool that does not support "#" characters, you must replace "#" with"?" (or "&", depending on the position of the variable
This method allows more precise click measurement. While the "direct" method considers any URL containing xtor as a click, the “redirection” method allows you to have an additional parameter which ensures that a click is only counted when passing through the redirection server.
The principle of tagging in this way is to modify the URLs declared in the interface in order to replace them with a URL on our servers (in charge of the redirect).
How is the URL composed?
Logxxxx: subdomain in charge of redirecting and the measurement of clicks (xxxx to be replaced by what you are given in your account).
go.url: address enabling a "strict" redirection to your site (without changing the URL contained in the URL variable). This method does not allow for "post click" measurement (prior attribution) as the destination URL does not contain the xtor variable.
xts: the xts variable contains your site ID (xtsite of the tagging code).
s2: ID of the level 2 of the page on which the user arrives (http://www.site.com in green, in the example). This variable allows you to retrieve the number of clicks on your campaign when analysing the level 2 in question. This variable is optional: you must have previously declared these level 2s in the interface.
xtor: the xtor variable must at least contain a prefix indicating the type of campaign, as well as a campaign ID.
url: the URL variable contains the precise destination URL.
If you want to conserve prior attribution measurement, you must replace go.url with gopc.url. Doing so allows you to arrive on your site with the xtor variable added to end of the string. If the URL to which you are redirecting contains "&" characters (but not "?"), a different method is recommended. Please contact our Support Centre for more details.
Structure of xtor variables
The different parameters of the xtor (with the following nomenclature: xtor=A-B-C-D-E-F) must follow these rules:
A (source): prefix EREC, EPR or ES
B: campaign ID value
C: Email ID in the format [label] or id[label]
D: Email date in short format: YYYYMMDD
E: link ID in the format "[label]" (filled out by you according to the link). Only fill this in if you want specific details about the Internet user’s click (notably the overlay measurement of this email)
The level of precision of the click remains the customer’s choice: each link, or only the main areas.
F: contacts list with contact ID according to id@list (for example 1435@1 for contact 1435 of list 1).
- The label of email (C) and link (E) must be filled out in the same way as page names: without special characters (accents, spaces or others).
- If [xxxxx] and id[xxxxx] are found, we’ll consider that these are 2 different elements (even if the label is identical).
- If we find the same ID with 2 different labels (for example 23[creative] and 23[creatives]), only the 1st label will be saved and associated with the ID.
- The values of A, B, C (and possibly E, F,) must be the same between link measurement and the measurement of email opens.
- If E is not filled out, the visit is associated with email (C), without specifying the link that the user has clicked. In addition, without variable E, no overlay analysis will be available.
- Unlike the measurement of email openings, there must not be a 'type=email' variable in the click measurement.