fr | en | es | de

ClickZone®/ScrollView®

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

Contents: ShowHide

All of the information described in this document requires version 4.0.001 or later of the xtcore.js file. This file is available in your interface, from:

• the Configuration zone > XiTi tags > Content tags (version 7.5)

• the Tools button > Tags panel > Specific tags (version NX)

ClickZone® allows you to measure all of the clickable items of a page and the zones displayed by the Internet user. The defined zones are analysed and displayed differently: list and Overlay as well as HeatMap for the click analysis.

Using ClickZone®

You need to use version 4.0.001 or later of the xtcore.js file

Download the JavaScript file xtclicks.js from:

• the Configuration zone > XiTi tags> Action tags > Usability (version 7.5).

• the Tools button > Tags panel > Specific tags, ClickZone®/ScrollView® (version NX)

Place this file as low as possible in the source code of the page to be measured. This call must be placed just before the call of the xtcore.js file and after the declaration of the standard variables.

• xtimod: if the audited page is part of a template previously declared in the Configuration zone > ClickZone® > Templates (version 7.5) or via the Tools button > Configuration panel > Navigation > ClickZone® > Templates (version NX), you must add the xtidmod variable at the bottom of the other standard JavaScript variables and enter the ID that was given whenever you declared the template.

• xtergo: a call to the xtclicks.js file is all that is required to start the ClickZone® analysis. If you do not wish to have this analysis carried out on all of your pages then you need to enter 0 as the value for the xtergo, this in turn will disable the ClickZone®.

Important

Please contact our Support centre if you would like to use the ClickZone analysis with an earlier version of ClickZone, in other words with a version prior to 4.0.00 : several lines of JavaScript need to be added before the closure of the BODY tag.

Note

After these two steps you can start to take advantage of the HeatMap, Overlay, and Click lists analyses. Here, the analyses only refer to navigation clicks.

In order to obtain download and exit clicks, you just need to open the xtclicks.js file and modify the 1^st line by changing the scriptOnClickZone variable to 2.

Important

