• Products
• Product-Demo
• Registration
• Features
• Links

• Home > 
• Features > 
• The Pixel-Code

The Pixel-Code

1 The Pixel-Code

Information about the visitors is collected with a so-called pixel-code. A pixel-code is a 1x1-pixel transparent graphic that is integrated, completely invisible, on the website. As soon as the user visits the website, the pixel-code is loaded automatically. This information is analysed by us and expressed as statistics.

This method has decisive benefits compared with other analyses that depend on server-based data. Using the pixel-code method, data is captured via the user's browser, which gives a significantly more accurate picture of the visitor. In this way, it is possible to analyse clickpaths, establish whether these are returning visitors, monitor actions within an application and much more. This data is saved in an SQL database and can be used later for any form of analysis.
The pixel-code is specific to each website. It delivers information about visitor behaviour relative to a particular website. In other words, the tracking code (the individual 'pixel-code') is intended for a specific website. If you are operating several websites, the pixel-code must always be adjusted accordingly, as otherwise incorrect results may be obtained. Of course, it may be that you want to analyse several different websites using the same pixel-code. In this case, you have to make sure that the pixel-code is handled as one website in the statistics.

1.1 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 pixelcode 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
• Installation for Flash-based websites

The following points cover further integration options:

•  PDF documents
• Content management systems

The corresponding pixel-code is available for downloading in the Configuration menu under Pixel-Code.
The pixel-code can also be easily integrated into widely distributed services, including

• PayPal, or
• Ebay

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.

 
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 '|'.

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 '/'.

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.

URI-codiert: KUNDE%7CDE%7Cde%7CLichttechnische+Grundgr%F6%DFe

Example of a group name:
Gruppenname: KUNDE/DE/de/Home/Service Leistungen
URI-codiert: KUNDE%2FDE%2Fde%2FService+Leistungen

Empty spaces have to converted (into a plus sign (+)). The following table contains several important characters and their related URI code:

Page and group names are case-sensitive.

1.2 Configuring the pixel-code

All the parameters of the pixel-code are described in this section. The code can vary depending on the website’s underlying technology; the parameters, however, are the same. Examples that show the complete code can be found in the installation instructions or in the downloadable code under 'Configuration – Pixel-Code'. The following details are given for your information. They are not required for a simple installation.

1.2.1 Extending functionality through parameters

The following parameters can be added to extend functionality (you will find more detailed information on how to do this under 'Campaigns' and 'E-Commerce'):

1.3    Simple installation for non-Flash-based websites

The following simple steps for installing the pixel-code are required to integrate the pixel-code into a non-Flash-based website without manually allocating page and group names.

1. Copy the pixel-code under 'Configuration – Pixel-Code – Description'.
2. Insert the copied pixel-code into the HTML code between the two body tags (<BODY> </BODY>) of the website. The best position is the line directly in front of the closing body tag (</BODY>).
3. If the website transmits data via an encrypted connection (SSL), the pixel-code will need to be
   adjusted by replacing the 'http' after '<img src=' with 'https' in the <noscript> part of the pixelcode.

These steps should be repeated for all pages that are to be included in the analysis.
The following is a basic example of how a simple integration of the pixel-code might appear:

<BODY>
....further HTML-Code....
....
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 START -->
<script type="text/javascript" src="http://ctsde01.wiredminds.de/track/count.js"></script>
<script type="text/javascript"><!--
wm_custnum="1";
// Begin own parameters.
// End own parameters.
wiredminds.count();
// -->
</script>
<noscript>
<div>
<a target="_blank" HREF="http://www.wiredminds.de"><img src="http://ctsde01.wiredminds.de/track/ctin.php?custnum=1&nojs=1"
 alt="WiredMinds eMetrics tracking with Enterprise Edition" border="0"></a>
</div>
</noscript>
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 END -->    
</BODY>

1.4    Advanced installation for non-Flash-based websites

To integrate the pixel-code into a non-Flash-based website with manual allocation of page and group names, the following simple steps are required to install the pixel-code.

