Postback URL vs tracking pixel — which should an affiliate use?

12 min readUpdated Nov 6, 2026

Postback URL vs tracking pixel — which should an affiliate use?

If you can only have one, use a server-to-server postback URL. A postback fires from the advertiser's server to your tracker, so it does not depend on a browser loading an image, surviving an ad blocker, or keeping a cookie alive for three weeks. A tracking pixel is a 1×1 image or script that fires in the browser — it is the fallback when your affiliate network or offer does not support a postback, and it is genuinely useful for landing-page behaviour. For counting conversions and revenue, the postback wins almost every time. This guide covers postback vs pixel tracking from the perspective of someone who has debugged both at 2am while traffic was still spending.

What is the actual difference between a postback and a pixel?

A pixel is a client-side request. When a conversion happens, the advertiser's page renders an image tag (or runs a script) pointing at your tracker with a click ID attached. Your tracker logs it because a browser asked for it.

A postback is a server-side request. When a conversion happens, the advertiser's backend makes an HTTP call to a URL on your tracker — again with the click ID attached — and your tracker logs it because a server asked for it.

Same data, different messenger. That difference decides almost everything about reliability:

  • Who has to cooperate. A pixel needs the user's browser, their extensions, their network, and the page's JavaScript to all behave. A postback needs one outbound HTTP request from a server that is already processing the conversion.
  • What can block it. Ad blockers, privacy browsers, ITP-style cookie expiry, script errors, and users closing the tab before the pixel renders all kill client-side tracking. Almost nothing kills a server request except a misconfiguration.
  • What it can carry. Postbacks can pass payout, currency, conversion type, and status cleanly because you control the query string. Pixels can too, but they are more exposed to truncation and encoding problems.
  • When it fires. A pixel often fires on page load of a thank-you page. A postback fires when the advertiser's system records the event — which may be before or after that page renders, depending on their setup.

The practical upshot: postback tracking is the default for anyone running paid traffic at volume. Pixel tracking is the emergency lane.

Why postback tracking is the default for paid traffic

Three reasons, and they compound.

1. It survives the browser

Your traffic sources — PropellerAds, EvaDav, RichAds, Taboola, MGID, solo email drops — send you users on browsers you do not control. A meaningful share run ad blockers, privacy-focused browsers, or aggressive tracking prevention. Every one of those users can still convert. With a pixel, a slice of those conversions silently vanish from your tracker while still showing up in the affiliate network's report. You then optimise against incomplete data and cut campaigns that were actually profitable.

2. It gives you clean revenue

A postback URL is just a URL. You can append &payout={payout}&currency={currency}&status={status} and your tracker receives the real number, not an estimate. That is what makes ROI reporting trustworthy rather than a guess built on a flat assumed payout. There is a full walkthrough in how to pass payout values in a postback so your ROI numbers are real.

3. It separates event types

Most offers have more than one thing worth counting: a lead, a sale, a rebill, a chargeback. A postback can carry a conversion type parameter so each lands as a distinct event in your tracker. A pixel can technically do this too, but you end up maintaining multiple pixel URLs on the advertiser's side, which is more fragile and harder to audit. See how to track leads and sales as separate conversion events.

Where pixels still earn their place

Do not delete your pixels. They solve problems postbacks cannot.

  • The network has no postback option. Some smaller networks, some direct advertisers, and a lot of custom offer walls only give you a pixel. If that is all you have, use it and accept the leakage.
  • You need landing-page behaviour. A pixel on your own pre-lander tells you who actually arrived and scrolled, which is different from who clicked. Adtraxo's one-line arrival snippet does this on any plan: it shows which clicks loaded the page in a real browser, so you can spot bot traffic and broken redirects before they eat your budget.
  • You are testing the chain. A pixel is a fast sanity check that a click ID is being passed through the funnel at all. If the pixel fires with the right click ID but the postback never arrives, you have narrowed the fault to the advertiser's server side.
  • Redundancy. Running both, where the network allows it, gives you two independent logs to compare. When they disagree, you learn something — usually that a chunk of users are blocking client-side requests.

How to set up a postback URL (step by step)

The mechanics are the same on any tracker. Here is the sequence, using Adtraxo's Pro postback conversions as the example, since it is the plan where S2S postbacks and sub-IDs are available.

  1. Get your click ID parameter straight. Your tracker appends a unique click ID to the offer URL — commonly as sub1 or a dedicated click_id parameter. Whatever the network calls it, that exact parameter must come back in the postback. If you are hazy on why, read what is a click ID, and why conversions go missing without one.
  2. Build the postback URL in your tracker. In Adtraxo, open the campaign, go to the postback/conversion settings, and copy the generated URL. It will look roughly like https://yourdomain.com/postback?cid={click_id}&payout={payout}&status={status} — the macro names in curly braces are placeholders the network fills in.
  3. Paste it into the affiliate network. Most networks have a global postback field plus a per-offer override. Set the global one first, then override on any offer with different macro names.
  4. Check the macro names against the network's docs. This is the single most common failure. One network uses {click_id}, another {sub1}, another {subid}. A postback with the wrong macro name fires successfully and logs nothing useful.
  5. Use a custom tracking domain. Serving the postback endpoint from your own domain avoids edge cases where a shared tracker domain gets filtered, and it keeps your links clean. Adtraxo includes one custom domain on Free and unlimited domains on Pro.
  6. Fire a test conversion. Use the network's test conversion tool if it has one, or run a real cheap conversion yourself. Do not skip this — see how to test a postback URL before you send paid traffic.
  7. Confirm the conversion appears with the right payout and click ID. If the click ID matches and the payout is correct, your chain is sound. If the click ID is blank, go back to step 1.