Each click which is traced is counted in the global volume making it possible to determine the billing period. If you only wish to audit the navigation clicks so as to lower this volume of measurement, you just have to edit the xtclicks.js file and modify the first line (changing the “scriptOnClickZone" variable to 1).

The tagging procedure is the same for the ClickZone® , ScrollView® and Zones analyses. You can choose to display the analyses of your choice in your interface, via :

• the Configuration zone > Action tags > Usability (version 7.5).

• the Tools button > Tags panel > Specific tags > ClickZone®/ScrollView® (version NX).

You can decide whether or not to display one or more features by clicking on the xtclicks.js file. You can consider:

• only the ClickZone® measurements

• only the ScrollView® measurements

• only the zones displayed

• both the ClickZone® and ScrollView® measurements

• the ClickZone® measurements and the zones displayed

• the zones displayed and the ScrollView® measurements

• both the ClickZone® and ScrollView® measurements as well as the zones displayed

Renaming items

We recommend that you rename items which are tagged and measured whenever your page contains at least one dynamic item. When you rename the items, you adapt the wordings of the analyses to the needs of the teams that interpret the results.

In order to do so, you must populate the xtclib variable as follows:

Note

In order to name items, you must respect the same rules used for naming web pages: no special characters (or space, quotes, apostrophes, etc). Only the special character “_” can be used to replace the spaces.

This xtclib variable should be included in the tag of the measured item (this is the case for an image) or in the tag which is the closest to the text. In the example above, the tag which is the closest to the "XiTi" text is <a href….>. If you insert a tag such as  <font …> or <b> between both, you must insert xtclib in this tag.

For example:

xtclib has been placed in the tag which is closest to the "XiTi" hyperlink: <b>

For an image, just insert xtclib directly into the tag <img.

For example:

Important

The <p> tag cannot contain the xtclib variable, even if it is the tag which is closest to the clickable text.

Declaring zones

You have the possibility of declaring specific zones within web pages, by declaring a variable named xtcz either in the “div” tags or directly in the tables.

When looking at the results, this allows you to filter your request over specific zones (Granularity option in your click analyses), which gives you a global vision of all of the clicks contained in this zone.

Example via div tags directly in the HTML code:

Which could lead to:

• 1 click of “mylink” (dynamic name)

• 1 click of “myimage” (dynamic name)

• 1 zone including the 2 “zone_level2” clicks

• 1 zone including all of the “zone_level1” clicks

Example via a table:

Which could lead to:

• 1 zone including all of “zone_level1”

• 1 zone of “zone_level2” including these 2 clicks and one zone of “zone_level2_b” including 1 click

• 1 click of “mylink” (dynamic name), 1 click of “myimage (dynamic name) and one click of “link2” (customised name)

Note

The zone levels are automatically determined depending on how the HTML items are interlinked (div or table).
For displayed zones, analyses are only available for the level 1.
Declared zones are similar to clicked or displayed zones. The analyses associated with these zones are based on the "xtcz" attribute.

Grouping zones by type

The types of zones are groups of zones which are displayed on the Internet users’ screen and which allow for more global analyses.

There are several types of predefined zones. You can, however, create your own groups.

The ID, which is either provided or generated must be placed in the xtdztype variable that you insert into your tag at the same level as the variable which contains the zone label.

• Predefined types

You can choose between several predefined types in order to organise your zone types:

• “CZSE” for search engines

• “CZM” for menus

• “CZA” for articles

• “CZF” for forms

• “CZC” for contents

• “CZAD” for advertisements
   

• Add a zone type

If you want to add a specific type of zone to your site, you have to populate a new label:

• In the ClickZone® configuration zone > Zone types (version 7.5)
  - select a site,
  - enter a label and click on Add.

• or via the Tools button > Configuration panel > Navigation&Usability > ClickZone® > Zone types (version NX)
  - select a site
  - click on Add,
  - enter a label and click on Add.

• Retrieve the generated ID, and place it in the xtdztype.

An example of a menu zone that has been grouped together is given below:

Creating templates

When creating templates, you create voluminous measurements of web pages which are structured in the same fashion (product sheet, search result pages, etc.). This means that you get all of the results on the one analysis page.

In order to create a template you need to specify the xtidmod variable in the tag.

Creating a template in the interface 7.5:

• Go to Configuration > ClickZone® > Templates.

• Enter a label for the template.

• Specify the URL address of the page which is to be used as a template.

• Retrieve the generated ID, and then place it in the xtidmod variable.

Creating a template in the interface NX:

• Go to the Tools button > Configuration panel > Navigation&Usability > ClickZone® >Templates.

• Click on Add.

• Enter a label.

• Specify the URL address of the page which is to be used as a template.

• Retrieve the generated ID, and then place it in the xtidmod variable.

You can directly modify the name of the template in the configuration zone.

Specific cases

You already measure clicks with the xt_med() or xt_click() function

In this case, you do not need to delete the calls to the xt_med() or xt_click() function. The two solutions are fully compatible.

If you insert a ClickZone® tag, the xt_med() or xt_click() function is disabled but the properties that you entered are saved (click name, click type ).

Exit clicks between 2 URLs of the same domain

If your account has several websites (xtsite identifier) on a single domain, the ClickZone® code tends to give priority to navigation clicks (same domain) while it deals with exit clicks.

For example:

a click from the page

to the page

is an exit click for the website 100.

Without any action from you, the ClickZone® code will not know that it refers to an exit click (same domain .site.com). As a result, there is no measurement.

Therefore you have the possibility of declaring the type of click via the xtcltype variable (in the same way as the xtclib) by populating:

• “S” for exit.

• “N” for navigation.

• “T” for download.

• “A” for action.

As in the example, the following link is obtained from the page www.site.com/page.html:

Recognition of unclickable items

The objective of this measurement is to find out if some items on a page should be clicked upon or not. You must call the xt_click() function via the OnClick action:

In this example, any click on the image is measured as an action click ('C' and 'A'. The part of the image which cannot be clicked upon is saved.

Using buttons/ads made with Flash

By default, ClickZone® does not measure the Flash items on your page. It deactivates any call to the xt_med() function which allows the click measurement (N, S, T or A) to take place.

If you wish to have a standard measurement of your clicks on Flash items:

• Download the new xtcore.js file (after 22/11/07).

• Replace the value ‘C’ in xt_med() with 'F' as the first variable.

For example, if you use:

You just need to replace it (in the source code of the Flash film) with:

Measuring clicks on Flash animations

There are two methods which can be used to declare a Flash film in your source code.

* Via the “AC_FL_RunContent” JavaScript method

The 'wmode' property must be added as a parameter of the function and fixed at the 'transparent' value.

* Via a direct method known as “<object”

The wmode property must be added to a "<PARAM" tag, as well as to the "<EMBED" tag.

• Declare the type of clicks measured on Flash animations

By default, the measurement of the Flash animation only considers the navigation clicks. The destination URL, which is returned when clicking on a piece of Flash animation, is empty (urldest=""). The type of click is therefore always equal to N (clickcz=”N”).

In order to declare the type of click as a different value, you should use the property "name" of the clicked object.

As an example, let’s look at the two cases previously mentioned:

• "AC_FL_RunContent()" JavaScript method

The property 'name' must be added as a parameter of the function. To be able to specify the type of click, the variable must be structured as follows:

'xtcltype'+ type of click ('N','S', 'T' or 'A')

Important

The value of the identifying attribute will be “Animation e-Commerce”, i.e. the ID of the object in this case. If the object does not have any ID, then the value of the identifying attribute will be its NAME, i.e. "xtcltypeS”. It is better to specify an “ID” and a “NAME” for the object at the same time if you wish to declare the type.
When objects are structured like this, certain “ClickZone® " attributes such as “xtclib” or "xtcltype" (which is not appropriate in all cases) can not be used directly.

• Direct method "<object"

The "name" property must be added to the "<OBJECT" tag, as well as to the "<EMBED" tag.

Measuring your site asynchronously

It is possible to tag your site with ClickZone® whenever you measure your site with the asynchronous tag. Tagging your site asynchronously will help avoid issues which slow down a page's loading time. A page's loading time is optimised by forcing a script to be loaded at the same time as the page is loaded. The asynchronous tag and ClickZone® are compatible with one another with version 4.0.001 and later of the xtcore.js file.

Please find a template of the asynchronous tag code below:

Should you require any further information on how to implement the asynchronous tag, please refer to the following section of the Help centre: Implementation and tagging  > Analyzer NX > Specific cases > Asynchronous tag.

www.atinternet.com/support
© AT Internet - 2016 - All rights reserved