What is a postback URL? It is a web address that an affiliate network or advertiser calls from its server when a conversion happens, passing back the click ID you sent it so your tracker can record the sale against the right click, campaign and traffic source. Because it travels server to server, it does not rely on the visitor's browser, cookies or pixels.

That is why media buyers and serious publishers treat postbacks as the backbone of their reporting. Below is a worked example, what each parameter does, and how to set one up without the usual mistakes.

How a postback URL works, step by step

The mechanics are the same in almost every tracker and network:

  1. A visitor clicks your ad or link. Your tracker records the click and creates a unique click ID, such as a7f3c91e.
  2. The tracker redirects the visitor to the offer, adding that click ID to the offer URL in the parameter the network expects (often a sub-ID field).
  3. The network stores the click ID alongside its own record of the visit.
  4. The visitor converts: signs up, subscribes or buys.
  5. The network's server takes your postback URL, replaces the placeholders with real values (the stored click ID, payout, transaction ID) and requests it.
  6. Your tracker receives the request, matches the click ID to the original click and records the conversion and revenue.

The term "S2S postback" simply means this server-to-server callback, as opposed to a browser pixel. For the trade-offs, see our comparison of server-to-server vs pixel tracking.

A postback URL example, explained

Here is a hypothetical postback URL as you might paste it into a network's settings. The domain and parameter names are illustrative; your tracker will give you its own format.

https://track.example-tracker.com/postback?cid={aff_sub}&payout={payout}&txid={transaction_id}&status={status}

Breaking it down:

PartWhat it isWho defines it
track.example-tracker.com/postbackThe endpoint on your tracker (ideally your own custom tracking domain) that listens for conversionsYour tracker
cid=The parameter name your tracker reads the click ID fromYour tracker
{aff_sub}The network's macro (placeholder) holding the click ID you passed inThe network
payout={payout}The commission amount for this conversionTracker parameter, network macro
txid={transaction_id}A unique conversion ID, used to block duplicatesTracker parameter, network macro
status={status}Optional: approved, pending or reversedTracker parameter, network macro

When a conversion fires, the network turns that template into something like ...postback?cid=a7f3c91e&payout=35.00&txid=88412&status=approved. If your tracker log ever shows the literal text {aff_sub} instead of a value, the network did not recognise the macro.

Postback parameters and macros: the essentials

The most confusing part for newcomers is that two vocabularies meet in one URL. The parameter names on the left of each equals sign belong to your tracker. The macros on the right, usually in braces, square brackets or hash marks, belong to the network. Each network documents its own; never assume they match your tracker's.

Parameters you almost always need

  • Click ID: the only thing that links the sale to the click. Without it, the postback is useless.
  • Payout: so revenue and ROI are calculated from real values, not a fixed estimate.
  • Transaction or order ID: lets the tracker ignore duplicates.

Useful extras

  • Status or event type: distinguishes leads, first payments, rebills and reversals.
  • Currency: essential if you work with programs paying in EUR, GBP and USD.
  • Additional sub-IDs: some setups pass back placement or creative data. Our guide to sub-IDs covers naming them sensibly.

How to set up a postback between a network and a tracker

The exact screens differ, but the sequence does not.

  1. Add the network in your tracker. Most trackers have templates for common networks that pre-fill the click ID parameter and postback format. Check the template against the network's current documentation anyway.
  2. Add the offer with the click ID token. Paste the network's affiliate link into the tracker's offer URL and put your tracker's click ID token into the network's sub-ID parameter, for example &aff_sub={clickid} (the braces here are your tracker's token).
  3. Copy the postback URL from your tracker. It will contain placeholders where the network's macros must go.
  4. Replace placeholders with the network's macros. Use the network's documented macro for the sub-ID field that carries your click ID, and its macros for payout and transaction ID.
  5. Paste the postback into the network. Usually under a global postback setting or per offer. Some networks require an affiliate manager to enable it.
  6. Run a test conversion. Follow the steps in our guide to testing affiliate tracking before sending traffic, then check the tracker's postback log.

Common mistake: passing the click ID in one sub-ID field (say, sub1) but using the macro for a different one (sub2) in the postback. The postback fires, but with an empty click ID, and the conversion lands nowhere.

Global, offer-level and event postbacks

Networks typically let you set postbacks at different levels:

  • Global: one postback for every offer you run. Easiest to maintain if every offer passes the click ID in the same field.
  • Offer-level: a specific postback for one offer, which overrides the global one. Useful when an offer pays on a different event.
  • Event or goal postbacks: separate calls for a registration, a first deposit or payment, and later rebills. Revshare deals benefit from these, because you can see lifetime revenue per traffic source.

Ask whether the network sends a postback, or any signal, for reversals and chargebacks. If not, your tracker will overstate revenue, and you will need to reconcile against the network's approved figures before paying for more traffic.

Postback security and data handling

A postback endpoint is just a URL, so anyone who discovers it could, in principle, send fake conversions. Sensible precautions:

  • Use a secret token parameter if your tracker supports one, and only give it to the network.
  • Whitelist the network's server IP addresses where your tracker allows it.
  • Rely on transaction IDs so replayed requests are not double counted.

Postbacks normally carry pseudonymous IDs rather than names or emails, and you should keep it that way. Do not ask networks to pass customer email addresses or other personal data in a postback. For the legal side, our guide to whether server-side tracking is GDPR compliant explains why server-to-server does not mean outside data protection law.

Frequently asked questions

What is the difference between a postback and a pixel?

A pixel is code loaded in the visitor's browser on the confirmation page; a postback is a request from the network's server to your tracker. Postbacks are not affected by ad blockers or browser cookie limits, but they need the click ID to be passed through correctly.

Why is my postback not firing?

The usual causes are a wrong macro, the click ID passed in a different sub-ID field, the postback not saved at the right level, or a conversion type that does not trigger postbacks. Our guide to affiliate conversions not tracking has a full diagnostic flow.

Do I need a tracker to use postbacks?

You need something that can receive them: a tracker, an analytics platform with a server endpoint, or your own script. Most affiliates use a tracker because it also handles click IDs and reporting.

Next steps

Set up one postback, test it with a single conversion and only then add more offers. If you are still choosing software, compare options in our affiliate tracking platforms directory or read more in our tracking and analytics guides.