1. Copy the pixel-code under 'Configuration – Pixel-Code – Description'.
2. Insert the copied pixel-code into the HTML code between the two body tags (<BODY> </BODY>) of the website. The best position is the line directly in front of the closing body tag (</BODY>).
3. Insert the parameters (wm_page_name and wm_group_name) between the lines '// Begin own parameters' and '// End own parameters'. The content of the parameters wm_page_name and wm_group_name is completed, as described above in 'Integrating the pixel-code'.
   Now the parameters (wm_page_name and wm_group_name) have to be inserted and set in the <noscript> part of the pixel-code. To do this, both parameters have to be appended to the URL of the pixel-code (see highlighted parts of the sample code below). Important: The values for the parameters in the <noscript> part have to be URI-coded! You will find a description on this in 'Integrating the pixel-code'.
4. If the website transmits data via an encrypted connection (SSL), the pixel-code will need to be adjusted by replacing the 'http' after '<img src=' with 'https' in the <noscript> part of the pixelcode.

These steps should be repeated for all pages that are to be included in the analysis.

The pixel-code can also be modified for Campaign and Milestone Tracking and ECommerce/Shopping Cart Tracking. You will find detailed information on this at 'Configuring campaign and milestone tracking' and 'Configuring e-commerce/shopping cart tracking'.

The parameters have been inserted in the following example and filled with placeholder designations. The highlighted areas have to be modified and the placeholders replaced with your own designations.

<BODY>
....further HTML-Code....
....
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 START -->
<script type="text/javascript" 
src="http://ctsde01.wiredminds.de/track/count.js"></script>
<script type="text/javascript"><!--
wm_custnum="1";
// Begin own parameters.
wm_page_name="MY_PAGE_NAME";
wm_group_name="MY_GROUP_NAME";
// End own parameters.
wiredminds.count();
// -->
</script>
<noscript>
<div>
<a target="_blank" HREF="http://www.wiredminds.de"><img src="http://ctsde01.wiredminds.de/track/ctin.php?custnum=
1&nojs=1&wm_page_name=MY_PAGE_NAME&wm_group_
name=MY_GROUP_NAME"
 alt="WiredMinds eMetrics tracking with Enterprise Edition" border="0"></a>
</div>
</noscript>
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 END -->
</BODY>

In the following sample code, the above placeholders have been replaced with examples. The code in a website might appear very similar.

<BODY>
....further HTML-Code....
....
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 START -->
<script type="text/javascript" 
src="http://ctsde01.wiredminds.de/track/count.js"></script>
<script type="text/javascript">
<!--wm_custnum="1";
// Begin own parameters.
wm_page_name="KUNDE|DE|de|index.html";
wm_group_name="KUNDE/DE/de/Startbereich";
// End own parameters.
wiredminds.count();
// -->
</script>
<noscript>
<div>
<a target="_blank" HREF="http://www.wiredminds.de">
<img src="http://ctsde01.wiredminds.de/track/ctin.php?
custnum=1&nojs=1&wm_page_name=
KUNDE%7CDE%7Cde%7Cindex.html&wm_group_name=KUNDE%2FDE%
2Fde%2FStartbereich"alt="WiredMinds eMetrics tracking 
with Enterprise Edition" border="0"></a>
</div>
</noscript>
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 END -->
</BODY>

1.5    Installation for Flash-based websites

To integrate the pixel-code into a Flash-based website, the following installation steps are necessary.

1. Copy the pixel-code under 'Configuration – Pixel-Code – Description'.
2. Insert the copied pixel-code into the HTML code between the two body tags (<BODY> </BODY>) in the website that also contains the Flash application. The best position is the line above the Flash application. If page and group names are to be set manually for the website, further information can be found in 'Advanced installation for non-Flash-based websites'.
3. In the next step, the global function 'wm_track' has to be inserted into the Flash animation. This code can be found under option 2 in 'Configuration – Pixel-Code – Flash'.
   These steps will have to be repeated for each Flash application to be tracked.
4. The function now needs to be accessed at each point where a visitor should be tracked (for instance, a button). The placeholders highlighted in the following example are to be replaced, as described above in 'Integrating the pixel-code' for wm_page_name and wm_group_name.

on (release) {
    _global.wm_track("PAGE_NAME", "GROUP_NAME");
    ...further actions...
}

The following is a basic example of how the pixel-code might appear in the Flash application.

_global.wm_track = function(page_name, group_name) {
    custnum = "1";
version = "3.0";
    click_url="&custnum="+custnum;
    click_url+="&version="+version;
    click_url+="&pagename="+page_name;
    click_url+="&group="+group_name;
    click_url+="&flver="+getVersion();
    if (_global.wm_last_referrer != undefined) {
        click_url+="&referrer="+_global.wm_last_referrer;
    {
    getURL("javascript:wiredminds.count_flash('"+click_url+"&t="+getTimer()+"')");
    _global.wm_last_referrer = page_name;
}

This is how accessing the global function within a Flash application might appear (the highlighted placeholders are to be replaced as described above in 'Integrating the pixel-code' for wm_page_name and wm_group_name).

on (release) {
_global.wm_track('page_name', 'group_name');
...further actions...
}

1.6 Tracking of PayPal

How the pixel-code is integrated into PayPal is explained in the following.

PayPal offers various options with which you can use their pay service. Brief descriptions can be found here on how these can be set up so that milestone and e-commerce tracking can be used.
To use milestone and e-commerce tracking in conjunction with 'PayPal', you can proceed as described in 'Integrating the pixel-code', 'Configuring campaign and milestone tracking' and 'Configuring e-commerce/shopping cart tracking'. Care should be taken, however, that correct content is defined for the variables in the pixel-code on the pages that open automatically after aborting or successfully carrying out payment. This would be possible as follows with ecommerce tracking:

The 'wm_sales' and/or 'wm_basket' parameters have to be configured correctly (see Configuring e-commerce/shopping cart tracking). One option would be to transfer the content of the page that is displayed if payment has been  completed successfully (e.g. in the GET list of the URL).

If campaign and milestone tracking is to be used, e.g. to track whether the order has been completed successfully or whether the user has aborted it during the payment transaction via PayPal, the 'wm_milestone' parameter has to be configured correctly (see Configuring campaign and milestone tracking). It would also be possible to transfer the content of this parameter via the GET list in the URL for the pages that are displayed for a successfully completed or aborted payment transaction.

In the following there is a brief description of the individual payment options offered by PayPal, and where to configure pages that open when the payment transaction has been completed successfully or cancelled.

Express Checkout
If Express Checkout is used as a payment method, the 'ReturnURL' and 'CancelURL' parameters of the SetExpressCheckout method (method of the PayPal-API) have to be configured correctly. The 'ReturnURL' parameter contains the URL of the page that is to be displayed if the payment transaction has been completed successfully. The 'CancelURL' parameter contains the URL of the page that is to be displayed if the payment transaction has been cancelled.
These parameters are transferred using the 'SetExpressCheckout' method and are also defined there.

Detailed information on how to configure this payment method can be found on the following page of PayPal:
https://www.paypal.com/us/cgi-bin/webscr?cmd=xpt/Merchant/merchant/
ExpressCheckoutTechView-outside

Solution A: Existing shopping cart
Solution A: Existing shopping cart
Using this method, either the complete value of the order (excluding individual items) or each individual item is transferred to PayPal. Regardless of which method is used, the 'return' and 'cancel_return' parameters have to be set to ensure tracking functions correctly. The 'return' variable specifies the page to which the user is directed after a correct payment. The 'cancel_return' variable specifies the page to which the user is directed if payment has not been carried out correctly.

Detailed information on how to configure this payment method can be found on the following page of PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=xpt/cps/merchant/
SellerHubShopSolutionsA-outside

Solution B: No shopping cart available (PayPal shopping cart)
If the items are paid for via the PayPal shopping cart, the following settings have to be made when configuring the shopping cart.
Clicking 'Weitere Optionen hinzufügen' [Add further options] brings up further settings, also for 'Geben Sie eine Folgeseite an' [Specify a following page].
Here you can specify the page to which the user is directed if payment is completed successfully or aborted. Under 'Erfolgreiche Zahlungs-URL' [Successful payment URL] you have to specify the page to which the user is directed if payment is completed successfully. Under 'Zahlungsstornierungs-URL' [Payment cancellation URL], you specify the page to which the user is led if the payment transaction has been aborted.

Detailed information on how to configure this payment method can be found on the following page of PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=xpt/cps/merchant/
SellerHubShopSolutionsB-outside

Solution C: Single item sale/donations
For single item sales or donations (and hence the corresponding buttons in PayPal), the following settings have to be made when creating these buttons.
Clicking 'Weitere Optionen hinzufügen' [Add further options] brings up further settings, also for 'Geben Sie eine Folgeseite an' [Specify a following page].
Here you can specify the page to which the user is directed if payment is completed successfully or aborted. Under ”Erfolgreiche Zahlungs-URL' [Successful payment URL] you have to specify the page to which the user is directed if payment is completed successfully. Under 'Zahlungsstornierungs-URL' [Payment cancellation URL], you specify the page to which the user is led if the payment transaction has been aborted.

Detailed information on how to configure this payment method can be found on the following page of PayPal:
https://www.paypal.com/cgi-bin/webscr?cmd=xpt/cps/merchant/
SellerHubShopSolutionsCoutside

You will find a list of the payment options offered by PayPal here:
https://www.paypal.com/cgi-bin/webscr?cmd=_merchant-outside

1.7    Tracking eBay transactions

To integrate the pixel-code in eBay, the code under 'Configuration – Pixel-Code – Description' will have to be copied. Where JavaScript is not permitted, only the code that lies between the two <noscript> tags has to be copied (only the code in between, without the <noscript> tags).
This copied code now has to be inserted into the description of the item up for sale. 'HTML' has to be selected for the description. The wm_page_name and wm_group_name parameters still have to be configured and appended to the URL. For this, see the description in Integrating the pixel-code, section 'Advanced installation for non-Flash-based websites').
The fact that JavaScript and other script languages are not permitted – or are permitted only under certain conditions – means that only a limited analysis is possible. Although you can execute JavaScript when you are 'ID Verified' by eBay, the conditions for use nevertheless prohibit sending information to external parties. If, however, the code does have to be inserted with JavaScript elements, the code must be configured as described in Integrating the  pixel-code.
The configured code is then integrated into the HTML part of the description, as described in this section.
The conditions for use with respect to script languages can be referenced at the following address:
pages.ebay.de/help/sell/skriptsprachen_hilfe.html

Tracking can of course also be used with eBay online shops. The tracking of campaigns and milestones and e-commerce tracking are of particular interest here. For information on configuring tracking options, see 'Configuring campaign and milestone tracking' and 'Configuring e-commerce/shopping cart tracking'.

1.8   Integrating the pixel-code in content management systems

This section describes the procedure for integrating a pixel code in a content management system such as Typo3 or Continedo.

1.8.1    Typo3

If you create your web pages with Typo3, follow these steps to install the pixel-code:

1. Copy the pixel code under 'Configuration – Pixel-Code – Description'. If the website transmits data via an encrypted connection (SSL), the pixel-code will need to be adjusted by replacing the 'http' after ' part of the pixel-code. <noscript>-Teil des Zählpixelcodes das „http“ nach "
2. Two parameters for the page and group names have to be inserted in the copied pixel-code. These parameters are 'wm_page_name' and 'wm_group_name' and have to be inserted between the lines '// Begin own parameters' and '// End own parameters' and in the <noscript> part of the pixel-code. For more detailed instructions, see Advanced installation for non-Flashbased websites'.
You now have to prepare these parameters for Typo3. For wm_page_name, specify ###TRACK_PAGE###.
For wm_group_name, specify ###TRACK_GROUP###.
Of course, you can use your own marker names if you like.
The pixel-code can then be integrated into the template. The ideal position is the line in front of the closing body tag (</BODY>).
In the following sample code, positions are highlighted where these parameters have to be inserted.

<BODY>
....further HTML-Code....
....
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 START -->
<script type="text/javascript" src="http://ctsde01.wiredminds.de/track/
count.js"></script>
<script type="text/javascript"><!--
wm_custnum="1";
// Begin own parameters.
wm_page_name="###TRACK_PAGE###";
wm_group_name="###TRACK_GROUP###";
// End own parameters.
wiredminds.count();
// -->
</script>
<noscript>
<div>
<a target="_blank" HREF="http://www.wiredminds.de"><img src="http://ctsde01.wiredminds.de/track/ctin.php?custnum=1&nojs=
1&wm_page_name=###TR
TRACK_PAGE###&wm_group_name=###TRACK_GROUP###"
 alt="WiredMinds eMetrics tracking with Enterprise Edition" border="0"></a>
</div>
</noscript>
<!-- WiredMinds eMetrics tracking with Enterprise Edition V5.0 END -->
</BODY>

3. The markers now have to be filled with content. Open the Setup part of the TypoScript template.
Insert the following into the PAGE definition at the point of the marker definitions.

marks {
   # Titel der aktuellen Seite auslesen
   TRACK_PAGE = TEXT
   TRACK_PAGE.value = page:title

   # Ein Rootline Menu erstellen das eine Bereichsanalyse ermöglicht
   TRACK_GROUP = COA
   TRACK_GROUP{
     10 = HMENU
     10{
       special = rootline
       special.range = 0|-1
       1 = TMENU
       1{
         NO = 1
         NO{
           linkWrap = |/
           doNotLinkIt = 1
         }
         CUR = 1
         CUR{
           linkWrap = |
           doNotLinkIt = 1
         }
       }
     }
     required = 1
   }
}

4. TRACK_PAGE returns the title of the web page as shown in the browser bar, for example.
TRACK_GROUP generates a rootline menu. The page levels are separated by a '/'. This '/' is important so that the page tree can be reconstructed for the analysis. In this way, areas of the tracked page can be selected for separate analysis.

1.8.2    Contenido

The following description explains how the pixel-code can be used with Contenido:

You can load the module and language file from the following link:
www.f-be.de/contenido-forum/hottracker_pixelzaehler.zip

Using this module you can integrate the pixel-code into your page (in the last container, if possible). Additionally, the PHP script (found under Configuration – Pixel-Code – PHP) has to be saved in the Include directory.
In the back end, you can configure whether the counter is active, determine the page and group names and specify whether an SSL connection will be used.
The module selects the current page title and the category name. These values can, however, be overwritten.

Input:
    /****************************************** 
    * File      :   Pixelzähler Input 
    * Project   :   Contenido 
    * Descr     :    
    * 
    * Author    :   Florian Behrendt 
    * modified  : 
    * Created   :   15.03.2006 
    * Modified  :    
    * 
    * Version   :   1.0 
    * © GPL ? 
    *****************************************/ 
    
// Bestimme Namen des Artikels und Name der Kategorie 
    $query = "SELECT ART.idartlang, ART.title, CAT.name FROM ". 
                $cfg["tab"]["art_lang"]." AS ART, ". 
                $cfg["tab"]["cat_lang"]." AS CAT, ". 
                $cfg["tab"]["cat_art"]." AS C ". 
                "WHERE ART.idartlang = $idartlang ". 
                "AND ART.idart = C.idart ". 
                "AND C.idcat = CAT.idcat "; 
    
                
    
    // execute query 
    $db->query($query); 
    $db->next_record(); 
    $arttitle = $db->f("title"); 
    $catname =$db->f("name"); 

/*  Eingabefelder: Seite zählen / Seitenname / Gruppenname / und SSL 
    Wenn die Felder leer sind, dann werden Seitenname und Kategoriename vorgeschlagen */ 

    echo ("<input type=\"checkbox\" name=\"CMS_VAR[1]\" value=\"checked\"CMS_VALUE[1]>".mi18n("count Page")."
" ); 

    if ("CMS_VALUE[2]" == "") { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[2]\" value=\"$arttitle\">".mi18n("Pagename").":CMS_VALUE[2]
") ; 
        } 
    else { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[2]\" value=\"CMS_VALUE[2]\">".mi18n("Pagename").":CMS_VALUE[2]
") ; 
        } 
    if ("CMS_VALUE[3]" == "") { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[3]\" value=\"$catname\">".mi18n("groupname").":CMS_VALUE[3]
") ; 
        } 
    else { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[3]\" value=\"CMS_VALUE[3]\">".mi18n("groupname").":CMS_VALUE[3]
") ; 
        } 
    echo ("<input type=\"checkbox\" name=\"CMS_VAR[4]\" value=\"true\"CMS_VALUE[4]>".mi18n("SSL ")."true
") ; 
value=\"$arttitle\">".mi18n("Pagename").":CMS_VALUE[2]
") ; 
        } 
    else { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[2]\" value=\"CMS_VALUE[2]\">".mi18n("Pagename").":CMS_VALUE[2]
") ; 
        } 
    if ("CMS_VALUE[3]" == "") { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[3]\" value=\"$catname\">".mi18n("groupname").":CMS_VALUE[3]
") ; 
        } 
    else { 
        echo ("<input type=\"Text\" name=\"CMS_VAR[3]\" value=\"CMS_VALUE[3]\">".mi18n("groupname").":CMS_VALUE[3]
") ; 
        } 
    echo ("<input type=\"checkbox\" name=\"CMS_VAR[4]\" value=\"true\"CMS_VALUE[4]>".mi18n("SSL ")."true
") ;

<?php 
/****************************************** 
* File      :   Pixelzähler Output 
* Project   :   Contenido 
* Descr     :    
* 
* Author    :   Florian Behrendt 
* modified  : 
* Created   :   15.03.2006 
* Modified  :    
* 
* Version   :   1.0 
* © GPL ? 
*****************************************/ 


// Ausgabe darf nicht im Edit Mode erfolgen, weil sonst Seite nicht bearbeitet werden kann. 
if($edit ==""){ 
    // Abfrage ob Seite mit gezählt wird.  
    if (CMS_VALUE[1] == "checked" ){        
        cInclude('includes', 'click_track_inc.php'); //Pixelzähler
        if ("CMS_VALUE[4]" == "checked") // SSL 
            {  
            $ssl = true; 
            }            
        else 
            {$ssl= false ;} 
    if ("CMS_VALUE[1]" == "checked") { 
echo click_track("CMS_VALUE[2]","CMS_VALUE[3]", $ssl);
    } 
} 
} 

?>

Source: contenido.org/forum/viewtopic.php

1.9  Tracking PDF documents

Carry out the following steps to track PDF documents:

1. The pixel-code has to be integrated, as described in 'Integrating the pixel-code', in the website where the link to the PDF document is located.
2. The following 'onClick' event must be added to the PDF document link:
   
   
   <table class="codetable"><tbody><tr><th>'onClick'-Event-Code:</th></tr><tr><td>

    onClick='wiredminds.count('file.pdf')

   </td></tr></tbody></table>
   This should be inserted in the link as shown: <table class="codetable"><tbody><tr><th>"onClick"-Event in einem Link:</th></tr><tr><td>
   </td></tr></tbody></table> 'Linkname' stands for the name of the link. This can also refer to a graphic.
   
   
   The placeholders highlighted above are replaced by examples in the following sample code. This is how the code might appear:
   
   
   <table style="width: 474px; height: 57px;" class="codetable"><tbody><tr><th>Sample Code</th></tr><tr><td>

    <a href="/pfad/zum/pdf/dokument.pdf" onClick="count

   ('dokument.pdf')">Ein Dokument</a> 

   </td></tr></tbody></table>
3. Steps 1 and 2 are to be repeated for each PDF document you want to include in the analysis.
   
   Please note: One common mistake is to specify the hierarchy (page name, such as CUSTOMER/DE/de) in front of the name of the file. This does not have to be set manually here, but will automatically be placed in front of the document name by the pixel-code.