...
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.
...
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’.
...
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: