Affiliate's pixel

There are 3 main pixel-based tracking methods: iFrame, Java Script and Image pixels. From an implementation perspective, all of the pixels work the exact same way.

Pixel tracking will place a cookie in the users browser when a click is occurred and will call back the cookie again on conversion situation to authenticate the conversion. The conversion information can all be extracted from that cookie and saved in Conversion Report. 

iFrame - This is a pixel that is set as an iFrame into a target page. It lights up when the conversion is complete. The conversion is recorded in the statistics as a lead. Please note that HTTP and HTTPS iFrame pixels are for client-based tracking with the use of cookies. The HTTP iFrame pixel is the industry standard for tracking conversions. Use the HTTPS iFrame pixel for offers that use SSL encryption. iFrame pixels are the recommended tracking options as they provide a robust facility for affiliates to track conversions in their own third-party systems.


<iframe src="" scrolling="no" frameborder="0" width="1" height="1"></iframe>


JavaScript - They are embedded into webpages using the <script> tag(like at the screenshot). It’s a JS file that can track the page a user came from, the time he spent on the page, and other granular details besides the number of page hits.

<script type="text/javascript" src="//"> </script> 

Image pixel
 - The image pixel is one of the first options in tracking conversions in the industry. The image pixel tracking protocol is usually used for offers in other tracking systems that do not support other tracking methods. Below is an example of what an offer image pixel.

<img height="1" width="1" style="display:none" src="[Game]=PBR&noscript=1"/>

Also we support the replacement of macro in affiliate's pixels, so you can get back the values, which are necessary for successfull conversion tracking.

The list of available macro:

{date} - The date will be used according to the timezone selected at affiliate's dashboard. If the timezone is not specified - UTC will be taken as a default.
sub1} - Subaccount 1
{sub2} - Subaccount 2
{sub3} - Subaccount 3
{sub4} - Subaccount 4
{sub5} - Subaccount 5
{sub6} - Subaccount 6
{sub7} - Subaccount 7
{sub8} - Subaccount 8
{city} - City
{geo} - Country


Was this article helpful?
6 out of 8 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.