← Back to blog
OpsMar 14, 2026

Affiliate tracking for SaaS subscriptions: trials, upgrades, refunds, and recurring commissions

How to handle trials, upgrades, churn, and recurring commissions without payout chaos

Affiliate tracking for subscriptions: events and edge cases

If you’ve ever said ‘affiliate tracking is broken’ while selling subscriptions, you were probably right — but not because cookies don’t work. Subscription businesses create edge cases that one-time sales don’t: trials, upgrades, downgrades, proration, churn, refunds after payout, and recurring commissions.

The fix is to decide what *event* earns commission, define how plan changes behave, and make sure your tracking pipeline can reconcile revenue over time. This guide gives you a clean default setup plus a testing checklist.

Quick answer

For most SaaS affiliate programs, the safest default is: attribute the referral at signup, pay commission on the first paid invoice, calculate recurring commissions on net revenue actually collected, and cancel or claw back commission when the customer is refunded.

Decision pointRecommended SaaS defaultWhy it works
Conversion eventFirst paid invoiceAvoids paying for trials that never convert
Attribution captureStore on the account at signupMore reliable than hoping the cookie survives weeks later
Plan changesCommission on net revenue collectedHandles proration and upgrades cleanly
RefundsCancel or claw back commissionKeeps payouts tied to real retained revenue
Recurring ceiling12 monthsSimple to explain and model early on

Table of contents

The 3 things that change with subscriptions

  • Revenue is not a single moment: it accrues over time (and can reverse via refunds/chargebacks).
  • The customer can change the product after the first purchase (upgrade/downgrade/seat changes).
  • You may pay affiliates multiple times (recurring commissions), which means you need policy + accounting discipline.

That’s why ‘track the checkout page visit and call it a day’ breaks down. You need a definition of conversion and a mapping between billing events and commissions.

Pick the conversion event (the non-negotiable step)

For subscriptions, your affiliate program should explicitly pick ONE conversion event that earns commission. Common options:

  • First paid invoice (recommended default for SaaS)
  • Trial start (only if you’re okay paying for low-intent signups)
  • Trial-to-paid conversion (paid event, but attribute off the trial start)

If you’re unsure: use **first paid invoice** as the conversion event and treat trials as ‘pre-conversion.’ You’ll avoid paying commissions on users who never pay.

Related: if you haven’t written terms yet, copy/paste a clear definition of conversion + net revenue in your affiliate terms.

Trials: when does commission start?

Trials create a time gap between click → account creation → first payment. You need two rules:

  • Attribution: how long the referral stays eligible (e.g., 30 days from click).
  • Trial window: how long a trial can run and still be commissionable (e.g., 21–45 days from signup).

Practical implementation: store the affiliate attribution on the user/account at signup (from the link click), then apply it when the first paid invoice happens. Don’t rely on ‘cookie still exists’ weeks later.

Upgrades, downgrades, and proration

Decide whether affiliates earn on plan changes. Three sane defaults:

  • Earn on initial plan only (simplest)
  • Earn on net revenue actually collected each billing period (most accurate, requires good data)
  • Earn on upgrades only (incentivizes expansion, but can be gamed)

If you do anything beyond ‘initial plan only,’ you must define how proration behaves (mid-cycle changes). Most teams choose ‘commission on net revenue collected’ and let proration fall out naturally.

Refunds, cancellations, and chargebacks

In subscriptions, the most common payout dispute is: ‘You paid me, then refunded the customer.’ Your policy should say commissions are calculated on net revenue actually received, and refunds/chargebacks cancel (or claw back) commission.

Recurring commissions: define the ceiling

Recurring commissions are powerful — and expensive if you don’t put a ceiling on them. You need to define at least one of these limits:

  • Time-based: pay for the first 6/12 months
  • Revenue-based: pay until $X of net revenue is reached
  • Plan-based: only on certain tiers

If you’re early: time-based (e.g., 12 months) is the simplest and easiest to explain.

Debugging + test checklist

Before you invite affiliates, run these tests end-to-end. Most ‘tracking bugs’ are really mismatched events or missing identifiers.

  • Test 1: click affiliate link → signup → first paid invoice (commission created).
  • Test 2: click affiliate link → signup → trial cancels (no commission).
  • Test 3: click affiliate link → signup → pay → refund (commission canceled or clawed back).
  • Test 4: upgrade mid-cycle (expected behavior matches your policy).
  • Test 5: two affiliates touch the same customer (your attribution rule is applied consistently).

If any of these fail, don’t patch it with ‘manual adjustments’ as a permanent process. Fix the rules + event pipeline so payouts stay boring.

FAQ

How do you track affiliate commissions on subscriptions?

The cleanest setup is to capture attribution when the user signs up, persist it on the customer or account record, and apply commission when a billing event happens, usually the first paid invoice or recurring paid renewals.

Should we pay on trial start?

Only if your trial-to-paid rate is high and you’re okay paying for leads. Most SaaS programs pay on first paid invoice to avoid incentives for low-quality signups.

Should upgrades earn affiliate commission?

They can, but only if you define the rule in advance. The simplest policy is to pay on the initial subscription only. The most accurate policy is to pay on net revenue collected each billing period, including upgrades and proration.

Do cookies still matter?

Yes — they’re great for the initial attribution capture. But for subscription timelines, the reliable approach is to persist attribution on the account and use it at billing events.

What happens if a customer refunds after the affiliate was paid?

Your policy should say commissions are calculated on net revenue actually received. If the customer is refunded or charged back, the commission should be canceled or deducted from a future payout.

Want this Playbook in your inbox?

I share practical notes on affiliate programs for SaaS.No spam. No hype.

Unsubscribe anytime. No spam.

Ready to launch?

If Rewardful feels like overkill, start simple: signup page + links + Stripe-attributed revenue.

Related posts

Affiliate platform migration checklist and questions

Affiliate platforms: questions to ask before you migrate (SaaS)

A practical checklist for migrating affiliate platforms in SaaS: what to export, how to compare ledgers, how to handle refunds and clawbacks, and the safest cutover plan.

Read article
Affiliate terms clauses checklist for SaaS subscriptions

Affiliate terms for SaaS subscriptions: template clauses for refunds, recurring commissions, and payouts

A founder-friendly affiliate terms template for SaaS subscriptions: last-click rules, coupon conflicts, refunds, recurring commission limits, payout schedule, and enforcement.

Read article