Clickcode based conversion tracking. Advanced method

What is conversion tracking?

Conversion tracking is a tool that shows you what happens after a customer clicks on your advertisement - whether they purchased your product, signed up for your newsletter, or filled out a form to receive more information. By tracking conversions, you will be able to know which campaigns, sites, or apps bring you business. This helps you invest more wisely in the best ones and boost your return on investment (ROI).

Eskimi DSP can provide these enhanced metrics by implementing conversion tracking pixel on your side. The conversion pixel is a tiny (1x1 pixel) transparent image.

Click code is an advanced tracking method. This is a server-side tracking method that does not require any client cookie information.

It works by passing back a eucid (encrypted user cookie id) value which is added to your landing page URL whenever the user clicks on any of your ads served through Eskimi DSP.

When the user completes a successful conversion event, the advertiser needs to transmit eucid value back to the Eskimi DSP server by calling back the DSP server's conversion tracking pixel.

Once the eucid is validated on a server, a successful conversion event will be recorded and will appear on the campaign performance optimization tool.

Implementation.

To enable click code based conversion tracking, the advertiser needs to pass back the eucid parameter value to Eskimi DSP conversion pixel by either requesting it by s2s (server to server) method or c2s (client to server) method.

Eucid pass to the advertiser

When the user clicks on one of your ads, Eskimi DSP adds a eucid (click code) parameter to the landing page URL and redirects the user to your landing page. By default, eucid is added automatically by using an HTTP GET method parameter under the name eucid.

The example below shows how the landing page URL looks before and after the user is redirected with the added eucid parameter:

before: http://advertisersite.com/campaign.php

after: http://advertisersite.com/campaign.php?eucid=MTAwMjZfNjU4NTg4NDFfbmdf

The advertiser is allowed to use a custom parameter name instead of eucid by adding {eucid} macro to the landing page URL while setting up the new campaign. This will be replaced with a unique eucid value automatically.

The example below shows how the landing page URL looks before and after user is redirected with added custom_name parameter:

before: http://advertisersite.com/campaign.php?custom_name={eucid}

after: http://advertisersite.com/campaign.php?custom_name=MTAwMjZfNjU4NTg4NDFfbmdf

Importance of eucid transportation

The advertiser is required to store the passed eucid until a successful conversion or end of the session occurs.

To perform a one-time conversion notification, the advertiser needs to issue the eucid by HTTP request either from the server-side (s2s) or an invisible pixel on the client's side (c2s).

From the examples above, we already know that eucid value is MTAwMjZfNjU4NTg4NDFfbmdf. The advertiser is required to keep this value until a successful conversion occurs.

Conversion tracking

After a successful conversion event, the advertiser will need to pass the eucid value by making a server-side HTTP request (s2s) to the URL https://dsp.eskimi.com/pixel?eucid=MTAwMjZfNjU4NTg4NDFfbmdf

or by placing a client-side invisible pixel (c2s) on the conversion page
<img src=”//dsp.eskimi.com/pixel?eucid=MTAwMjZfNjU4NTg4NDFfbmdf" style=”display:none” />.

Conversion tracking flow example