...
Choose a conversion target for which you want to create a conversion code for. Conversion targets usually designate an event type such as ‘sale’ or ‘appinstall.’ This conversion target should obviously correspond with the conversion of the confirmation page you want to integrate the code on. In case you work with multiple conversion targets, make sure the parameter is filled with the correct value from data layer. Conversion targets should be set up before implementing the conversion code.
Working with conversion targetsSelect a tracking category for the conversion code you are implementing. Tracking categories usually designate the commercial category of a conversion.
If you are implementing a conversion code that should enable basket tracking, make sure you select ‘basket’. In case you work with multiple tracking categories, make sure the parameter is filled with the correct value from data layer. Tracking categories should be set up before implementing the tracking code.
Tracking categoriesDefine whether you want the third party tracking codes in the container if the tracking codes to load synchronous or asynchronous. When you select synchronous loading, the codes implemented in the container will be loaded as soon as the browser reaches the position of the tracking code in the source code of the page. When you select asynchronous loading, the codes implemented in the container will be loaded as soon as the browser has loaded the complete page. Asynchronous loading is highly recommended, although it requires you to make sure all third party tracking codes implemented in the container of the conversion code are asynchronous as well.
After you have selected a conversion target and the tracking category, you will need to fill in a brief description of the page you want to implement the tracking code on. Make sure the description explains the event on the confirmation page unambiguously. We recommend that it is only one word, such as “checkout.”
In case of session tracking/ working with the click ID: Make sure the click ID is transmitted with every ad media click to the corresponding target URLs. It should be transmitted as additional parameter. We recommend working with the click ID, since it allows tracking when no cookie is available. For more details read more here: Working with the clickId
...
Name (JS code) | Name (img code) | Explanation | Format | Example |
|---|---|---|---|---|
convTarget | ctg | This parameter identifies the conversion target. The value of the parameter corresponds with the target you selected in the configuration panel. | Alphanumeric | AddBasket |
trcCat | trc | This parameter identifies the tracking category. The value of the parameter corresponds with the category you selected in the configuration panel. Tracking category 'default' will be used implicitely when none or unknown tracking category is supplied. In case of basket tracking the value “basket” should be used. | Alphanumeric | default |
siteId | sid | For security reasons, this parameter identifies the page on which the conversion is made. | Alphanumeric | checkout_page |
convId | cid | This parameter identifies the the conversion and therefore should be unique. In case the ID contains sensitive information such as an email address, it can be replaced by an alternative ID on the platform. | Alphanumeric | ORD12345 |
ordValue | orv | This parameter transmits the value of the conversion. If the conversion does not contain a value, the transmitted value should be '0.00'. | Numeric: #.# | 25.00 |
ordCurr | orc | This parameter transmits the currency following ISO 4217. The currency should always correspond with the currency used on the advertiser's website. | Alphabetic | EUR |
locationHref | hrf | The complete Browser-URL on which the tag was fired. Used to prevent accuracy issues in case of strict referrer browser policy. Please don’t change the default value | URL | Result of |
...