What is a postback URL and how does it work?

12 min readUpdated Apr 15, 2026

What is a postback URL and how does it work?

A postback URL is a server-to-server call your affiliate network or offer platform makes to your tracker the moment a conversion is confirmed. The network hits a unique URL you generate in the tracker, the tracker matches the click ID in that URL to the click it recorded earlier, and the conversion is attributed — no cookie, no browser redirect, no pixel required. In postback URL affiliate tracking, that single mechanism is what lets you trust your conversion numbers and calculate real ROI per campaign, per sub-ID, per geo.

If you've ever seen a network report 40 conversions while your tracker shows 26, you already know why this matters. The gap is usually a mix of pixel failures, blocked cookies, and redirects that drop parameters. Postbacks close most of it. This article explains the exact flow, what each parameter does, how to wire it up on Adtraxo and the network side, and how to debug the three failure modes that account for nearly every broken integration.

What is a postback URL in affiliate tracking?

A postback URL is an endpoint on your tracking platform that accepts a conversion event from a third party. It's sometimes called a server-to-server (S2S) postback, a conversion pixel alternative, or a "callback." The important distinction: a pixel loads in the user's browser and reports back from there; a postback is fired by a server that already knows the conversion happened. The browser is out of the loop.

The URL carries data in its query string. At minimum it needs a click identifier so the tracker knows which click converted. Typically it also carries the payout, the conversion status, and sometimes a transaction ID for deduplication. A representative postback looks like this:

https://track.yourdomain.com/postback?cid={click_id}&payout={payout}&txid={transaction_id}&status=approved

The {click_id} placeholder is filled in by the network with the value it received when the user clicked your tracking link. Everything else is metadata you can use downstream for reporting and reconciliation.

How does a postback URL work, step by step?

The flow has six steps. Read them once and the rest of this article — parameters, setup, debugging — becomes obvious.

  1. You generate a tracking link in your tracker. It contains a unique click ID parameter, usually named something like click_id, cid, or subid depending on the network's convention.
  2. The visitor clicks your ad and lands on the tracking link. The tracker records the click — timestamp, geo, device, user agent, traffic source, sub-IDs — and assigns it a click ID.
  3. The tracker redirects to the offer URL, appending the click ID into the network's tracking parameter. The network now stores that ID alongside the visitor's session.
  4. The visitor converts. The offer platform confirms the conversion — this might be instant or after a hold period for approval.
  5. The network fires the postback URL you configured in its interface, substituting the stored click ID and payout into the placeholders. This is an HTTP request from the network's server to yours.
  6. Your tracker receives the request, looks up the click ID, and records the conversion against that click. From that point, the conversion appears in your campaign reports, revenue totals, and EPC calculations.

Because step 5 is server-to-server, it works even if the user closed the tab, switched devices mid-funnel (assuming the network supports cross-device matching), or has cookies disabled. That's the entire reason postbacks exist. If you want the broader picture of how click and conversion data fit together, read click tracking vs conversion tracking — what's the difference?

What do the parameters in a postback URL actually mean?

Networks use different names for the same concepts. Here's the mapping you'll encounter most often, and what each field does in practice.

PurposeCommon namesWhat it does
Click identifierclick_id, cid, subid, clickid, aff_subRequired. Matches the conversion to the click the tracker recorded.
Payout / revenuepayout, amount, revenue, sale_amountRecords the value of the conversion so you can compute revenue and EPC.
Statusstatus, event, typeDistinguishes approved, pending, rejected, or different event types (lead vs sale).
Transaction IDtxid, transaction_id, order_idOptional but strongly recommended. Prevents duplicate conversions from double-fires.
Currencycurrency, currency_codeNeeded if you run offers in multiple currencies and want accurate revenue totals.

Two rules save you hours. First, the parameter name in the postback URL must match what your tracker expects — not what the network calls it. Second, the click ID placeholder in the postback must be the exact macro the network uses for the value it stored. If you configure {click_id} but the network uses {subid}, the tracker receives an empty string and silently drops the conversion. No error, no alert — just missing data.

