
Integrating the pixel-code
This section describes how the pixel-code is integrated in your website. How the pixel-code is integrated depends on whether your website uses Flash or not. If the current version of the pixel-code is used (which is recommended), the following instructions are to be observed:
- Simple installation for non-Flash-based websites,
- Advanced installation for non-Flash-based websites, und
- Installation for Flash-based websites
The following points cover further integration options:
The corresponding pixel-code is available for downloading in the Configuration menu under Pixel-Code. The pixel-code is normally delivered invisibly by the server. It is however also possible to have the pixel-code displayed as a counter. For more information about this, click here:
Descriptions for the usage of the “Campaign and Milestone Tracking” and “E-Commerce/Shopping Cart Tracking” can be found at the following sections:
The pixel-code can also be easily integrated into widely distributed services, including
In the following, alongside installation instructions for Flash and non-Flash-based web pages, there is also an instruction for tracking PDF documents.
If the website uses different technologies, the relevant instructions and associated code must be used in each case.
| Example: |
|---|
| The website is made up of HTML and Flash elements and both parts have to be analysed. This means the pixel-code for Flash has to be integrated into the Flash elements of the website, and the HTML pixel-code into the corresponding HTML elements, as described in the respective instructions. |
Before the pixel-code is integrated into the pages, you should think about what should later be measured and analysed, which specific areas of the website you will want to analyse later on, and what convention you want to use for allocating names, provided the names are to be set manually for the selected pages. The naming convention should be clear and meaningful, as the names will appear in the statistical analysis. When allocating names, you can assign names for two identifiers, 'wm_page_name' and 'wm_group_name'. Where these identifiers are not set manually, the identifiers will be determined automatically from the URL of the accessed page.
If the identifier wm_page_name is set manually, this should contain information about the page on which you currently are (e.g. 'index.html'). If required, customer, country and language can also be added. The name may not contain empty spaces and must be separated by '|'.
| Example of 'wm_page_name': |
|---|
| Customer|DE|de|index.html |
It is not crucial that wm_page_name consists of page names (for instance 'index.html'). 'Index' or something else is equally possible.
If the identifier wm_group_name is set manually, it should contain information about the area in which you are currently located (for example, service). Customer, country and language can also be added, if required. The name may not contain empty spaces and must be separated by '/'.
| Example of 'wm_group_name': |
|---|
| Customer/DE/de/Service |
The allocated names should not start or end with '|' or '/' and the pages and group names should not have the same name and they should be uniquely identifiable.
The names also have to be HTML-compatible. Exactly what this means is described below.
HTML compatibility is particularly important when using special characters specific to a particular language. Here the character set (character encoding) used must be correctly configured for the HTML page. HTML compatibility also has to be taken into account when integrating page and group names into the pixel-code. In the JavaScript section (and therefore also for the PDF downloads) this is already assured by using the JavaScript function 'escape()'.
When inserting the page and group names (wm_page_name and wm_group_name) in the <noscript>...</noscript> section, the names have to be URI-coded. This means that all special characters have to be given in URI syntax.
| Example of a page name: |
|---|
Page name: KUNDE|DE|de|Home|Lichttechnische Grundgröße URI-coded: KUNDE%7CDE%7Cde%7CLichttechnische+Grundgr%F6%DFe |
Empty spaces have to converted (into a plus sign (+)). The following table contains several important characters and their related URI code:
| Original: | URI-coded: |
|---|---|
| blankspace | + |
| + | %2B |
| % | %25 |
| & | %26 |
| ? | %3F |
| ; | %3B |
| Ä | %C4 |
| Ö | %D6 |
| Ü | %DC |
| ä | %E4 |
| ö | %F6 |
| ü | %FC |
| ä | %E4 |
| ß | %DF |
| | | %7C |
| / | %2F |
Page and group names are case-sensitive.
