New!
Discover the latest tools in the Analytics
Suite, thanks to our new online help.
Contents: Hide
The tagging of a site is, technically speaking, a simple process. Tagging consists of placing a few lines of JavaScript code on all pages of a site, mostly by using the ‘copy and paste’ method.
In some cases tagging requires preparation and planning depending on the complexity of the expected results. For this reason clients are strongly advised, when using the professional versions, to consider their marketing plan with care before placing the code on their pages. AT Internet uses analysis levels (group of sites, level 2 sites, chapter etc.) and it is important for clients to know at which level to organise their pages.
The tag code can be modified manually. However, minor modifications which are made to variables can lead to unreliable measurements, and may create JavaScript errors. If you have several sites, the code can be different and as a result you must always retrieve it in the appropriate zone.
There are several types of tags.
The "standard" tag (made up of JavaScript variables and a call to the xtcore.js file) must be inserted into all of the web pages.
<script type="text/javascript">
<!--
xtnv = document; //parent.document or top.document or document
xtsd = "http://logxxxx";
xtsite = "xxxxx"; //site number
xtn2 = ""; //level 2 site
xtpage = ""; //page name (with the use of :: to create chapters)
xtdi = ""; //implication degree
xt_multc = ""; //customised indicators
xt_an = ""; //numeric identifier
xt_ac = ""; //category
//do not modify below
if (window.xtparam!=null){window.xtparam+="&ac="+xt_ac+"&an="+xt_an+xt_multc;}
else{window.xtparam = "&ac="+xt_ac+"&an="+xt_an+xt_multc;};
//-->
</script>
<script type="text/javascript" src="http://www.mysite.com/xtcore.js"></script>
<noscript>
<img width="1" height="1" src="http://logxxxx.xxxx/hit.xiti?s=xxxxx&s2=&p=&di=&ac=&an=&" >
</noscript>
Some of this tag's variables are permanent and compulsory, including:
xtnv: this is the HTML level of the site's tree structure. This variable specifies the area in which the referrer is to be retrieved. By default this variable is entered in "document", and should be changed to "parent.document" in the case of a frame/iframe on the same domain name (for different domain names, please contact our Customer Service).
xtsd: this is the sub-domain of AT Internet's collector. This variable can be retrieved from the Tags panel. This information should not be modified.
xtsite: this is the site's numerical ID. This variable can be retrieved from the Tags panel. This information should not be modified.
Other variables are optional and depend on the specific page that is being traced (recommended):
xtn2: this is the numerical ID of the level 2 site in which you place the traced page. You can then create the level 2 sites on your interface.
xtpage: this is the page label which you must enter.
xtdi: visitor engagement. The default value is 0 or it is left empty. This variable can have values of 1, 2, 3, 4 and 5 for pages which have a visitor engagement that is not equal to 0.
There are also more global values which are available on the whole site:
xt_multc: custom variables.
xt_an: numerical ID of the identified visitor.
xt_ac: numerical ID of the visitor category.
Tagging procedures differ depending on the AT Internet solutions that you have subscribed to.
For any further information on the tag, please go to the section entitled Tagging Methods.
These are specific tags called by HTML events. These include:
Orders and Sales: to monitor the content of an order (available with the SalesTracker module) and the sales on conversion pages
Clicks: to monitor the main clicks on strategic pages (navigation, download, exit, action)
Plug-ins: to find out which plug-ins have been installed on browsers
Usability: to measure the whole clicks (ClickZone® ) and the use of the scroll bar (ScrollView®)
Internal engine: to find out which keywords have been entered the most into your site's internal search engines
MV testing : to test the different versions of web pages (usability tests)
Page variables: to define custom attributes on pages (in addition to xtpage,xtn2 and xtdi)
On site ads: to measure ads displayed on your site (self-promotion and advertisers)
Campaigns: to monitor traffic generated by your marketing campaigns and to measure their visibility (email opens, banner displays, RSS feed update)
For each of these
of codes, we offer:
* a secure version (for https pages or elements) so that the code does
not generate an alert window,
* an XSL version for pages developed in xml and whose content is formatted
with XSL,
* an XHTML version in case you want to strictly apply the XHTML standard.
The same variables tend to appear in most of these codes. They are essential in assigning measurements to your site. These variables are detailed below.
For more information about the technical implementation of all of these tags, please refer to the tagging guide link.
Flash (AS3): to monitor Flash content
Mobile sites and applications
Frames: this is used if your site is made up of frames in URL domains that differ from the declaration file
Redirection tag: this addresses the problem of the loss of the JavaScript referrer during HTML redirections
Intranet sites (closed)
In the tag code, you will see that there are several key elements which are retrieved depending on the site and level 2 site:
The "xtsite=" or "s=" parameter, which corresponds to the site number.
The "xtn2=" or "s2=" parameter, which corresponds to the level 2 site (and therefore the level 2 site which the page including the tag code will be assigned to).
The "xtpage=" or "p=" parameter, which gives a name to the traced page, meaning that it can be assigned to a chapter.
You should not modify the code for the "xtsd"
and "xtsite" parameters yourself - please use the code that
is available in the Tags panel.
Should you experience any coding problems whilst creating your page labels
(by inserting accents or any other special characters) please contact
the Support centre via your interface. Our team will provide you with
a solution which is adapted to your site's tagging.
A site is made up of pages (or other types of format, such as e-mails, Flash, etc): all the pages based on the same site's ID (xtsite) relate to the site which will be analysed in the interface (regardless of its domain name(s)).
The AnalyzerNX solution by AT Internet makes it possible to create level 2 sites. These sites are independent sub-sites and are more than just separate sections. Almost all of the analyses available at site level can also be applied to a level 2 site. It is also very simple to allocate restricted access for one or more level 2 sites to specific users.
As far as tree structure is concerned, level 2 sites are found just under the site level, and must be declared using the interface before they can be used. When you create a level 2 site, place the ID which is generated into the xtn2 variable. Please remember that a page cannot belong to several level 2 sites.
It is therefore very important to define your level 2 sites correctly before tagging the site. You can always define your level 2 sites later, but it will mean tagging the whole site again.
The xtpage parameter (or p= in the “noscript” section) is optional. If it is not given, the URL of the page will be used as the name of the page in your reports.
For example, the following URL will be the name of your page:
http://www.mysite/mypage.html
This parameter is therefore frequently used to clarify the audience reports by providing a more explicit name, for example: Home, Product, Registration, Contact etc.
As this page name is passed to our server using the http protocol (the standard web protocol), it is subject to certain rules to ensure a high degree of browser compatibility. These rules are as follows:
no accentuated characters,
no spaces (we recommend that spaces be replaced with the underscore character, "_"),
no characters other than letters or numbers (do not use inverted commas and apostrophes).
If necessary, here is a list of the recommended characters which can be used:
upper or lower case letters abcdefghijklmnopqrstuvwxyz
numbers 123467890
dots .
slashs /
dashes -,
underscores _
tildes ~
Use the separator :: to place pages into chapters.
Chapters are located just below level 2 sites.
There are 3 different levels of chapters. Pages can be assigned to any chapter at any level. In general, certain pages may never be assigned to a chapter.
There are two
methods which can be used to create a chapter:
* Through the administration interface:
Creating chapters in the administration interface is simple and convenient.
It is possible to create chapters after your site has been tagged. However,
the pages will be disorganised and not associated with any level
after level 2 sites. Pages must therefore be assigned to the chapters
you create, one by one. If you do not have many pages, this administration
method is adequate. However, note that every new page measured will have
to be manually placed in a chapter.
* Through the tag code:
Customising the tag code requires you to think strategically about
your site structure in its entirety. As a result it may seem more difficult
than creating chapters using the administration interface. However, in
the longer term, this is a more durable and flexible solution. When the
tagging and the classification of pages into chapters are clearly defined,
each new page added on-line will be automatically assigned to the correct
chapter. If the chapter does not exist, it will be created when the page
is encountered.
Dynamically creating chapters
In addition to the name of the page, it is possible to create a chapter (and sub-chapter) dynamically and to assign the page to it automatically. To do so, use a double colon, "::" (with no spaces either before, between, or after).
If you wish to dynamically create a chapter you must not use more than three (3) "::". If you do happen to use more than three the "::" will be replaced with "_".
The page name:
xtpage="my_chapter1::my_sub_chapter1::my_sub_chapter2::my_sub_chapter3_my_page";
will be restored in the interface:
A chapter "my_chapter1" containing:
A chapter "my_sub_chapter1" containing:
A sub-chapter "my_sub_chapter2" containing:
A page "my_sub_chapter3_my_page"
AT Internet has a team of advisors who can develop a Personalised Tagging Plan for you. Please don't hesitate to submit your questions to us via the "Support centre".
www.atinternet.com/support
© AT Internet - 2016 - All rights reserved