Overview
Trackier provides multiple methods to track conversions, including Server Postback (S2S), Image Pixel, and IFrame Pixel. Each method has its own use case, placement requirements, and level of reliability. Choosing the right tracking method depends on your campaign setup, the type of data you want to capture, and the integration capabilities of your platform. This guide explains the differences, recommended usage, and examples of each method.
How Each Method Works
1. Server Postback (S2S) — Recommended
A Server-to-Server (S2S) postback is a direct server-level communication between the advertiser's system and Trackier. When a conversion occurs, the advertiser's server sends an HTTP request to Trackier's postback URL, passing the click ID and any other conversion data (such as sale amount or currency) as URL parameters.
Because this happens entirely server-to-server, it is not affected by browser settings, ad blockers, or cookie restrictions — making it the most reliable tracking method available.
The click ID is mandatory — it tells Trackier which click to attribute the conversion to
Placed on the advertiser's server or tracking software — not on a webpage
Not suitable for loading third-party pixels like Google or Facebook within Trackier
Recommended above all other methods
Sample Postback URL:
https://demo.trackier.co/acquisition?click_id=CLICK_ID&security_token=b503xxxxxxxxxxxxac33&sale_amount=AMOUNT¤cy=INR
2. IFrame Pixel — Recommended Over Image Pixel
An IFrame pixel is a small snippet of HTML code placed on the advertiser's Thank You or confirmation page. Unlike an image pixel, an IFrame can act as a container — it can hold and fire multiple other pixels (such as Google or Facebook pixels) from within it, making it more versatile for campaigns that require multiple tracking tags on the same page.
The click ID is not mandatory, making it easier to implement for advertisers who cannot pass click IDs
Placed inside the
<body>tag of the Thank You page — either directly or via Google Tag Manager (GTM)Supports loading Google and Facebook pixels inside the IFrame, which the other two methods do not
Recommended over the Image Pixel when pixel-based tracking is required
Sample IFrame Pixel Code:
html
<iframe src="https://demo.gotrackier.com/pixel?adid=5fcfxxxxxxxxxxxxxxx0dc3" scrolling="no" frameborder="0" width="1" height="1"></iframe>
3. Image Pixel — Least Recommended
An Image pixel is a 1x1 transparent image tag placed on the advertiser's Thank You page. When the page loads, the browser makes a request to the pixel URL, which triggers the conversion in Trackier. It is the simplest method to implement but the least reliable, as it can be blocked by ad blockers, privacy settings, and some browsers.
The click ID is not mandatory
Placed inside the
<body>tag of the Thank You page — either directly or via GTMCannot load third-party pixels like Google or Facebook within Trackier
Least recommended — use only when S2S postback and IFrame pixel are not feasible
Sample Image Pixel Code:
html
<img src="https://demo.vnative.net/pixel?adid=64bexxxxxxxxxxxxxxxx4e28&sale_amount=AMOUNT¤cy=INR">
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 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. |
Conclusion
Understanding the differences between Server Postback, Image Pixel, and IFrame Pixel is essential for accurate conversion tracking. Server Postback (S2S) is the most reliable method, sending conversions directly from the advertiser server and requiring a click ID. Image Pixels are simpler but less recommended, while IFrame Pixels allow multiple pixels to be nested and can include Google or Facebook pixels. Choosing the right method ensures accurate reporting, better campaign performance tracking, and seamless integration with your tracking platform.
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.
