...
Transmitting a click ID in the conversion code tag allows tracking and attribution even without cookies or in case no cookie is found or available.
The idea is to transmit an ID when a user clicks is redirected to a shop or a web site. This ID then is saved by the shop/website, for example in a first party cookie or in the database. When the conversion is called, it is transmitted in the conversion codetag.
For the ID you can use the default Ingenious click ID. The possibility exists to use custom click IDs as well, e.g., if you want to use existing IDs that you have in your system. The next two sections explain both variants.
...
The default click ID is automatically generated by the Ingenious Platform and assigned to the click. Usually, Ingenious adds a click id automatically to every (bounce) tracking link, so you do not need to do anything. The name of the Ingenious click . You only need to configure the transmission.id is ICLID. It looks like this (example)
| Code Block |
|---|
https://www.shop.com/?iclid=#{ICLID} |
where #{ICLID} will obviously be replaced by the click id.
Exception: Manual configuration
In (usually very rare) cases, where you need to set up the transmission of the click id manually (for example if a certain specific parameter is needed, you may do the set up manually. The automatically generated parameter ICLID is not added by default in this case.
The click ID will be transmitted as query parameter in the URL with every click. This happens with the use of the additional parameter tool.
...
You reach this page by clicking on ‘manage advertiser’ in the advertiser section main navigation menu. On the page with the overview of all the advertisers on your platform, click on the icon next to the relevant advertiser. You will find the additional parameter feature in the middle of the page.
Start to create a new parameter by clicking on the icon. If you do so, three new fields will appear under the columns ‘parameter name’, ‘value type’ and ‘value’.
Under ‘parameter name’ fill in the parameter name the system via which you will trigger the conversion code tag requires.
Under ‘value type’, select ‘dynamic’.
Under ‘value’ select ‘click ID’.
When you are done, scroll down the page and click on the button ‘save’ in the right lower corner.
Example result: https://yourshopdomain.com/?clicklid=#{CLICK_ID}
read more here: Additional parameters
Transmitting an Ingenious ID (ICLID) on ad impressions
In some cases it can be useful to transmit an Ingenious ID with ad impression redirects. You can use the placeholder #{ICLID} on any redirect target: trg=https%3A%2F%2Fyourshop.com%2Fhtlp.html%3Ficlid%3D%23%7BICLID%7D
You can provide such ad impression ID on conversions the same way as the click one. The background system will automatically add the corresponding ad impression touchpoint to the user journey and process it according to the attribution rules.
read more here: Post View Tracking with a High Traffic Landing Page (HTLP)
Transmitting a custom click ID
...
Then, before executing the conversion codetag, the click ID needs to be fetched from the cookie/ the data base so that it can be transmitted in the conversion codetag.
Examples for saving the click ID
...
| Code Block | ||
|---|---|---|
| ||
<script>
function getCookie(cname) {
var name = cname + "="; var ca = document.cookie.split(";"); for (var i = 0; i < ca.length; i++) {
var c = ca[i]; while (c.charAt(0) == " ") {
c = c.substring(1);
} if (c.indexOf(name) == 0) {
return c.substring(name.length, c.length);
}
} return "";
}
var clickid = getCookie("clickid");
</script>
|
Implementing the conversion
...
tag with click ID
When implementing the conversion codetag, add all the parameters you need. Make sure, that the click ID that you fetched from the cookie is transmitted. This happens with the parameter ‘clickId’ when you use the Javascript code or with ‘cli’ when you use the image pixel or server to server callback URL.
Further reading on how to implement the conversion codetag: