Pixel Compliancy is important to understand when using

confirmation pixels.  The pixel compliancy chart will help you

maintain tracking between you and the Publisher
. 
Image Pixels:
An image pixel is a pixel URL delivered to the confirmation page via
an HTML image tag. 
Example: 
<img src="http://www.domain.com/pixel.aspx" height="1" width="1">

Javascript Pixels:
A Javascript pixel is a tracking URL located on the confirmation
page within javascript tags (See examples below).  Most JavaScript
pixels are accompanied by a <noscript> pixel.  <noscript> pixels should
not be used in LinkTrust.  They are intended to only be placed on the
actual confirmation page as a backup in the event that the consumer's
browser has scripting disabled. 
Example:
script language="JavaScript"
src=http://domain.com/pixel.aspx></script>
This example shows you what a <noscript> pixel looks like:
<noscript><img src="http://www.domain.com/pixel.aspx" height="1"
width="1"></noscript>

iFrame Pixels:
An iFrame pixel is a pixel delivered to the confirmation page via
an iFrame tag.  This type of pixel is not as efficient as a JavaScript
pixel. 
Example:
 <iFrame scr="http://www.domain.com/pixel.aspx" ></iFrame>

Server-side Pixels:
A Server-Side pixel is a Post Back URL executed by a server instead of
the confirmation page.  A server side post back URL is just a URL that
should be executed upon each conversion.  When your merchant is
going to fire your LT post back URL, please make sure the URL is not
secure.  
Example: 
http://www.domain.com/pixel.aspx