Your SaaS is launching an affiliate program. Partners refer people to the app and earn commissions—but the rules go well beyond a percentage of the first subscription payment.
Perhaps a referral earns an initial reward after completing onboarding, another after reaching a product milestone, and recurring commission only while certain conditions remain true. Enterprise referrals might follow a separate schedule. Refunds, account changes, and partner tiers could all affect the final amount.
Your team decides to build the program itself. You already own the product events, understand the business rules, and want control over how commissions are calculated.
CustomerDashboard.io can provide the affiliate reporting portal once your system has calculated the results. Keep referral tracking, commission rules, and payment operations in your SaaS. Connect the reporting data and give affiliates a branded place to follow their earnings, payments, and performance.
Your program follows your product's business rules
Consider a fictional SaaS application with a collaboration-based pricing model. Its affiliate program rewards partners for bringing in customers who become active, successful users.
The program could have rules like these:
| Event or condition | Example commission rule |
|---|---|
| Referred workspace completes onboarding | A fixed activation reward |
| Workspace adds five active teammates | A second milestone bonus |
| Customer pays an eligible subscription invoice | A percentage of eligible net revenue |
| Customer remains active for three months | A retention bonus |
| Affiliate reaches a performance tier | A different rate for future eligible events |
| Invoice is refunded | A corresponding commission adjustment |
| Referral qualifies as an enterprise account | A separately agreed commission schedule |
These are illustrative rules, not built-in CustomerDashboard features. Your application decides which events qualify, which rules can combine, and when earnings become payable.
Standard affiliate platforms may support some of these arrangements. But if your team has decided that its program needs a custom implementation, the next question is how much surrounding software it also needs to build.
Build the commission engine. Connect the reporting portal.
A custom affiliate program has two distinct jobs.
The first is operational: identify referrals, evaluate events, calculate commissions, approve earnings, and arrange payments. This is where your special logic belongs.
The second is informational: let each affiliate see what happened, what they earned, and what has been paid.
CustomerDashboard fits the second job. Its published use cases include affiliate and reseller reporting, with individual logins and customer-specific data. CustomerDashboard product overview
Referral tracking + SaaS events + subscription and payment records
|
v
Your commission engine
Applies your program rules
|
v
Affiliate reporting data
Earnings, adjustments, payments
|
v
CustomerDashboard.io
Branded affiliate dashboards
|
v
Each affiliate logs in
and sees their own figuresYour application remains the source of truth. The portal displays the results your application has produced.
Prepare reporting data with a stable affiliate identifier
You do not need to expose every internal product event to affiliates. Prepare a reporting dataset containing the information they need to understand their performance and earnings.
Use a stable affiliate_id to associate each record with the correct partner. A possible structure is:
| Dataset | Suggested contents |
|---|---|
| Referrals | Affiliate ID, referral reference, referral date, current qualification stage |
| Commission entries | Affiliate ID, event reference, commission type, amount, currency, status, earned date |
| Adjustments | Affiliate ID, original commission reference, adjustment amount, explanation |
| Payments | Affiliate ID, payment reference, amount, currency, status, confirmation date |
| Performance summaries | Affiliate ID, reporting period, referred signups, qualified referrals, eligible revenue |
This is a suggested architecture, not a required CustomerDashboard schema. Your existing tables may already contain most of this information.
Keep customer details limited to what partners need and are entitled to see. An affiliate-friendly referral reference can provide traceability without displaying internal account information.
Calculate complex rules once, in your own system
Suppose an affiliate refers a company that completes onboarding, reaches an activation milestone, and later upgrades its subscription.
Your commission engine evaluates those events and creates the appropriate earnings records. Each entry should explain the amount through a commission type, a relevant date, and a reference to the qualifying event or rule.
The dashboard then presents those records. It should not need to reconstruct your eligibility logic independently.
That keeps the portal consistent with your finance and operations processes. If the program changes, your application applies the correct rule version and publishes the resulting reporting data.
For a reliable implementation, make repeated event processing safe, preserve the rule used for each commission, and record reversals as traceable adjustments. Those responsibilities stay with your custom program.
Give affiliates clear answers about their money
An affiliate opening the portal usually wants answers to a few straightforward questions:
- How much have I earned?
- How much is still pending approval?
- What is available for payment?
- What has already been paid?
- Which referrals and events generated those amounts?
A useful dashboard might start with pending earnings, approved unpaid earnings, and paid-to-date totals. A commission table can explain individual entries, while a payment-history table provides the recorded payment status and date.
Define these states in your own system. For example, a pending commission might still be subject to a qualification window. An approved commission may be eligible for payment but remain unpaid. A paid amount should reflect confirmation from your payment process, rather than merely a scheduled payment instruction.
If you track several currencies, display separate balances or a clearly defined conversion basis. Adding unrelated currencies into a single earnings total would give affiliates a misleading figure.
Add performance analytics alongside commission reporting
The portal can also help affiliates understand which activity produces results. Suggested reporting views include:
| Report | Question it answers |
|---|---|
| Referrals over time | How many referred signups were recorded this month? |
| Qualification progress | How many referrals reached the milestones that earn commission? |
| Earnings by event type | Which rewards contribute most to my earnings? |
| Earnings trend | How are my commissions changing over time? |
| Campaign breakdown | Which tracked referral campaigns produced eligible outcomes? |
| Payment history | Which payments were completed, and when? |
These reports depend on the data your SaaS collects and exposes. For example, campaign reporting needs campaign identifiers, and conversion rates need a defined denominator and attribution window.
Start with a few accurate, understandable charts and tables. Affiliates should be able to reconcile their earnings before you add more elaborate analytics.
Connect CustomerDashboard and set up affiliate access
Once the reporting data is ready, the remaining setup follows a straightforward sequence:
- Connect a supported data source. Make the reporting dataset available through a connection supported by CustomerDashboard. Confirm compatibility with your database and network setup.
- Build the affiliate dashboard. Present earnings, payment records, and the performance metrics relevant to your program.
- Apply your branding. Give partners a reporting destination associated with your SaaS.
- Set up affiliate accounts and data mapping. Use each partner's affiliate identifier to scope the records they should see.
- Verify two different affiliate views. Confirm that each partner receives the right commission, payment, and referral information.
CustomerDashboard's core workflow is to build a shared dashboard and manage accounts while each customer sees their own data. In this scenario, each affiliate organization occupies that customer role. Custom logos and unlimited users per customer are included from the Production plan upward. CustomerDashboard workflow and plans
The integration still requires a compatible source, correct mapping, and a dashboard configuration. The saving is that your team can use an existing reporting portal instead of developing its own reporting pages and account-management interface.
Reporting stays separate from payout execution
Your SaaS or payment workflow remains responsible for moving money. CustomerDashboard displays the payment records and statuses you supply; this architecture does not assume that it calculates commissions, approves payouts, or sends funds.
The same applies to affiliate registration, referral-link generation, agreements, and payment-detail collection. Keep those operational workflows in your application or the services you have chosen for them.
This division gives each component a clear role: your custom system runs the program, and the dashboard keeps affiliates informed.
Launch a distinctive program with a familiar reporting experience
Your commission model may be unusual. The affiliate experience can still be straightforward: log in, see earnings, understand the qualifying events, and follow payment progress.
For a SaaS team building its own event-based affiliate program, CustomerDashboard.io is a practical choice for the reporting layer. You retain control over the rules that make the program special while giving affiliates a branded place to understand their results.
Build your program around your product's economics. Then connect the reporting data and give your partners a clear view of the value they are creating.
Explore CustomerDashboard.io for affiliate reporting.
This article describes a proposed integration architecture. Referral attribution, commission calculation, approvals, and payment execution belong to the SaaS application's own systems. Confirm data-source compatibility and required reporting features during setup.
