Support Questions:Why can affiliates only use image pixels or postback URLs
From HasOffers
When an offer uses HTTP Image Pixel or HTTPS Image Pixel for its conversion tracking method, affiliates capabilities for third-party pixels are limited.
When an offer has an image pixel placed, only other image pixels can be loaded inside the main offer image pixel. When an affiliate pixel is placed as an image pixel, browsers only load the URL of the image. Browsers are unable to load additional URLs inside an image or any other HTML content since the browser is interpreting it as an image.
For offers that use an image conversion tracking pixel, the HasOffers platform allows affiliates to place 1 single image pixel only. After the offers loads the HasOffers Image Pixel and the HasOffers platform registers a conversion, the ad server redirects the image pixel URL to the URL of the affiliate image pixel using a 302 redirect. Since the ad server can only redirect to one location, an affiliate can only place one image pixel.
An unlimited number of affiliate postback URLs can be added to offers that use an image conversion tracking pixel. Since postback URLs don’t rely on cookies and are loaded by the ad server itself (not by client’s browser), the ad sever can load as many postback URLs for affiliates as needed.
If your affiliate requires you to place third-party tracking pixel that isn’t an image, then you will need to have the advertiser update the offer conversion tracking pixel to be either an HTTP iFrame Pixel or HTTPS iFrame Pixel. When an advertiser places an iFrame pixel, the ad server can display any sort of affiliate code inside the iFrame. Thus, iFrame pixels are the preferred tracking pixel for offers.
Email this page to a friend or co-worker
