📅Meet us at SBC Summit Americas 2026 — Fort Lauderdale, USA, May 12-14, 2026

Postback

A postback is a server-to-server HTTP callback used to confirm that a conversion event -- such as a registration, FTD, or purchase -- has occurred. Postbacks are more reliable than browser-based tracking because they are not affected by ad blockers, cookie restrictions, or client-side failures.

What it means in practice

A postback is a server-to-server (S2S) notification sent from the advertiser's or operator's server to the tracking platform when a conversion event takes place. Unlike pixel-based tracking, which relies on a snippet of code firing in the user's browser, a postback is triggered entirely on the server side. This makes it independent of browser behavior, ad blockers, and cookie duration limitations.

The typical postback flow works as follows: a user clicks an affiliate link, which passes a unique click ID to the operator's site. When the user completes a qualifying action -- such as a first-time deposit (FTD) or registration -- within the attribution window, the operator's server sends an HTTP request back to the tracking platform, including the click ID and conversion details. The tracking platform then attributes the conversion to the correct affiliate.

Postbacks are the industry standard for high-accuracy affiliate attribution. They reduce discrepancies between what affiliates report and what operators record, because both sides rely on the same server-side event. However, proper implementation requires coordination between the operator's tech team and the tracking platform to ensure click IDs are captured, stored, and passed back correctly.

How Postback works across industries

See how postback is applied in the verticals Track360 supports, from qualification logic and payout structure to the operational context behind each model.

iGaming

Postback in iGaming affiliate programs

In iGaming, postbacks are used to confirm [FTDs](/glossary/ftd), registrations, and qualifying deposits. Since [CPA](/glossary/cpa) and [RevShare](/glossary/revshare) payouts depend on accurate conversion data, postback reliability directly impacts commission accuracy and affiliate trust. Operators typically fire postbacks for multiple event types to support different deal structures.
Read More
Forex

Postback in Forex partner and IB models

In Forex, postbacks confirm account registrations, first deposits, and sometimes individual trades. Because [introducing broker](/glossary/introducing-broker) commissions often depend on ongoing trading activity, Forex postback implementations may include recurring event notifications alongside one-time conversion events.
Read More
Prop Trading

Postback in prop trading acquisition flows

In Prop Trading, postbacks typically fire when a referred user purchases a trading challenge or evaluation. Since the purchase event is the primary conversion in most prop firm affiliate programs, postback accuracy is critical for [CPA-based](/glossary/cpa) commission calculations.
Read More

How Track360 handles this

Track360 supports server-to-server postback integrations with configurable event types, automatic click ID management, and real-time conversion logging. Operators can monitor postback delivery status and troubleshoot failures directly from the reporting dashboard.

FAQ

Frequently Asked Questions

Common questions about postback, how it works in affiliate programs, and where it shows up across Track360's supported verticals.

A tracking pixel fires in the user's browser when a conversion page loads. A postback is sent directly from the operator's server to the tracking platform. Postbacks are more reliable because they are not affected by ad blockers, browser privacy settings, or cookie restrictions that can prevent pixels from firing.