Conversion Tracking for Affiliates: Postbacks, Pixels, UTMs and Sub-IDs Explained

Affiliate tracking is really a chain of handoffs. A visitor clicks your link, lands on the advertiser’s page, and either converts or doesn’t. The entire discipline of conversion tracking exists to answer one question with confidence: which of my traffic sources produced this result? Everything else — postbacks, pixels, UTMs, sub-IDs — is machinery for carrying identity across that chain without losing it.

When any link in the chain breaks, you don’t just lose a data point; you lose the ability to make spending decisions.

The Four Mechanisms and What Each One Does

It helps to separate the tools by what they carry and who reads them.

• UTMs are query parameters appended to a URL (utm_source, utm_medium, utm_campaign, and so on). They label a click for analytics platforms like Google Analytics. They are descriptive, not identifying — they tell you “this came from Facebook, campaign X,” not “this is visitor 8f3a.”
• Sub-IDs are the affiliate network’s version of the same idea. Most networks give you a parameter (often sub1 through sub5, or s1–s5) that you fill with your own value. Whatever you put there comes back in the network’s conversion report, letting you map a sale to a specific source, ad, keyword, or creative.
• Pixels are a snippet of JavaScript or an image tag that fires in the browser when a conversion happens. The browser loads it, and it reports back to whoever owns the pixel — the advertiser, the network, or your own tracker.
• Postbacks (server-to-server, or S2S) are an HTTP request sent directly from one server to another when a conversion is recorded. No browser involved.

The distinction between pixels and postbacks is the one that matters most, and it’s worth understanding why.

Why Postbacks Usually Beat Pixels

A pixel depends on the user’s browser. That means it depends on cookies surviving, on the page actually loading the tag, on no ad blocker or browser privacy setting interfering, and on the user not closing the tab before the tag fires. Modern browsers have made all of these less reliable over time.

A postback depends on two servers talking to each other. The affiliate network’s server tells your tracking platform’s server “conversion happened, here’s the sub-ID and the payout.” That conversation happens regardless of what the user’s browser does afterward. For most affiliate setups, postbacks are the more durable choice, and pixels are a fallback or a supplement.

The trade-off: postbacks require configuration on both ends. You need a postback URL from your tracker, and you need to paste it into the network’s postback settings (or have the network support it at all). Some networks only offer pixel-based tracking, which forces your hand.

How the Sub-ID Chain Actually Works

Here’s the mechanic in sequence, because it’s easier to see where things break when you trace it:

1. You generate a tracking link in your tracker. It contains a unique click ID.
2. You append that click ID into the affiliate link’s sub-ID parameter, so the network receives it.
3. The network stores the sub-ID against that click.
4. When the user converts, the network fires a postback containing the sub-ID and conversion details.
5. Your tracker matches the sub-ID to the original click and attributes the conversion to the correct source, ad, and campaign.

If step 2 is wrong — say you put a static value in the sub-ID instead of the dynamic click ID — every conversion comes back looking identical, and your reporting collapses into a single undifferentiated bucket. This is one of the most common setup errors, and it’s silent: the conversions still register, they just can’t be traced.

Where UTMs Fit, and Where They Don’t

UTMs are excellent for understanding traffic behavior in an analytics platform — bounce rates, session duration, which landing page variant holds attention. They are poor at conversion attribution for payouts, because they live in the URL and get stripped or overwritten by redirects, and because analytics platforms measure sessions, not affiliate conversions.

A practical division of labor: use UTMs to analyze traffic quality and on-site behavior, and use sub-IDs plus postbacks to attribute revenue. Don’t ask one system to do the other’s job.

Choosing a Tracking Approach

The right setup depends on your scale and how much control you have over the funnel.

• Few campaigns, one network, simple offers: the network’s built-in sub-ID reporting may be enough. You get conversion counts by source without running your own tracker.
• Multiple networks or traffic sources: a dedicated tracker becomes worthwhile, because it normalizes click IDs and postbacks across networks into one reporting view.
• Running your own landing pages: you’ll want both a tracker and a way to pass the click ID through your page to the offer, so the chain survives the extra hop.
• Link-management plugins (the WordPress category that includes tools like Pretty Links and ThirstyAffiliates) handle link cloaking and basic click counts, but they are not conversion trackers — they generally won’t reconcile postbacks.
• Link shorteners (Bitly, Rebrandly and similar) are for clean, branded URLs and click analytics, not for affiliate conversion attribution.

The honest trade-off across all of this: more tracking layers mean more precision but also more places for the chain to break. Every redirect, every page load, every parameter you forget to pass is a potential leak. The goal isn’t maximum complexity — it’s a chain you’ve actually tested end to end, from click to confirmed conversion, so you know the data you’re optimizing against is real.