Pixel Compliancy is important to understand when using confirmation pixels. The pixel compliancy chart will help you maintain tracking between your merchant, you and the affiliate.
An image pixel is a pixel URL delivered to the confirmation page via an HTML image tag. When copying pixels into the PixVantage textbox, make sure you replace all single quotes (') with double quotes (").
Example: <img src="http://www.domain.com/pixel.aspx" height="1" width="1">
This example shows you what a <noscript> pixel looks like:
<noscript><img src="" height="1" width="1"></noscript>
We have discovered an issue where advertisers/clients that use asynchronous calls on their websites to fire LT JS pixels dont fire affiliates pixels that are being piggybacked. Thus the affiliate does not see the conversions in their platform. This is not a LinkTrust issue. It has to do with the inability for an asynchronous call to do a document.write to the page.
"document.write can't be called from an asynchronous script, because it's detached from the document and therefore your JS parser doesn't know where to put it. at best, the browser will ignore it."
One way to identify if an Asynchronous call is being used is to run the pixel test while using Google Chromes F12 option. In the Console, it will give you the an error that looks similar to this one.
Example: <iFrame scr="" ></iFrame>
A Server-Side pixel is a Post Back URL executed by a LinkTrust 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. LinkTrust will not recognize secure post back URLs.