| Table of Contents |
|---|
...
Basis for all data collection and analysis is the implementation of a conversion tracking code tag on the confirmation page that is displayed after completion of the sale.
in a nutshell
conversion tracking connects clicks and sales, that were registered via a tracking codetag.
Click out: Additional Parameters
...
The click id is transmitted with every click to the shop as get-parameter in the URL. The shop fetches and saves this click id and then returns it to the tracking system, when the conversion tracking code tag is executed.
Usually, Ingenious adds a click id automatically to every (bounce) tracking link. The name of the Ingenious click id is ICLID. It looks like this (example)
...
1. set up the click id as additional parameter: First, create the click id parameter that will be added to the target URL e.g. clicklid=#{ICLID}. This is done in the system under Manage Advertisers > Advertiser Tracking
read on
A detailed guide to additional parameters can be found here:
...
Fetching the click id on the confirmation page in order to include it in the conversion tracking codetag.
Example code fetch click id from cookie with PHP
...
Conversion targets as well as tracking categories should be registered to the system, before they are transmitted via an implemented conversion tracking codetag. Set up is done in the system under Manage Advertisers.
Conversion target: Defines an event and its type, for example Sale, Appinstall, Newslettersignup.
Tracking Category: Defines the commercial dimension, for instance according to the margin of a product group, for example a product group (“Flight”, “Hotel”, “Car Rental”)
read on
A detailed guide on conversion targets and tracking categories can be found here:
Conversion
...
tag
The conversion tracking code tag is implemented on the confirmation page after the sales process (or in case of other events on the corresponding pages). This way a completed sale or event will be measured. Data is transmitted with the help of several variables and parameters, for example order id or basket value.
Types of
...
tags
You will can either get the conversion tracking code by e-mail or you can generate it in tag through the user interface under Manage Advertisers > view tracking code Trail -> Tracking tags.
| Info |
|---|
Please implement your individual conversion tracking |
...
tag that contains your advertiser id and your tracking domain. Please do not use the PHP/JavaScript code of the following examples as it is. |
read on
A detailed guide to generate the conversion tracking code tag can be found here:
JavaScript
We generally recommend the use of JavaScript code when implemented browser side.
The JavaScript Code is very suitable for implementation in JavaScript environments such as tag management systems. Another advantage is that the basket parameter (JSON Object) can be easily included. Also it has additional functionalities like a container functionality.
Example:
...
Image Pixel
For simple tracking events (usually the ones without a basket) the image pixel is well suited. Also, many tracking switches require an image pixel.
...
The S2S callback link is quite similar to the image pixel. To convert an image pixel to a S2S callback URL just change the parameter typ=i to typ=s .
Example:
...
read on
A detailed guide on generation of S2S callback URLs can be found here:
Configuring and implementing tracking codes tags server-to-server (S2S)
Mandatory parameters
Variable (JS) | Variable (img/ s2s) | Example | Description |
|
| sale | Conversion Target. The supplied conversion target needs to be registered in the system. |
|
| default | Tracking Category. The supplied tracking category should be registered in the system and has to be active. 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. |
|
| ORD12345 | Conversion ID/ Order ID: This parameter identifies the conversion and should be unique. In case the ID contains sensitive information such as an email address, it should be hashed. |
|
| 4.98 | Order Value: This parameter transmits the value of the conversion. If the conversion does not contain a value, the transmitted value should be '0.00'. |
|
| EUR | Currency Code (ISO 4217) |
|
| checkout | Sie ID: This parameter identifies the page on which the conversion is made. |
|
| 1234567890 | Click id, that was transmitted with the click-in to the website. Usually it is the iclid and as well the the gclid, fbclid. For S2S callbacks this parameter is mandatory. |
...
Variable (JS) | Variable (img/ s2s) | Explanation | Example |
|
| This parameter transmits any discount values related to the conversion. When a discount is applied, please do not change the order value, the system can deduct the discount value from the order value. | 12.34 |
|
| Code of the used voucher. | XMAS2020-4578aved |
|
| This parameter transmits any ID given to the customer who placed the conversion. Use this for implementing cross-device and cookieless tracking. Important parametr. | bon78945 |
|
| This parameter transmits any ID given to the session of the customer who placed the conversion. Use this for implementing cross-device and cookieless tracking. Important parameter! |
|
|
| This parameter registers whether the customer was new to the advertiser. Possible values are true (new) or false (recurring). | true |
|
| Payment method | paypal |
|
| This parameter can transmit additional information. | |
|
| This parameter can transmit additional information. | |
|
| This parameter can transmit additional information. | |
|
| This parameter can transmit additional information. |
read on
A detailed guide tracking code tag implementation and a list of all parameters can be found here.
Basket tracking
Basket tracking adds basket positions to a conversion. This way all individual products that are part or a conversion can be remunerated and/or analyzed.
...
| Code Block | ||
|---|---|---|
| ||
[{
"uuid": "34f40211-98dd-4543-8980-c4b9bcf7416a",
"pid": "123456",
"prn": "!Adidas Originals Continental 80",
"brn": "Adidas",
"pri": "54.95",
"qty": "1",
"trc": "default",
"prc": "Mode.Herren.Schuhe.Sneaker"
}, {
"uuid": "c4f3a903-f9c2-4921-b865-0719c067b3dd",
"pid": "9876543",
"prn": "Anna Field Damensocken schwarz",
"brn": "Anna Field",
"pri": "12.34",
"qty": "3",
"trc": "default",
"prc": "Mode.Damen.Zubehör"
}] |
The onpage
...
tag
The onpage code tag should be implemented on all publicly accessible pages. Its main purpose is the detection of incoming traffic. Further functionalities are related to traffic quality and a container functionality.
...
The following test is a suggestion for a section in the privacy policy of shops working with Ingenious Technologies. Tracking domain as well as external advertiser id (i-number in conversion tracking codetag) should be completed:
| Expand | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Tracking technology of the Ingenious Enterprise platform | Usage of cookies We are using a tracking technology provided by Ingenious Technologies AG, Französische Straße 48, 10117 Berlin, to connect customers’ views and clicks on advertising media (so called touch points) with their actions (for example a sale or a registration). For every touch point and every action, your browser sends a so called HTTP-request to the server of Ingenious Technologies, along with certain data. This data consists of the URL of the website on which the advertising media is placed (referrer URL), information on the browser, operative system and device, further technical data (so called HTTP-header), the time and date of the touch point, the IP address of the device and, if available, cookies stored previously by Ingenious Technologies and all the information they carry. Please note that the IP address is anonymized by Ingenious Technologies automatically. A cookie is a small package of data which is transferred between your browser and the server. In this package, information related to the advertising media can be stored, for example the content of a shopping basket. To document actions, the tracking technology stores cookies on your device. In the cookie, information on the last touch points is stored. This information includes data related to touch points, i.e. clicks and views of advertising media produced on your device. Furthermore, an ID is added to the cookie. Stored data on touch points and actions will be allocated to this ID. Stored touch points can be used to create a so called customer journey, which identifies all touch points preceding an action. An action request usually involves the order ID and the order value of your order. In some cases, the following values can be submitted and stored as well: your customer ID, your age and gender, your answers to customer surveys and a marker in case you are a new customer. Both the data transmitted to Ingenious and the cookies have the sole purpose of monitoring the effectivity of advertising media and the corresponding clearance. This usage is compliant with the legitimate interest as defined in the General Data Protection Regulation of the EU. If you do not want cookies to be stored in your browser, you can adjust your browser settings. Depending on the type of browser you use, you can prevent the storage of cookies in your browser settings or limit the storage to specific websites only. Please note that this might hamper the performance and limit your usage of certain websites. You can also delete cookies at any moment. In this case, the data stored in cookies will be deleted permanently. Storage and usage of tracking can be also disabled by clicking on the following tracking opt-out link:
In case the tracking opt-out link is clicked, a special cookie is stored which disables tracking for the browser used to enable the request on your device. Tracking will be applied again when you delete this cookie. What cookies are used for what tracking purposes is explained in the following table in detail:
|
...
Use of a first party tracking domain (for setup, please contact Ingenious Technologies)
Implementation of the click id, that should be saved with the use of server side technologies (PHP)
Implementation of the onpage codetag
Use customer id (which can be encrypted or hashed)
Use session id
in case of third party tracking: Execution of the conversion code tag server side (S2S callback) to bypass regulated browsers or ad blockers
...