Guides
Part of 6 things to check in affiliate platforms
The affiliate platforms checklist owners actually finish
An affiliate platforms checklist: check program fit, test tracking and exports, set partner and payment rules, and document renewal and exit terms.
Mistake: Trusting an export you have not tested
An untested export is the costliest failure in this affiliate platforms checklist because a totals-only file turns departure into a project rather than a decision. Inspect the actual record during evaluation, since its structure and terms may be difficult to change after signature. Once signed, changing the arrangement may be difficult.
Affiliate networks, partner-marketing suites and standalone tracking tools are different product categories, not interchangeable labels. This checklist gives you tests to run on your own shortlist; it does not report platform-specific results.
Checklist: evaluate an affiliate platform
Check an item only when you have its answer in writing or have saved the test evidence; a sales assurance alone does not count.
- Program fit:Write down the program's goal, its named daily owner and available capacity, the order routes, partner standards, and whether the client or agency owns the program.
- Contract and exit:Confirm who controls the tracking domain, test the export format, and settle notice and post-cancellation terms, including tracking, partner notice, export access and commissions on sales validated after the end date.
- Tracking:Place a test order through every customer order route. Switch devices or wait to test identifier behavior, then record which routes track and how failed matches are explained.
- Export:Open a full data sample and verify partner contact details, historical performance by partner, partner creative and payment history. Confirm the file is readable by a person and loadable by a machine.
- Disputes:Follow an actual dispute through the interface from start to finish, and note whether the process depends on a support ticket.
- Partner rules:Put disclosure and link-placement rules in partner terms before the first partner joins, and keep a record of the policy.
- Payments:Settle the float, validation period, pending-versus-approved visibility, post-payout chargeback responsibility, currency and exchange-rate date, tax paperwork and responsibilities before funds move.
- Renewal:Compare program use and pricing on the same basis. Record whether incrementality was tested; if it was not, state that rather than treating attributed sales as incremental.
- Handover:Record whose name is on the account, who funds payments, who holds partner contacts, what the client receives at handover, and whose terms govern marketplace partners.
Mistake: Choosing a platform before deciding what the program must do
Starting evaluation without settling the program's purpose, ownership, workload, order routes and partner standards creates questions that become harder to answer as the program grows. Decide these points early, then match the platform to the job instead of treating every uncertainty as equally urgent.
- What is the program meant to achieve: reaching audiences you cannot buy directly, generating incremental sales, or providing a payment mechanism for partners you already have? Those aims call for different products.
- Who will run the program day to day, by name, and how many hours will they have? Without a named owner, partners may go unrecruited and rules unenforced.
- Which order routes does the business useweb checkout, app, phone, renewal, in store or marketplace? Each route is either instrumented or invisible.
- What will you do about partners you would rather not have? Deciding after they arrive is harder than deciding beforehand.
- Does the client or the agency own the program? On an agency retainer, that answer determines what happens at the end of the relationship.
If partners enter through a creator marketplace, its standard terms arrive with them. Those terms are rarely identical to yours. Find the mismatch before depending on your own rules or assuming that recruitment meant the partner accepted them as written.
Think of this exercise as setting up a drawer system: the cabinet itself brings no value. Value comes from knowing where each fact belongs before it is filed and who may open that drawer. This keeps evidence tied to decisions and responsibility attached to the person authorized to act.
Mistake: Signing while the contract still hides the exit costs
Signing while the tracking domain, export format and notice arrangements remain assumptions makes the vendor's defaults your practical limits. These are three terms that are hard to reverse after signature, so settle them in the contract before those defaults become the boundary for the program.
Three that close forever
- Tracking domainwhose name is on it
- Export formattested, not promised
- Notice termstracking, partners, export, commissions
The tracking domain. Check the registrant in the domain registration record, sometimes called its WHOIS entry, to learn whose name controls it. Old posts and videos can send traffic for years; if the vendor owns the tracking domain, those links become its asset when you leave. Register your own subdomain at signature; it cannot be done at exit.
The export format, tested rather than promised. Do not accept the existence of an export as proof of portability, because every vendor has one. Open a sample and check for partner contact details, historical performance by partner, the creative used by each partner, and payment history. A usable file must be readable by a person and loadable by a machine.
The notice terms and the period after notice. Agree whether tracking continues, whether partners are told, whether exports stay available after cancellation, and who pays commissions on sales that validate after the end date. Each issue has a default position, and the vendor's default is not written for your program.
Mistake: Treating a sales assurance as a test result
Relying on a vendor's yes leaves you with an assurance rather than a finding. Run the practical checks on every shortlisted platform during evaluation. Compare the results, not the sales answers, so you can see what each product actually records and exposes.
Four evaluation tests
- Place a real order through every order path
- Break the identifier on purpose
- Export everything during the trial
- Read one dispute end to end
| The test | How to run it | What a failure looks like |
|---|---|---|
| Place an order on each available route | Buy something yourself through every customer order path | A route where the partner receives no recorded sale |
| Intentionally disrupt the identifier | Complete a purchase after switching devices or waiting a long time | No explanation of whether matching was attempted |
| Request the complete data file | Ask for the full export while the trial is still open | Totals without the rows behind them, which is a report rather than a record |
| Follow a dispute from start to finish | Ask to see an actual dispute handled in the interface | Only a support-ticket exchange, showing the process depends on people rather than the product |
Agencies commonly omit identifier and export testing. Skipping the export is the costly miss because it decides whether exit is straightforward or becomes a project. A refusal is itself an answer, not a reason to wait. Apply the supplier-comparison principle on a real job with the supplier comparison checklist.
Mistake: Writing partner rules after launch
Writing enforcement rules only after launch lets the first disputed decision establish the standard for the year. Before the first partner joins, state the disclosure requirement and prohibit improper link placement; otherwise, early enforcement sets the policy by habit rather than design.
Rules to set before launch
- Where links may and may not appear
- Whether partners may bid on brand terms
- How coupon, cashback, extension partners are treated
- What counts as incentivized traffic
- Deduplication rule with other paid channels
- First-time rule-breaker policy
In the United States, the Federal Trade Commission's Endorsement Guides (16 CFR Part 255) place responsibility on the advertiser to ensure partners disclose the material connection: the affiliate link and the commission it pays. Put that duty in partner terms before launch, alongside the placement rule, and keep a record that you did.
The hardest policy to draft, and one worth having in writing, concerns link placement fraud: a partner can place a tracking cookie on visitors who never clicked. Cookie stuffing is old, remains common, and is invisible in dashboards that count only conversions. The audience and traffic quality guide explains what detection products can establish and what they cannot; conversion totals alone do not show a click.
Mistake: Settling payment questions at the first payout
Waiting until the first payout to settle money questions leaves the program without agreed answers on timing, validation, reversals, currency or tax paperwork. Decide each point before funds move, using your own returns pattern rather than an industry default as the reference.
- Who holds the float between your funding and the partner payout, and for how long?
- What is the validation window, measured against your own returns pattern?
- Can partners distinguish pending amounts from approved ones? Without that view, they may chase money that was never theirs.
- What happens if a chargeback arrives after a payout has run, and whose loss is it?
- Which currency records the sale, at what rate and on what day? Cross-border programs do not reconcile by accident.
What tax paperwork does the platform collect, and what remains your responsibility? In the United States, collect a W-9 from domestic partners and issue a 1099-NEC at year end, plus a W-8BEN or W-8BEN-E for partners outside the country. The place where the sale is booked determines whether VAT or GST is involved.
Mistake: Renewing because the dashboard credits sales
At renewal, attributed sales are not proof that the program created additional sales. Use what happened in the prior quarter to test incrementality instead of treating a dashboard total as the result; the vendor cannot make that assessment on your behalf.
Renewal holdout decision
Has the program ever been tested for incrementality?
Use the tested incremental figure in the renewal note
Say so in the renewal note, do not repeat attributed figure
List what you used in the last quarter and compare it to what you are paying for. If the pricing meter has changed, ask what the quote would have been using last year's meter, so the comparison reflects what you actually used rather than a shifted basis.
Whether the program adds sales is a holdout question, not a dashboard question; the broader treatment appears in the guide to measurement tooling. If nobody has tested incrementality, say so in the renewal note rather than repeating the attributed figure as if it were incremental.
Mistake: Leaving agency ownership unresolved until the relationship ends
Client-owned and agency-owned programs differ at one precise point: the end of the relationship. Deciding who controls the program only as the relationship ends is too late. Set handover terms at the start so ownership, payment responsibility and partner information do not become last-day disputes.
Record whose name is on the account, whose payment funds the program, who holds the partner contact list and what the client receives on the final day. If partners came from a marketplace rather than direct outreach, establish whose terms govern them too; that answer is usually not yours.
Mistake: Assuming onboarding proves the program can move
A vendor's onboarding checklist is built to get the program live, not to make departure easy. Treating those outcomes as the same leaves exit conditions unresolved, even if setup handled instrumentation thoroughly in the launch plan on paper.
The onboarding list may cover instrumentation thoroughly while leaving exit terms untouched. Review what happens when you leave separately, including tracking-domain control, export conditions and notice terms; completing setup does not settle any of those points or guarantee that the program can move.
For an inherited program, identify the tracking domain and its registrant first, then list the leading partners by revenue and what each actually does. Those checks explain the inherited program more clearly than relying on the outgoing owner's summary alone.
Keep evaluation open long enough to place real orders on every route, and add a validation cycle if one is available. If an export test is refused, treat the refusal as the answer, not a reason to postpone the choice until after signature.
