If you want to know how to test affiliate tracking, the short version is this: click your own link exactly as a visitor would, complete a real or program-approved test conversion, and confirm that the click, the conversion, your sub-IDs and any postback all appear correctly, with the right values, in both the program's dashboard and your own tracker. Then repeat it on mobile, in Safari and across devices before you commit meaningful traffic.

It sounds obvious, yet most lost commissions we hear about come from setups nobody tested end to end. This guide gives you a pre-launch test plan you can run in an afternoon, what good results look like, and the red flags that should make you pause.

Why you should test affiliate tracking before launch

Tracking is the only evidence you have that you earned a commission. If a click ID is dropped in a redirect, a postback macro is misspelt or a program's cookie is blocked in one browser, the sale still happens but you are not credited. You rarely find out from the program; you find out weeks later when your earnings look thin against your traffic.

Testing first protects you in three ways:

  • Money: you avoid paying for traffic that converts but never reports.
  • Leverage: you have documented evidence if you later need to raise a discrepancy with an affiliate manager.
  • Trust: you learn how a program behaves (speed of reporting, honesty about rejected sales) before your income depends on it.

What to prepare before your test

Gather these before you click anything. A test without them produces results you cannot interpret.

  • Your exact affiliate link, including every parameter, copied from the program's link generator.
  • Written confirmation from the affiliate manager of how test conversions should be done. Many programs ask you to use a test mode or to tell them in advance so a self-referral is not flagged as fraud. Never place a fake order or sign-up without permission.
  • The program's cookie or attribution window, attribution model (usually last click) and how long conversions take to appear.
  • Access to your tracker, if you use one, with the program set up as an offer and a postback URL configured.
  • A spreadsheet to log timestamp, device, browser, sub-ID used, click ID and what appeared where.

Tip: use a unique sub-ID for every individual test, such as test01-desktop-chrome. It makes each test conversion unmistakable in reports and saves arguments about which click produced which sale.

A step-by-step affiliate tracking test plan

Run the steps in order. Each one isolates a different part of the chain, so when something fails you know where.

  1. Inspect the link. Paste it into a browser with developer tools open (Network tab, "preserve log" enabled). Follow every redirect. Note each hop's domain and confirm your affiliate ID and sub-ID survive to the final landing page or are stored by the program before the last hop.
  2. Check the click registers. Within a few minutes, the program's click report should show one more click against your sub-ID. If it does not, stop here; nothing downstream will work.
  3. Complete a test conversion. Follow the agreed method: a test-mode payment, a free sign-up, or a low-value real purchase the manager has approved. Record the order or user ID.
  4. Confirm the conversion in the program dashboard. Check that it is attributed to your account, shows the right sub-ID and has the correct commission type (CPA, revshare or lead).
  5. Confirm the postback. If you use a tracker, the conversion should appear there with the matching click ID and payout. See our explainer on what a postback URL is and how it works if this part is new.
  6. Repeat on other devices and browsers. At minimum: desktop Chrome, iPhone Safari, Android Chrome, and one in-app browser if you buy social or app traffic.
  7. Test cross-device. Click on mobile, convert on desktop while logged in to the same account if the product allows it. Ask the program whether it supports this; many cannot credit it.
  8. Measure latency. Note how long each event took to appear. You will need this when judging campaigns in real time.

Check that sub-IDs pass back correctly

Sub-IDs are the parameters you attach to a link to identify the page, placement or campaign that produced a click. If they do not come back in reports and postbacks, you cannot optimise anything. Our guide to sub-IDs and naming conventions covers how to structure them.

During testing, check:

  • How many sub-ID slots the program supports and their maximum length.
  • Which characters survive. Some systems strip hyphens, full stops or uppercase letters, or truncate long values.
  • Whether sub-IDs appear in click reports, conversion reports, exports and the API, or only some of these.
  • Whether each sub-ID slot can be returned in a postback macro.

A sub-ID that shows up in the click report but is blank on the conversion is a common and serious fault. It usually means the program stores the click and the sale in separate systems that are not joined properly.

Test postbacks and server-to-server tracking

For media buyers, the postback is the most important part of the test. A browser pixel can be blocked by ad blockers, consent tools and browser privacy features; a server-to-server postback is not affected by those. Our comparison of server-to-server and pixel tracking explains the trade-offs.

A sound postback test checks that:

  • The postback fires for every conversion type you are paid for (sign-up, first payment, rebill), or you know which ones it does not cover.
  • The click ID returned is exactly the one your tracker sent, with no URL encoding damage.
  • The payout value and currency are correct. A EUR payout reported as USD will distort your ROI.
  • Reversals or chargebacks are reported, either by a negative postback or a status update, or you know they are not.
  • Duplicates are handled: a page refresh on the thank-you page should not create a second conversion.

