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 (1×1 pixel) transparent image.
Cookie is basic tracking method. This is a client side tracking method which requires client cookie information.
It works by setting up an eucid (encrypted user cookie id) to cookie on user’s browser whenever the user clicks on any of your ads served through Eskimi DSP.
When the user completes a successful conversion event, eucid value will be read from cookie and transmitted back to Eskimi DSP server by calling back 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 cookie based conversion tracking, advertiser needs to pass back the eucid parameter value to Eskimi DSP conversion pixel by placing it on client side.
Eucid pass to advertiser
When user clicks on one of your ads, Eskimi DSP sets up an eucid value to cookie on user’s browser and redirects user to your landing page.
Conversion tracking
After a successful conversion event, advertiser will need to pass the eucid value by placing a client side invisible pixel on conversion page
<img src=”//dsp.eskimi.com/pixel/cookie” style=“display:none” />.
Please note that the tag must be implemented in the <body> of the “Success” page.
The eucid from user cookie is read automatically by Eskimi DSP.
Note: Our conversion tracking pixel can not only be fired on success page but also can be placed on Javascript events, e.g. onclick Bet now button. If such action happens, script need to http-request https://dsp.eskimi.com/pixel/cookie
The main point is that our conversion pixel must be fired (http-requested) from user’s browser side (loaded as image element).
Conversion tracking flow example
