
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 articleTrials, upgrades, churn — track events, not vibes
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.
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.
For subscriptions, your affiliate program should explicitly pick ONE conversion event that earns commission. Common options:
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 create a time gap between click → account creation → first payment. You need two rules:
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.
Decide whether affiliates earn on plan changes. Three sane defaults:
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.
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 are powerful — and expensive if you don’t put a ceiling on them. You need to define at least one of these limits:
If you’re early: time-based (e.g., 12 months) is the simplest and easiest to explain.
Before you invite affiliates, run these tests end-to-end. Most ‘tracking bugs’ are really mismatched events or missing identifiers.
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.
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.
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.
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.

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
A founder-friendly set of affiliate terms clauses for SaaS subscriptions: last-click rules, coupon conflicts, refunds/chargebacks, recurring commission limits, payout schedule, and enforcement.
Read article