Most trackers have a postback log. Use it. If the log shows the postback arriving with an empty or literal macro such as {clickid}, the program has not substituted its value and the macro name is wrong.

Test across browsers, devices and consent states

Tracking that works on your desktop may fail for the majority of your audience. Pay special attention to:

  • Safari and iOS: Intelligent Tracking Prevention limits how long script-set cookies last, and Private Browsing strips some known click identifiers. Read our guide to Safari ITP and affiliate tracking for the details.
  • Cookie banners: if the program's site uses a consent tool, test once accepting and once rejecting cookies. If tracking only works after acceptance, ask whether the program has a server-side fallback.
  • In-app browsers: social and messaging apps open links in their own browser, which can lose sessions when the user switches to a native browser to pay.
  • Ad blockers: run one test with a mainstream blocker enabled to see whether the program's tracking domain is on common block lists.

Cross-device sales deserve their own question to the manager: if a visitor clicks on a phone and subscribes on a laptop later, will you be paid? If the answer depends on the visitor logging in, you need to know that before you value mobile traffic.

Check reporting latency and data quality

How fast and how complete the reports are matters as much as whether the conversion is recorded at all. Note:

What to measureWhat good looks likeWarning sign
Click reporting delayMinutesClicks appear hours later or in daily batches only
Conversion reporting delayMinutes to a few hours, stated in writingNo stated timescale, or conversions appear days later without explanation
Sub-ID coveragePresent on clicks, conversions, exports and APIMissing on conversions or exports
Status visibilityPending, approved and reversed clearly labelledConversions silently disappear
Data exportCSV or API with timestamps and IDsScreen-only totals

If you are new to reading these reports, our guide to reading an affiliate dashboard explains clicks, leads and pending sales.

Red flags: when not to trust a program's tracking

A single failed test can be a set-up mistake on your side. A pattern of the following should make you hold back traffic:

  • The manager refuses or ignores requests for a test conversion.
  • Test conversions appear but with the wrong sub-ID or no sub-ID.
  • No postback support, or postbacks only for some conversion types with no explanation.
  • Conversions reported, then removed without a reason code.
  • Reports that cannot be exported or reconciled with your own logs.
  • Large gaps between your tracker's clicks and the program's clicks that nobody can explain. Our guide to tracking discrepancies covers what is normal.

Persistent under-reporting that only affects some affiliates is sometimes called shaving. Our explainer on how to spot affiliate shaving sets out the evidence to collect.

Worked example: a pre-launch test log

Here is a hypothetical log from a publisher testing a cam program before a paid push. The numbers are illustrative, not from a real program.

TestDevice / browserClick shownConversion shownSub-ID on conversionPostback
test01Desktop ChromeYes, 1 minYes, 4 minYesYes, correct payout
test02iPhone SafariYes, 1 minYes, 6 minYesYes
test03Android in-app browserYesNon/aNo
test04Mobile click, desktop sign-upYesNon/aNo

The verdict: desktop and mobile Safari are fine, but in-app and cross-device conversions are lost. The publisher would either avoid in-app social placements for this program or ask the manager whether a login-based or server-side fix exists, and value that traffic accordingly.

Frequently asked questions

Is it allowed to make a test purchase through my own affiliate link?

Only with the program's permission. Self-referrals breach most affiliate terms and may be flagged as fraud. Ask the affiliate manager for a test mode or written approval, and tell them the time and sub-ID of your test.

How long should I wait for a test conversion to appear?

Ask the program for its stated reporting delay and wait at least that long. Clicks usually appear within minutes; conversions on well-run platforms usually follow soon after, but some programs batch-process. If nothing shows after the stated window, raise it with your click ID and timestamp.

Do I need a tracker to test affiliate tracking?

No. You can test using only the program's dashboard and unique sub-IDs. A tracker adds an independent record of clicks and lets you test postbacks, which is essential if you buy traffic.

How often should I re-test?

Re-test whenever the program changes its platform, domain or checkout, when you change your own redirects, and periodically on your top earners. A quick monthly check on the main offers catches silent breaks early.

Next steps

Once a program passes your test, keep the log as a baseline. If figures drift later, our troubleshooting guide on why affiliate conversions are not tracking walks you through the likely causes. If you are choosing the tool to run these tests, compare options in our affiliate tracking platforms directory, or browse more guides in tracking and analytics.