A partner who has not sent a referral in 60 days has not necessarily left your program. They may be testing a new channel, waiting for product updates, or sitting on a long B2B sales cycle.
Accurate partner churn reporting separates those cases before someone removes an affiliate, changes a commission, or sends the wrong email. Rewardful can supply core referral and commission records, but your team still needs clear rules around lifecycle status, billing events, and attribution.
Start by defining what each status means in your program.
Define partner churn before you measure it
Partner churn is a partner leaving an active commercial relationship with your program. It is not a slow month. It is not a customer refund. It is not a commission that remains pending.
Set four separate classifications in your reporting model.
| Status | What it means | What it should affect |
|---|---|---|
| Partner inactivity | The partner has not generated a defined activity event within your review window | Re-engagement and account review |
| Partner churn | The partner ends participation or meets your documented churn rule | Partner retention rate |
| Customer churn | A referred customer cancels, fails to renew, or becomes inactive | Referred revenue retention |
| Program cancellation | Your company ends the program or removes a partner | Program operations and audit logs |
Keep these records separate. Mixing them turns a useful dashboard into a list of false alarms.
Inactivity needs a review window
An inactive partner is still a partner. Define inactivity using a rule that fits your buying cycle.
For a self-serve SaaS product, 60 or 90 days without a new referral may be enough to trigger a review. For enterprise software, that window may need to be 180 days or longer. A consultant may send one high-value customer each quarter. Calling that churn would be wrong.
Track the last qualifying activity date. Use an event you can prove, such as a tracked click, referred signup, paid referral, or approved commission. Do not use login activity alone. A partner can log in without promoting you.
Customer churn is a quality signal, not partner loss
A referred customer who cancels tells you something about acquisition quality, onboarding, pricing, or product fit. It does not prove the partner churned.
Measure customer churn by the affiliate who originally referred the account. This lets you compare customer retention across partner cohorts. A partner with fewer signups may create stronger retained revenue than a high-volume partner with fast cancellations.
Stripe subscription events can support this view. Review Stripe’s subscription webhook guidance before you decide which status changes count as churn in your own billing model.
A commission status is an accounting status. It is not proof that a customer stayed, left, or that an affiliate stopped promoting you.
Set the rules before you export data
A churn rate only works when every person uses the same inclusion rules. Write the rules in a short operating document. Store the version date beside every monthly report.
Your team needs answers to four questions:
- What makes a partner eligible for the starting population?
- Which event officially marks a partner as churned?
- Which partners are excluded from the calculation?
- How long must a partner remain inactive before a human reviews the account?
Do not change these rules after a weak month. That makes trend reporting useless.
Use a fixed denominator
The basic partner churn formula is:
Partner churn rate = churned eligible partners during the period / eligible active partners at the start of the period x 100
Say you began April with 80 eligible active partners. Four partners formally opted out, and one account was removed after a verified terms violation. If your policy treats both outcomes as churn, the April rate is:
5 / 80 x 100 = 6.25%
Do not add partners who joined during April to the denominator. They had no chance to churn at the beginning of the period.
Exclude test accounts, duplicate accounts, unapproved applicants, and partners placed on a documented temporary pause. Keep fraud removals in a separate field if you want to report voluntary and involuntary churn independently.
Define the event that closes the relationship
Use a clear churn event. Examples include a written opt-out, an account closure request, a signed termination notice, or a manager decision after a documented partner review.
Do not automatically classify someone as churned because commissions fell to zero. Revenue can decline because of seasonality, attribution windows, plan changes, product stock, or a partner’s campaign calendar.
Program cancellation is different. If you shut down the affiliate program, record the end date and impacted partner count. Do not report that event as partner churn. Your team made the commercial decision.
Build a trusted Rewardful source record
Rewardful tracks affiliate program objects such as affiliates, referrals, commissions, payouts, campaigns, and affiliate links. Its REST API documentation states that merchants can create affiliate accounts and fetch reporting data.
That does not mean every churn metric exists as a native dashboard field. Before you build an automated report, verify your current Rewardful plan, API access, available exports, webhook events, and dashboard filters.
Store the records that explain a result
Create one monthly row per partner in your spreadsheet, warehouse, or BI tool. Include both Rewardful data and internal lifecycle fields.
Capture:
- Rewardful affiliate ID, partner name, email, campaign, and join date.
- The partner’s last tracked referral, sale, and approved commission date.
- Referred customer ID or billing customer ID where your privacy policy permits it.
- Active referred subscriptions at the period start and end.
- Commission state, payout status, refund or reversal status, and payout date.
- Partner lifecycle status, churn reason, reviewer, and decision date.
- Source system, report date range, export date, and record version.
The source fields matter when a partner disputes a classification. “No activity” is not enough. You need to show the report range, the activity definition, and the records used.
Preserve attribution when records change
Attribution can change after the initial signup. A customer may need manual correction after a sales-assisted deal, a migration, or a checkout issue.
Rewardful documents how to manually attribute an existing Stripe customer. That can correct reporting, but it also means historical numbers may change.
Do not overwrite the original export. Add an adjustment record with the customer ID, partner ID, adjustment date, reason, reviewer, and impact on commissions or retention. Your finance team needs the same history your partner manager needs.
Connect billing events to referral data
Rewardful is strongest when it is connected to the billing records that prove revenue movement. Referral creation and commission creation are useful events. They are not a full customer-retention system.
Your churn workflow should connect the original affiliate attribution to the subscription lifecycle in Stripe or your billing platform.
Track the subscription events that matter
Set your customer churn definition before you map events. You might count a cancellation when a subscription ends. You might wait until the paid period expires. You might classify payment failure as at-risk instead of churned.
For recurring SaaS, maintain separate fields for:
- Subscription created and first invoice paid.
- Trial ended without conversion.
- Payment failed and recovery status.
- Cancellation scheduled for period end.
- Subscription canceled or expired.
- Refund, chargeback, and commission reversal.
- Reactivation after a prior cancellation.
Stripe treats cancellation, failed payments, updates, and trial transitions as separate parts of the subscription lifecycle. Read the subscription cancellation documentation before mapping a cancellation to your internal churn date.
Use webhooks for updates, not blind trust
Rewardful webhook payloads can include the object that caused the event, such as an affiliate, campaign, conversion, or commission. Review the Rewardful webhook request format before you build an integration.
Store the event ID, timestamp, object ID, source system, and processing result. Reject duplicates. Route failed events to an exception queue. Reconcile the queue every week.
A webhook delivery confirms that an event was sent. It does not confirm that your database applied the correct status. Compare a sample of webhook records against Rewardful and Stripe each month.
Calculate partner churn and customer retention separately
Once your rules and records are stable, calculate two reports. The first measures the health of your partner base. The second measures customer value by partner cohort.
Keep the labels plain. Leaders should not need to guess what a percentage includes.
Report partner churn by cohort
Group partners by the month they joined or became eligible. Then compare each cohort against the same lifecycle rule.
For example, the January cohort may include 20 approved partners. By the end of June, three formally exited and four remain inactive but unconfirmed. Report:
- Formal partner churn: 15%.
- Inactive partners requiring review: 20%.
- Still active or retained partners: 65%.
This gives the team a useful distinction. Re-engagement work belongs with the four inactive partners. Offboarding analysis belongs with the three who left.
Cohort analysis also stops a growing program from hiding losses behind new signups. A SaaS cohort analysis framework can help you structure retention views by starting group and time period.
Measure referred customer churn as a second report
Use a separate formula for customers:
Referred customer churn rate = referred customers who churned during the period / active referred customers at the start of the period x 100
Group this by originating affiliate, campaign, plan, and signup month. Do not credit or blame a partner for customer churn until you check the sample size.
One cancellation from two referrals is not a reliable trend. Ten cancellations from 200 active referred customers deserves attention. Review onboarding completion, first-value actions, plan fit, refund reasons, and sales handoff quality before changing partner terms.
Run an ethical partner retention workflow
Retention work should start with evidence. Do not send a generic “we miss you” campaign to everyone who has a quiet month.
Create a review queue for partners who cross your inactivity threshold. Assign one owner. Give the owner access to the relevant activity history, campaign terms, support notes, and prior outreach.
Diagnose the actual problem
Check the basics before you contact the partner. Confirm that their link works, the campaign is active, the landing page matches their audience, and referral attribution is present.
Then review the funnel. A partner may have clicks but no paid referrals. That usually points to the offer, page, checkout, or audience match. A partner may have referred customers who cancel quickly. That points to customer quality or product experience.
Change one variable at a time. If you replace the offer, commission rate, landing page, and email sequence together, you will not know what improved retention.
Communicate without pressure or false claims
Tell partners what you can prove. Use their last confirmed activity date and the current program terms. Do not say they “lost” commissions unless the commission record shows a reversal and you can explain why.
Ask whether they want updated assets, a deep link, product training, or a pause. Give them a clear opt-out path. Do not use customer-level data in outreach unless your agreement and privacy rules allow it.
If your team needs help defining the data model, payout controls, and partner review process, Book A Call before you scale the program.
Keep an audit trail when reports disagree
A report dispute is easier to resolve when the source record is complete. Keep the partner ID, campaign, referral or customer ID, report range, event timestamps, commission state, payout status, and screenshots of the relevant records.
State the expected result and why. For example, a referred subscription renewed on a known date, but no recurring commission appeared after the normal processing window. That gives your team a case they can reproduce.
Do not assume every missing commission is a Rewardful error. The customer may have canceled, received a refund, changed plans outside the reward rule, failed payment, or been attributed under another allowed process.
Review the current configuration before each major reporting change. Rewardful settings, plan access, campaign rules, and billing integrations can change. Your published operating rules should match the system your team uses today.
Final Thoughts
Accurate partner churn reporting starts with definitions, not a dashboard export. Separate inactive partners, confirmed exits, customer cancellations, and program closures before you calculate a rate.
Rewardful provides the affiliate and commission records. Stripe or your billing system provides the subscription evidence. Your operating process connects both records, preserves corrections, and gives partners a fair explanation when something changes.