How to set up a pixel (and what to watch for)

  1. Generate the pixel URL in your tracker with the click ID macro in place.
  2. Place it on the conversion page — the thank-you page, the order confirmation, wherever the event is definitive. Not the offer landing page.
  3. Fire it once per conversion. Duplicate pixels on a page that reloads will inflate your numbers. If you cannot control reloads, ask the advertiser to fire it server-side instead.
  4. Verify with a browser devtools network tab that the request actually goes out on a test conversion, and that the click ID in the request matches the click you started with.

The classic pixel failure is a thank-you page that renders before the conversion is recorded, or a page the user can refresh. Both produce inflated or zero conversions depending on which way it breaks.

Postback vs pixel tracking: side-by-side

Postback (S2S)Pixel (client-side)
Fires fromAdvertiser's serverUser's browser
Blocked by ad blockersNoOften
Depends on cookiesNoFrequently
Carries payout cleanlyYesYes, but more fragile
Requires network supportYesYes, but more widely offered
Good for landing-page behaviourNoYes
Typical discrepancy vs networkSmallLarger

If your network and tracker numbers disagree, the pixel is usually the first suspect. There is a full diagnosis in why your affiliate network and your tracker report different conversions.

What about sub-IDs and UTMs — do they change the answer?

No, but they are related. Sub-IDs (sub1–sub5) are parameters you append to the offer URL to carry your own segmentation — traffic source, creative, placement, email in a sequence. The click ID usually rides in one of them. UTMs are for analytics tools and get stripped or overwritten more often on affiliate hops. If you are deciding between them, UTM parameters vs sub-IDs — which should you use on affiliate links? covers the trade-offs.

For email sequences specifically, the sub-ID is what lets you attribute a sale to the third email rather than the campaign as a whole: how to track which email in your follow-up sequence drives affiliate sales.

When the postback does not fire

Work in this order, because each step eliminates a layer:

  1. Did the click record? If the click is missing, the problem is upstream of the conversion entirely.
  2. Did the click ID reach the network? Check the network's click log for the sub-ID value.
  3. Is the network firing anything at all? Check its postback log or test tool.
  4. Is the macro name correct? Compare character by character.
  5. Is the endpoint reachable? Curl the postback URL with dummy values and see what your tracker returns.

The expanded version of this sequence is in postback not firing: the checks to run, in order, and the broader sweep is in affiliate conversions not tracking? A step-by-step troubleshooting guide.

What this costs you

Postback tracking and sub-IDs are Pro features on Adtraxo — $27/month at the founding rate, rising to $47 for new accounts, with existing subscribers keeping $27. That buys unlimited links, clicks and domains, fraud detection and rules, A/B split testing, sub1–sub5, country analytics and S2S postback conversions, with a 30-day money-back guarantee and cancellation any time. The Free plan covers 10 tracking links, 5,000 recorded clicks a month, 1 custom domain and basic stats with no card — useful for learning the interface, but it will not run postback conversions.

For context on what the market charges, as of October 2026: Voluum's cheapest plan, Profit, is $119/month billed annually; RedTrack's Solo plan is $169/month billed monthly or $118/month billed annually; ClickMagick Starter is $79/month billed monthly or $66/month billed annually; BeMob has a free plan with paid plans from $49/month. Prices change, so check each vendor's page. Binom and Keitaro have their own licence pricing — go to their pricing pages directly.

The point is not the price comparison. It is that postback tracking is table stakes, not a premium add-on, and any tracker that makes you fight for it is costing you in misallocated ad spend long before it costs you in subscription fees.

Frequently asked questions

Can I use a postback and a pixel at the same time?

Yes, and on high-volume campaigns it is worth doing where the network supports both. The postback is your source of truth for optimisation; the pixel gives you a second log to compare against. If the two disagree by a wide margin, you have a client-side blocking problem worth knowing about. Just make sure you do not count both as separate conversions in the same tracker — deduplicate by click ID.

Why does my pixel show conversions but my postback shows none?

Almost always a macro mismatch or an unreachable endpoint. The pixel fires in the browser with whatever click ID the page has; the postback fires server-side with whatever the network's backend substitutes into your URL. If the macro name in your postback does not match what the network expects, it fires with an empty or literal value and your tracker cannot match it to a click. Curl the URL with test values to confirm the endpoint works, then compare macro names against the network's documentation.

Is postback tracking blocked by ad blockers?

No. Ad blockers operate in the browser and block client-side requests. A postback is an HTTP call between two servers, so browser extensions never see it. This is the core reason postback vs pixel tracking is not really a fair fight for conversion counting.

Do I need a custom domain for postbacks?

Not strictly, but it helps. A custom tracking domain keeps your postback endpoint on a domain you control, which avoids edge cases where a shared tracker domain gets filtered or flagged, and it makes your links look consistent. Adtraxo includes one custom domain on Free and unlimited domains on Pro.

What if my affiliate network only supports pixels?

Use the pixel and compensate for the leakage. Expect your tracker to under-report relative to the network, and reconcile against the network's numbers when you judge campaign performance rather than trusting the tracker alone. If the network grows enough to matter to your business, ask them to add postback support — most will, because their other affiliates want it too.

Ready to run postbacks properly? Set up your first campaign with server-to-server conversions, sub-IDs and fraud detection at adtraxo.com.

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.