The system uses tracking pixel (later referred as "pixel") to notify affiliate network on an action performed on advertiser's website.
In lay terms, when an action is performed, the code of the page that visitor is loading includes the code that loads a transparent 1x1 pixel size image from the SLICE Digital server which is invisible for visitor. This image is used to execute a request to the affiliate network server and transfer the required parameters.
If the advertiser assigns unique ID for every action to make it possible to easily find additional information for each action, such ID must be transferred to pixel by the "afid" parameter. Below are ID examples:
- request number
- visitor ID
- payment number
- the ID of an object created in advertiser's system
- etc.
Any sequence of numbers, letters, and characters without spaces can serve as an ID. The afid parameter is transferred to pixel.
Tracking pixel can be installed in 3 different ways (you should choose one. JavaScript is the common-used one):
- JavaScript
- Image
- Iframe
JavaScript
This type of tracking requires two pieces of code to be installed on advertisers web-site.
First JavaScript pixel
Standard JavaScript pixel looks like:
<script language="javascript" type="text/javascript">function sc(v){var d=new Date();d.setTime(d.getTime()+(365*24*60*60*1000));document.cookie="affclick="+v+";"+"expires="+d.toUTCString()+";path=/";localStorage.setItem('affclick',v)}sc((new URLSearchParams(window.location.search)).get("clickid"))</script>
An advertiser should place this code after the opening <body> tag on the landing page. It's required to add &clickid={clickid} parameter in the Tracking URL - SLICE Digital manager will add this parameter.
Second JavaScript pixel
Standard JavaScript pixel looks like:
<!-- S.L.I.C.E. Digital tracking pixel :: Begin -->
<script language="JavaScript" type="text/javascript">
// Required fields
var afid = 'XXXX'; // unique order or sale ID
var afgoal = 'XXXX'; // (required) goal name. Can be 'lead', 'sale', 'signup' or other
var afsecure = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'; // (required) security hash provided by S.L.I.C.E. Digital manager
// Optional fields
var afprice = ''; // total order sum/value/monthly price
var afcomment = ''; // any comments for this order, e.g. plan name/details
var custom_field1 = ''; // custom field 1
var custom_field2 = ''; // custom field 2
var custom_field3 = ''; // custom field 3
var custom_field4 = ''; // custom field 4
var custom_field5 = ''; // custom field 5
var custom_field6 = ''; // custom field 6
var custom_field7 = ''; // custom field 7
</script>
<script language="JavaScript" type="text/javascript" src="//track.roeye.co.nz/track.js"></script>
<!-- S.L.I.C.E. Digital tracking pixel :: End -->
where:
Mandatory parameters - advertiser MUST set it up:
- afid - unique request ID on advertiser's side
- afprice - payout for conversion
- afgoal - goal ID provided by S.L.I.C.E. Digital manager
- afsecure - security hash provided by S.L.I.C.E. Digital manager
Optional parameters - advertiser MIGHT set it up:
- afcomment - comment (any additional information advertiser can pass)
- custom_fieldX - any extra data
XXXX values in the pixel must be replaced with the real values.
The script is intended for transferring visitor's action and must be installed on the page that confirms this action - 'Thank you' page.
iFrame pixel
An iFrame pixel is the most common pixel-based method of tracking conversions. Here is an example of what an offer iFrame pixel looks like:
<!-- S.L.I.C.E. Digital tracking pixel :: Begin -->
<iframe src="//track.slice.digital/success.php?afid=XXXX&afgoal=XXXX&afprice=XXXX&afsecure=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&afcomment=" height="1" width="1" />
<!-- S.L.I.C.E. Digital tracking pixel :: End -->
where:
Mandatory parameters - advertiser MUST set it up:
- afid - unique request ID on advertiser's side
- afprice - payout for conversion
- afgoal - goal ID provided by S.L.I.C.E. Digital manager
- afsecure - security hash provided by S.L.I.C.E. Digital manager
Optional parameters - advertiser MIGHT set it up:
- afcomment - comment (any additional information advertiser can pass)
XXXX values in the pixel must be replaced with the real values.
The script is intended for transferring visitor's action and must be installed on the page that confirms this action - 'Thank you' page.
The iFrame protocol is the option for tracking conversions on the client-side, it is generally more accurate than using an image pixel because it does not use the image tag to call the conversion URL for the offer, which has proven to be less reliable.
Another advantage that iFrame has is its robustness in firing affiliate pixels inside itself. When an affiliate wants to track conversions on their end, they can place their own pixel inside to track in real time. When you have an iFrame pixel, this has unlimited formats to load their pixels, while image pixels can only load other image pixels. iFrame is usually the best option to track conversions on the client-side.
Image pixel
The image pixel is the legacy client-side tracking option for your account, and was one of the first options in tracking conversions in the industry. In most cases, the iFrame pixel option is recommended simply because it is the most compatible with other tracking systems. 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:
<!-- S.L.I.C.E. Digital tracking pixel :: Begin -->
<img src="//track.slice.digital/success.php?afid=XXXX&afgoal=XXXX&afprice=XXXX&afsecure=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx&afcomment=" height="1" width="1" alt="" />
<!-- S.L.I.C.E. Digital tracking pixel :: End -->
where:
Mandatory parameters - advertiser MUST set it up:
- afid - unique request ID on advertiser's side
- afprice - payout for conversion
- afgoal - goal ID provided by S.L.I.C.E. Digital manager
- afsecure - security hash provided by S.L.I.C.E. Digital manager
Optional parameters - advertiser MIGHT set it up:
- afcomment - comment (any additional information advertiser can pass)
XXXX values in the pixel must be replaced with the real values.
The script is intended for transferring visitor's action and must be installed on the page that confirms this action - 'Thank you' page.
This does not mean that image pixels are not accurate, they use the same methods for tracking conversions as the iFrame pixel. Like the iFrame pixel, the image pixel runs into the same limitations and advantages that iFrames do. With cookie-based offers, the cookie will remain in the users browser even if they leave the offer funnel and leaves them the potential to come back later to the offer and convert. Just like the iFrame, the only step to set up the offer with an image pixel is to add the code to the conversion page.
Cookie-based tracking with iFrame and image pixels does have a few limitations. When placing a cookie in the users browser, you are running the assumption that the user will not modify the setting in the browser, or clear their cookies out, which happens on occasion. There is also the risk of the user blocking cookies in their browser, but can still convert on the offer. Both situations will result in legitimate conversions not being tracked. While these instances are very rare, this is something to consider when tracking offers with cookies.