What is Postback URL

Postbacks allow for communication between different platforms: trackers and ad networks, affiliate networks with ad trackers. Unlike browser-based tracking methods such as cookies or pixels, postbacks operate entirely on the server side — meaning they run invisibly in the background, unaffected by ad blockers, browser privacy settings, or cookie deletion. This makes them one of the most reliable mechanisms for passing conversion data across the digital advertising ecosystem.

Because postbacks require a firing mechanism to be implemented on the source side — typically by a developer integrating the logic into a server or backend — they are not as widely adopted by solo marketers or offer owners working without technical resources. There are, however, no-code and low-code solutions available that allow setting up a postback-firing mechanism without the need for a dedicated developer, such as pre-built integrations within affiliate tracking platforms.

Names

Postback is the term most commonly used in performance marketing and adtech, but the same underlying technology appears under different names depending on the platform or context:

Regardless of the name, all of these refer to the same core mechanism: a server-side HTTP request that carries structured data from one platform to another.

How It Works

A postback operates similarly to an API request but is intentionally simpler in design. It is a one-directional HTTP GET or POST request sent from one server to another, carrying data as URL parameters. The request can be triggered automatically by a predefined conversion event — such as a completed purchase, app install, or form submission — or it can be fired manually by pasting the full postback URL into a browser’s address bar, which is useful for testing purposes.

The flow typically works as follows: a user clicks an ad, the tracking platform records the click and generates a unique identifier, that identifier travels with the user through the campaign funnel, and when the user converts, the affiliate network or advertiser’s server fires a postback URL back to the tracker — completing the attribution loop entirely server to server, without any reliance on the user’s browser.

Postbacks can carry specific pieces of information using parameters. A parameter is a part of a postback URL and consists of a parameter_name={token} pair, where:

• The parameter name describes the type of value being passed. Examples include click ID, payout, payout currency, transaction ID, and conversion type.
• The token is a dynamic placeholder that the sending platform automatically replaces with a real value at the moment the postback fires.

For example, a parameter for passing payout value looks like this in the template:

payout={payout}

When the postback fires, the token is replaced with the actual value:

payout=0.5

Multiple parameters are chained together in the URL using & as a separator. The ? character separates the base URL from the parameter string. Each platform uses its own token syntax — curly braces {token}, square brackets [token], or percent signs %token% are all common formats depending on the network.

Parameters in Postback URL

The single most important parameter in any postback URL is the click ID. It is the unique identifier that ties a specific conversion back to the specific user click that initiated it. Without a valid click ID, most tracking systems will reject an incoming conversion to prevent data inconsistencies and attribution fraud.

Click IDs are assigned independently by both ad networks and ad trackers. The flow works as follows: the click ID is first appended to the offer URL when a user clicks an ad, passed through the campaign funnel to the affiliate network or offer page, and then returned in the postback URL when a conversion is recorded. This round-trip journey is what makes accurate, reliable attribution possible.

Most systems are configured to reject conversions that arrive without a recognized click ID. However, there are scenarios where a click ID may be unavailable — most notably on iOS 14.5 and later devices, where users who have opted out of app tracking cannot have their individual clicks identified. In these cases, some platforms allow conversions to be validated using an alternative identifier, such as a campaign ID, though this results in aggregated rather than individual-level attribution.

Other parameters that can be passed in a postback URL include:

• Payout — passes the monetary value of the conversion (e.g., the commission earned by the affiliate for that event). Useful for reconciling earnings and calculating return on ad spend in real time.
• Payout currency — specifies the currency in which the payout is denominated. Essential when working with international campaigns across multiple markets where currency values differ.
• Transaction ID — passes a unique identifier assigned to each individual conversion event. This is critical when a single click can result in multiple conversions — for example, when a user who clicked once subsequently makes several purchases. Without transaction IDs, each conversion cannot be individually identified, making it impossible to accurately track upsells or repeat purchases from the same user session.
• Conversion type — passes a label that distinguishes between different kinds of conversions. This is particularly valuable in campaigns where not all conversions have equal weight. For instance, an advertiser may assign different payout rates or optimization priorities to an app install versus an in-app purchase, or to a free trial signup versus a paid subscription activation.
• Status — indicates whether a conversion is confirmed, pending, or declined. This is especially important in verticals like finance or ecommerce where conversions may be subject to verification, fraud review, or chargeback.
• Offer ID / Affiliate ID — identifies which specific offer and which affiliate generated the conversion, enabling granular reporting and correct commission attribution in multi-partner programs.

Postbacks vs. Conversion Pixels

Postbacks are a reliable and privacy-resilient way to pass conversion data server to server. The main alternative — conversion pixels — are small snippets of JavaScript or image tags placed on a confirmation page that fire in the user’s browser when a conversion occurs. Pixels are easier to set up and require no server-side integration, but they are vulnerable to ad blockers, browser privacy restrictions, cookie deletion, and page load failures.

Because postbacks fire directly between servers without involving the user’s browser at all, they are unaffected by these limitations — making them the preferred tracking method in performance marketing, mobile advertising, and any context where data accuracy and privacy compliance are priorities.