What has to be tracked
Four facts have to be captured for a commission to be calculated correctly. Which partner sent the visitor, usually as a partner identifier issued by the network or platform. Which click, a unique identifier that lets the platform tie a specific visit to a later conversion and tell repeat clicks apart. What happened: the outcome the programme pays for, whether a sale with its value, a qualified lead, a trial, an install or a subscription. Whether it stood: the later status of the outcome, after returns, cancellations, fraud checks or lead qualification.
Most programmes also capture context that matters for payment and reporting. The order value and currency, so that a percentage commission can be calculated. Whether the customer is new or returning, if the programme pays differently for each. Product categories, if commission varies by margin. A coupon code, if one was used. A sub-identifier the partner passes through, so that it can see which of its own pages or placements worked.
The cost per action (CPACost of each conversion.) basis of the model makes accuracy a commercial issue rather than a reporting nicety. Under-tracking means partners are underpaid and lose interest; over-tracking means the business pays for outcomes it would have had anyway. The aim of the setup is to record exactly what the terms say is payable: no more, no less. Who deserves the credit when other channels were involved is a separate question, handled in affiliate attribution and deduplication.
Tracking links and parameters
The partner never links directly to the product page in most setups. It links to a tracking URL that the platform issues, which logs the click and redirects to the destination, or to the destination itself with parameters appended that the advertiser's site reads on arrival.
| Element | What it carries | Who sets it | What breaks it |
|---|---|---|---|
| Partner identifier | Which affiliate sent the click | Platform, at partner approval | Partners editing links by hand; shared links between partners |
| Click identifier | A unique token for this click | Platform, at the moment of the click | Redirect chains that drop query strings |
| Campaign or creative identifier | Which offer, banner or feed item was used | Platform or advertiser | Links reused across campaigns |
| Sub-identifier | The partner's own placement or page reference | Partner | Partners not using it, or passing personal data into it |
| Destination URL | The landing page | Advertiser or partner, within the terms | Deep links to pages that later move |
| Analytics parameters | Source, medium and campaign for the advertiser's own analytics, often as UTMURL tags identifying traffic source. tags | Advertiser, sometimes appended by the platform | Inconsistent naming across partners |
Two practical points follow. First, every redirect between the partner and the landing page is a place where parameters can be lost: a site moving to a new domain, a regional redirect, a consent page or a link shortener. Test the full path whenever the site changes. Second, the analytics tags and the affiliate identifiers do different jobs. Analytics tags tell the advertiser's analytics where the visit came from; the click identifier is what the affiliate platform needs to pay the partner. A visit can be correctly tagged for analytics while the platform never sees the conversion, or the other way round. On the partner's own pages, an affiliate link is also a paid link for search engines, and the guide to outbound links and link attributes covers how to qualify it.
When a site change is a whole new site, domain or checkout, the tutorial on protecting affiliate tracking through a website migration puts partner destinations, redirect tests, the postback and the partner feed into the project before launch day.
Cookies, windows and browser limits
Once the click is logged, something has to remember it until the customer converts, which may be minutes or weeks later. Traditionally that was a cookie. The platform set a cookie on its own domain during the redirect, and when the confirmation page loaded the platform's pixel, the pixel read the cookie and recorded the conversion against the partner.
That approach depends on a cookie that belongs to a domain other than the one the customer is visiting, and browsers have spent several years restricting exactly that. Some block such cookies outright; others shorten the life of cookies set in certain ways, or limit tracking parameters in links. Ad blockers and privacy extensions block many platform pixels too. The practical effect is that cookie-only tracking undercounts, and the undercounting is uneven: worse on some browsers and devices than others, so some partners are hit harder than others.
The common response is to store the click identifier on the advertiser's own domain, read from the landing page URL and held in a first-party cookie or in the session, then passed to the order record at checkout. The identifier then survives as long as the advertiser's own systems keep it.
The cookie window (also called the referral or return period) is a separate, commercial setting. It is how long after a click a conversion still counts for that partner. It is set in the programme terms and enforced by the platform, whatever the technology used to remember the click. Choosing it is part of commission design, covered in commission structures and partner economics. To set the length from the programme's own orders, the tutorial on setting the affiliate lookback window reads the delay between click and order for each partner type and prices each option.
Server-side postbacks and APIs
A postbackA server-to-server message reporting a conversion, install or in-app event back to the ad network or affiliate platform that should receive credit. (also called server-to-server tracking) removes the browser from the conversion step. When an order is placed, the advertiser's server, or a server-side tag managerRunning tags on a server the business controls instead of in the visitor's browser. acting for it, sends a message directly to the affiliate platform. The message carries the click identifier stored earlier and the order details. The platform matches the identifier to the logged click and records the conversion.
Variants exist. Some platforms provide a conversion API (Conversions APIServer-side event sharing with Meta.) that the advertiser's systems call with the order data. Some take scheduled file uploads of orders. Many advertisers run both a postback and a browser pixel, with the platform removing duplicates, so that the pixel acts as a backup while the postback is the main record. The server-side tagging basics guide explains how a server container can sit between the site and its vendors and send these events.
Server-side tracking is more reliable, but it adds responsibilities. The advertiser now owns the integration and has to monitor it; when the order system changes, the postback can silently stop. It also makes the advertiser the one deciding what data leaves its systems, which is the point at which privacy rules apply most directly.
Postbacks also make status updates possible. When an order is returned or cancelled, the advertiser can send an update that adjusts the commission, rather than relying on someone to edit a spreadsheet before payment.
Consent and privacy constraints
Affiliate tracking reads and stores identifiers on the customer's device and shares data about their activity with a third party, so it falls within privacy and electronic communications rules in many markets. This guide does not teach the law; the privacy and consent guide covers the general position for measurement, and the UK Information Commissioner's Office publishes guidance on direct marketing and the related rules on cookies and similar technologies. Take advice for your own markets.
In general direction, a few practical consequences apply to most programmes. Affiliate tracking is usually treated as non-essential, so where consent is required, the click identifier should not be stored or shared until the customer has agreed. That means some conversions will never be attributable to a partner, and the programme terms should say so, so that partners are not surprised. The consent banner and the tracking setup must agree: a platform pixel that fires regardless of the customer's choice is a compliance problem, not a tracking win.
Moving to server-side tracking does not remove the need for consent; it changes where the data flows, not whether the customer agreed. Minimise what is sent. The platform needs the click identifier, the order reference, the value and the status; it does not need the customer's name or email. Partners should be told never to pass personal data in sub-identifiers.
Validation and commission approval
A tracked conversion is not yet a commission. Between the two sits validation: the advertiser reviews pending conversions and approves, adjusts or rejects them before the platform invoices and pays.
A subscription box validates a month of affiliate orders
Pantry Parcel, an invented food subscription business, runs its programme on a network with a server-side postback and a browser pixel as backup. In March the platform shows 2,310 pending conversions. Matching them against the order system, Pantry Parcel finds 46 duplicates where both the pixel and the postback fired and the platform had not deduplicated them, 188 orders cancelled within the trial period its terms exclude, 71 orders from customers who were already subscribers, which the terms pay at a lower rate, and 9 orders from a single partner's own staff, which the terms prohibit. It rejects 243, adjusts 71 and approves 1,996. The review takes a morning because the postback already carries the order reference.
The rules for validation belong in the programme terms before the first partner joins. Typical grounds for rejection are returns and cancellations within a stated period, duplicate or test orders, orders that break the terms (for example, a coupon used outside its permitted partner), and suspected fraud. A validation periodHow long the business has to review an affiliate conversion before approving its commission, long enough to cover returns and cancellations. long enough to cover returns protects the business; one much longer than needed delays payment and frustrates partners.
Two habits make validation workable. Carry the order reference in every conversion, so that platform records can be matched to the order system automatically rather than by hand. And reconcile totals every period: the platform's approved conversions, the order system's qualifying orders and the analytics view of affiliate traffic should tell a consistent story. Where they diverge, the reasons are usually tracking gaps or AttributionAssigning conversion credit to touchpoints. differences, which the measurement section explains. The comparison of networks and in-house programmes covers how much of this work each type of platform does for you, and the fundamentals hub places tracking among the other foundations.
Where the platform records far more orders than analytics credits to the channel, the diagnosis of affiliate sales not matching analytics starts from the order reference in each postback and classifies every gap.
Before a programme opens, or moves to a new platform, the affiliate programme launch checklist asks for a test click-to-sale journey, a documented lookback window and a deduplication rule while they are still cheap to fix.
Common mistakes
- Relying on a browser pixel alone. It undercounts unevenly and fails silently. Make a server-side postback the main record and keep the pixel as a backup.
- Not testing the full redirect path. Site migrations, regional redirects and consent pages strip parameters. Test a partner link end to end after every significant site change.
- Confusing analytics tags with affiliate identifiers. A correctly tagged visit in analytics does not mean the platform recorded the conversion. Check both.
- Firing tracking before consent. Where consent is required, the identifier waits for it. A setup that ignores the customer's choice creates a compliance risk the commission does not justify.
- Paying before validation. Approving every pending conversion automatically pays commission on returns, duplicates and fraud. Validate against the order system each period.
- Sending more data than the platform needs. The click identifier, order reference, value and status are enough. Personal data has no place in postbacks or sub-identifiers.
- Leaving the integration unmonitored. A postback that breaks during a checkout update can go unnoticed for weeks. Alert on sudden drops in recorded conversions per partner. When a partner reports sales the platform never recorded, the tutorial on tracing missing affiliate conversions works the gap from the partner's evidence to a fix.