Postback URL vs conversion pixel: which should you use?

Use a postback. The pixel still has a place in specific situations, but for affiliate performance marketing, S2S postbacks are the default because they're more reliable and more accurate.

  • Postback: fired from the network's server, immune to ad blockers and browser cookie restrictions, works for long approval cycles and delayed conversions, supports deduplication via transaction ID.
  • Pixel: fired from the user's browser, vulnerable to blockers and third-party cookie limits, useful when the offer platform can't fire server-side postbacks (rare now), or as a redundant signal for debugging.

If you're running offers where cookies are unreliable — iOS traffic, in-app browsers, privacy-hardened browsers — read how to track affiliate conversions without cookies. The postback is the core of that answer.

How do you set up a postback URL in Adtraxo?

Postback conversion tracking is a Pro feature on Adtraxo. Here's the full sequence, end to end.

  1. Create the tracking link for the offer in Adtraxo, choosing your traffic source and campaign. If this is your first time, how to set up your first tracking link in 5 minutes walks through it.
  2. Open the offer's postback settings in Adtraxo. The platform generates a postback URL with the correct parameter names already in place — you don't need to construct it by hand.
  3. Copy the postback URL and paste it into the affiliate network's postback / conversion tracking field. Replace any placeholder tokens with the network's own macros for click ID, payout, and transaction ID.
  4. Fire a test conversion. Most networks have a test postback button; if not, run a low-value test conversion yourself. Confirm the conversion appears in Adtraxo against the correct click.
  5. Check the click ID round trip. In Adtraxo, open the click log and confirm the click ID recorded matches what the network stores. If it's blank on either side, the integration is broken.
  6. Add sub-IDs if you're splitting traffic across sources, creatives, or placements. Sub-IDs let you pass custom parameters through the click and see them in the conversion report. See Sub-ID tracking explained: how to pass custom parameters.

Once conversions are flowing, the reporting side is where the value shows up. In Adtraxo, each campaign shows conversions, revenue, and EPC alongside geo and device breakdowns, so you can see which placements actually paid. If you're not yet sure how to read that number, how to measure EPC and why it matters for affiliate campaigns covers it.

What are the most common postback URL mistakes?

Three failure modes account for almost every broken integration. Check them in this order when conversions don't appear.

1. Placeholder mismatch

The postback URL uses {click_id} but the network only supports {subid}. Result: the tracker receives an empty click ID, can't match it, and drops the event. Fix: check the network's documentation for its exact macro names and map them one by one.

2. URL encoding problems

If the postback URL contains a callback parameter that itself has a query string, the ampersands need encoding as %26. Unencoded ampersands truncate the URL and the tracker only receives the first parameter. Fix: encode nested parameters, or use the tracker's built-in generator which handles it.

3. Duplicate fires

Some networks fire the postback on both pending and approved status, or retry on timeout. Without a transaction ID, the tracker records two conversions for one sale and your EPC looks inflated. Fix: always include txid in the postback and enable deduplication in the tracker.

If you've checked all three and conversions still don't show, test with a manual HTTP request to the postback URL using a known click ID. If the tracker records the conversion, the problem is on the network side; if it doesn't, the problem is in the URL configuration. This kind of isolation is faster than reading logs.

How do postbacks interact with fraud detection?

A postback is only as trustworthy as the click behind it. If you're buying traffic from PropellerAds, EvaDav, RichAds, or solo ad vendors, you'll get junk clicks. Adtraxo's Pro plan includes fraud detection that flags IP velocity, datacenter IPs, bot user agents, uniqueness conflicts, and invalid referers — before those clicks convert. Postbacks then record conversions against clean clicks, so your EPC and ROI numbers reflect real traffic, not bot noise. Without fraud filtering, a postback integration will happily record conversions from fake clicks and you'll scale a losing campaign.

