Skip to main content

s2s (server to server) method

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 optimizationoptimisation tool.

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.

 

Examples

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} 

afterhttp://advertisersite.com/campaign.php?custom_name=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.

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).

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 

 

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.

  • Eskimi Postback URL for s2s tracking with redirect:

Our Postback urlURL for S2S tracking: https://dsp.eskimi.com/pixel?eucid={random_click_id} 
WellThe placingrandom_click_id this postback url random_click_id needs to be replaced with your click_id macro, so when conversion happens it should send us the value for click id which delivered conversion.

  • Eskimi Postback URL for s2s tracking without redirect:

This tracker can be sharedused forby clientsadvertisers which don'tdo not support redirect in postback.postback Itrequest. mightThis be not thatis unusual case,case because mostlymost allof systems support redirect.

Our Postback urlURL for S2S tracking: https://dsp-ap.eskimi.com/campaign/pixel?eucid={random_click_id} 
The random_click_id  shouldneeds to be replaced with clientyour click_id macro, so when conversionsconversion happenedhappens it should send us the value for click id which deliversdelivered conversion.

 

// BotSonic