fr | en | es | de

Mobile sites

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

Contents: ShowHide

Several methods can be used to measure the audience and the performance of your mobile sites and applications. There are different elements which are available to meet your needs:

• a standard tag (2 implementation methods can be used)
• specific tags (clicks, internal search engine, forms, etc)
• a procedure which can be used to track mobile applications (iPhone)

Mobile sites

The standard tag

The tag code for mobile sites is a transparent image. It does not use JavaScript code since this type of code does not work on the majority of mobile devices.

Downloading this image whenever any of your pages are opened will send a hit which will be counted as a page view.

The tag code is as follows:

This code must be inserted in the pages of your mobile site.

*Step 1: create/add a mobile site

All you need to do is to add a mobile site to your contract.

You can make a request for a mobile site to be added by going to:

• Configuration > Support centre > Add a site (version 7.5)
• Tools > Tags (version NX).

*Step 2: retrieve the tag for your site

Once your site has been added, you need to go to:

•  Configuration zone > XiTi tags > Content tags (version 7.5)
•  Tools > Tags (version NX).

Then select the mobile site.

*Step 3: enter the standard parameters

s: your site ID: all of the pages which are tagged with this ID will be attributed to your site.

p: provides a page description: you can find the pages in your analyses. Only the characters a-z, A-Z and 0-9 are allowed. underscores (_), fullstops (.) and slashes (/) can also be used.

This variable can also be used to define chapters. The different chapter levels are separated by using ::.

For example:

places the page "hotel_name" in the sub-chapter "France", which in turn is stored in the chapter "hotel".

You can create up to three levels of chapters.

idclient: used to recognise users during a visit. We recommend that you retrieve this variable. If this variable is not populated, you may get a result in which the number of visits is equal to the number of page views.

The idclient may be present in the form of a 12-character alphanumeric code which is retrieved in the HTTP header.

For example:

We suggest that the following code be used (in PHP and for an i-Mode site):

Note

You can try to use the m user alias. This is a unique ID which combines phone number, phone model and phone operator. It has an unlimited life span as long as the person does not change the phone number, the model or the operator. The alias is easy to find in Gallery,. but as is the case for the other sites you need to contact the operator.

• na: used to retrieve a random number. This is used to avoid cache effects and make sure that page reloads are counted correctly.
• ref: the tag code cannot dynamically collect the incoming site referrer (due to the absence of JavaScript). This variable therefore needs to be retrieved manually.

We suggest that the following code be used:

Specific tags

As is the case with a standard website, you can use specific tags (clicks, internal engines, ROI, site custom variables, identified visitors, geolocation etc,) with mobile sites. They can be used to collect specific information depending on the type of site you are measuring.

In order to do this, you must concatenate the specific parameters to the standard tag.

Important

Please consult the general tagging guide for further information on the different tags.

Examples of variable structures

Clicks:

clic= takes one of the following values: S, N, T or A. These values depend on the type of click measured (S = exit; N = navigation; T = download; A = action)

Internal search engine:

mc=: keyword typed into the internal engine

np=: number of the result page

ROI:

roimt=: total value of the order

cmd=: order number

Your page must be previously declared as a "Main goal" so that the a measurement can be taken.

Site custom variables:

Identified visitors:

an=: an ID which you will have retrieved once your visitor has been identified

ac=: visitor category (to be declared in your interface)

Note

These different IDs do not need to be inserted on all pages. Whenever a particular ID is encountered, it is associated with all pages of the visit.

Geolocation:

idpays= country's ISO code, made up of 2 letters (e.g. fr)

idprov= predefined numeric ID provided by AT Internet

If no variable is populated, geolocation is then based on the IP address.

Note

Please contact the AT Internet Support centre for further information on how to tag mobile sites.

Specific case: source tags (campaigns)

In this section, we will deal with the tagging of marketing sources, including:

• Email campaigns
• Sponsored links
• Ads
• Affiliations
• RSS feeds

Method 1: dynamic language

Unlike classic websites, placing an "xtor" variable in the URL is not sufficient enough to populate the source campaign, because there is no JavaScript available to collect the variable and place it in the code.

An additional stage is therefore required which involves server-side code. You must collect the "xtor" variable so that it can be placed in an "xto" variable in the code.

Below is an example of a campaign URL which redirects traffic to the home page with an xtor value:

In this example we see the ASP server-side code which is used to extract the xtor value:

(collects the value of the xtor variable in the URL and places it in the xto variable of the tag code).

An example of the tag code:

Method 2: redirection

If you are unable to use server-side code as described above, or if you cannot add variables into your URL, you can use the redirection method.

This involves replacing the destination URL:

with a URL that collects the data before redirecting the user:

• the go.url parameter ensures that redirection takes place
• xts contains your site ID
• xtor must contain the appropriate labels for A, B, C, etc.
• url must contain the URL which the redirect sends traffic to (a URL which must begin with http://)

Mobile sites on SmartPhones

For mobile sites on SmartPhones, the code which is to be used is exactly the same as the one used for classic web sites (refer to previous paragraphs).

You need to declare the JavaScript variables and call the standard xtcore.js file for the complete version. Should you not want to increase the weight of your mobile pages a lighter version exists on the NX, in which no call to the xtcore.js file is made.

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