Can you use postbacks with any traffic source?

Yes, as long as the offer platform supports S2S postbacks, which nearly all affiliate networks do. The traffic source doesn't matter — the postback is between the network and your tracker. What does vary is how you pass sub-IDs through the traffic source's own tracking parameters, so you can attribute conversions back to the specific placement, creative, or solo ad send. If you're running solo ads specifically, how to track solo ad campaigns with a dedicated tracker covers the parameter setup in detail.

One more consideration: custom tracking domains. Running the tracker on your own domain (Adtraxo supports one on Free and unlimited on Pro) keeps postbacks and click links on branded infrastructure, which reduces the chance of a network or browser flagging the tracking link and keeps your click data first-party.

What should you check before choosing a tracker for postbacks?

Three things matter more than the feature list: does the tracker support S2S postbacks with deduplication, does it expose sub-ID parameters you can map to traffic sources, and does it show conversions alongside click data in the same report? If yes to all three, the tracker will do the job.

Pricing is where the options diverge sharply. As of October 2026, Voluum's cheapest plan ("Profit") is $119/month billed annually; RedTrack's "Solo" plan for affiliates is $169/month billed monthly or $118/month billed annually; ClickMagick's "Starter" is $79/month billed monthly or $66/month billed annually; BeMob has a free plan and paid plans from $49/month. Binom and Keitaro have their own licence pricing — check their pricing pages directly. Prices change, so verify before committing.

Adtraxo's Pro plan is $27/month at the founding rate (rising to $47 for new accounts; existing subscribers keep $27) and includes S2S postback conversions, sub-IDs sub1–sub5, A/B split testing, fraud detection, country analytics, and unlimited links, clicks, and domains, with a 30-day money-back guarantee. The Free plan covers 10 tracking links, 5,000 recorded clicks a month, one custom domain, and basic stats with no card required — but postbacks and sub-IDs are Pro features. For a fuller breakdown, see Adtraxo vs Voluum vs RedTrack — honest comparison and best affiliate tracking software in 2026 — compared.

Frequently asked questions

Do postback URLs work without cookies?

Yes. Postbacks are server-to-server, so they don't depend on cookies at all. The click ID is passed through the URL and stored by the network, then returned in the postback. That's why postbacks are the standard for cookieless affiliate tracking.

What's the difference between a postback URL and a webhook?

Mechanically they're similar — both are HTTP requests triggered by an event. A postback is specifically a conversion notification tied to a click ID in an affiliate context. A webhook is a broader integration pattern. In affiliate tracking, the terms are often used interchangeably, but "postback" implies the click ID matching step.

Why are my conversions showing in the network but not in my tracker?

Almost always one of three things: the click ID placeholder in the postback doesn't match the network's macro, the postback URL has an encoding problem that truncates parameters, or the postback is firing to the wrong endpoint. Test with a manual HTTP request using a known click ID to isolate which side is failing.

Can I use a postback URL with multiple offers?

Yes. Each offer gets its own postback URL generated in the tracker, or you can use a single postback with an offer identifier parameter. The important thing is that each postback carries the correct click ID so conversions land against the right click and campaign.

Is postback tracking available on Adtraxo's Free plan?

No. S2S postback conversions and sub-IDs sub1–sub5 are Pro features on Adtraxo. The Free plan covers 10 tracking links, 5,000 recorded clicks a month, one custom domain, and basic stats. Pro is $27/month at the founding rate and includes postbacks, fraud detection, A/B split testing, and country analytics.

Ready to stop guessing which clicks converted? Set up a postback URL in Adtraxo and see every conversion attributed to the click, campaign, and sub-ID that produced it. Start free at adtraxo.com — no card required — and upgrade to Pro when you're ready for S2S postbacks and fraud detection.

Track your affiliate campaigns for free

Clicks, conversions, fraud detection — all in one tracker.

Get started free →

Not ready for an account? Get the Tracking Domination Playbook — free, just your email.