At a Glance: This article will provide you with the details and distinctions among server postback, HTTP/HTTPS image, and HTTP/HTTPS iframe pixel options.
Difference between Postback, Image, and Iframe Pixel
Server Postback | Image Pixel | Iframe Pixel |
S2S postback integration comprises a URL that will send a conversion from the advertiser server by replacing the click ID you have sent via the tracking URL. | It is a small piece of code snippet that you add to your Thank You page code, inside the <body> tag. | The IFrame pixel is similar to the Image pixel, but it can work as a piggy bank that holds more pixels inside it, which you will add to the platform for affiliates. |
The click ID is mandatory. | The click ID is not mandatory. | The click ID is not mandatory. |
You need to place on the server or tracking software. | You need to place the code directly or via GTM inside the <body> tag. | You need to place the code directly or via GTM inside the <body> tag. |
Recommended above all the methods. | Least Recommended. | Recommended above Image Pixel. |
Google or Facebook pixels can't be added to Trackier with this integration. | Google or Facebook pixels can't be added to Trackier with this integration. | Google or Facebook pixels can be added to Trackier with this integration. |
Examples:
1. Server Postback (S2S)
2. Image Pixel
<img src="https://demo.vnative.net/pixel?adid=64bexxxxxxxxxxxxxxxx4e28&sale_amount=AMOUNT¤cy=INR">
3. IFrame Pixel
<iframe src="https://demo.gotrackier.com/pixel?adid=5fcfxxxxxxxxxxxxxxx0dc3" scrolling="no" frameborder="0" width="1" height="1"></iframe>
We're thrilled to have put together a top-notch team of qualified experts who are available to handle any of your concerns and respond to any inquiries you may have. You can contact us at any time by sending an email to support@trackier.com or using the in-platform chat feature.
