A detailed look at pixel types
iFRAME Pixel
Target multiple landing pages for the same campaign. An iFrame is an object on a page that allows a site to embed HTML from an external source. When the advertiser places the iFrame pixel on the site, 3rd party pixels are displayed within the iFrame allowing a publisher's system to make a direct connection with the end-user. The iFrame is very versatile because it allows multiple 3rd party pixels per affiliate, as well as access to cookies placed by the publisher's tracking system.
Example iframe pixel generated from the system:
<iframe width='1' height='1' frameborder='0' src='http://affiliate.yourdomain.com/rd/ipx.php?hid=[TRACKING_VAR_VALUE]&sid=2&transid=[UNIQUE_TRANSACTION_ID]'></iframe>
Placing an iFrame pixel with the advertiser will give you the capability of placing any type of pixel for your affiliates. An iframe pixel is capable of firing all types of pixels such as iFrame, image, javascript and postback URL.
JAVASCRIPT Pixel
Javascript is a client-side scripting language. A Javascript pixel can be used In lieu of an iFrame if the advertiser cannot place an iFrame on the site. The Javascript is just as versatile as the iFrame pixel when firing third party/affiliates pixels.
Example Javascript pixel generated from the system:
<script type='text/javascript' src='http://affiliate.yourdomain.com/rd/jpx.php?hid=[TRACKING_VAR_VALUE]&sid=2&transid=[UNIQUE_TRANSACTION_ID]'></script>
Users have the ability to disable Javascript. If user has Javascript disabled, sales will not track when using this type of pixel.
IMAGE Pixel
An image pixel can be used when the advertiser cannot place an iFrame pixel on the site. Unlike an iFrame, HTML cannot be placed within an image so there are limitations when placing third party pixels when an image pixel is used.
Example image pixel generated from the system:
<img width='1' height='1' border='0' src='http://affiliate.yourdomain.com/rd/px.php?hid=[TRACKING_VAR_VALUE]&sid=2&transid=[UNIQUE_TRANSACTION_ID]' />
You can only place one third party pixel for each affiliate for a particular campaign, and it must be an image pixel. Any other third party pixels placed, will be attempted from the server level though it isn't guaranteed that the affiliate pixel will track if it needs access to the users' cookies.
POSTBACK URL
Postback URL are also known as Server2Server (S2S) or server side pixels to target multiple landing pages. A postback URL can only fire other postback URLs. Firing a Post Back pixel from a remote server has several advantages over placing a pixel directly on a thank you page. It's a secure way to report sales since it happens in the background. In addition, there isn't any unnecessary HTML on the confirmation page. Affiliates must have the ability to track without cookies. Thus, anytime that you place a postback URL with your advertiser, you will be limited to only placing postback URL's for your affiliates.
Example Postback URL pixel generated from the system:
https://affiliate.yourdomain.com/rd/px.php?hid=[TRACKING_VAR_VALUE]&sid=2&transid=[UNIQUE_TRANSACTION_ID]
Tracking via Hit ID is necessary since cookies won't exist on a server, so the advertiser must be able to process sub ID's to be able to dynamically insert the Hit ID in the pixel when reporting a sale.
