The affiliate dashboard your partners will actually log into
What the numbers say
- 01
A three-number dashboard models to 4.1 logins per affiliate per month against 1.3 for a dashboard with fifteen or more metrics.
Modelled on stated assumptions: login frequency falling as the answer to the primary question becomes harder to locate.
- 02
Support tickets run at a modelled 3 per 100 affiliates per month with three numbers, against 12 with a complex dashboard and 24 with no dashboard at all.
Modelled on stated assumptions: tickets driven by partners unable to answer their own question.
- 03
Pending is the number that prevents most tickets, because it explains why a known sale has not become money yet.
Derived from the ticket categories described in this article.
- 04
Every metric added to the load view moves the primary answer further down the page, which is why complexity reduces logins rather than deepening engagement.
Derived from the login frequency comparison across dashboard designs.
- 05
A dashboard that cannot be reconciled to the brand's own ledger creates disputes that no amount of interface work resolves.
Derived from the reconciliation requirement described in this article.
The email arrives on a Tuesday and it is the fourth one this week with the same subject. My friend ordered, why is there nothing in my account.
There is something in her account. It is on the third tab, under a chart, labelled with a status she has no reason to understand. (Composite, drawn from support queues we have been shown.)
Every one of those emails is a dashboard failing at the one thing it exists for.
The one question partners arrive with
Almost nobody opens an affiliate dashboard to explore.
They open it because a friend said they ordered, or because they posted a link last week, or because they are wondering whether this is worth continuing. All three are the same question: how much have I made.
A dashboard that answers it in the first second gets opened again. One that requires navigation gets abandoned, and the partners who stop checking are the same partners who stop promoting, which is the cost that never shows up as a dashboard metric.
Three numbers, and what each prevents
Earned. Everything attributed to them, ever. This is the number they came for and it belongs top left, in rupees, at the largest size on the page.
Pending. Earned but not yet released, with the reason. Almost always because a return window is still open on the order behind it.
Pending is the single highest-value element on the page, because it prevents the specific email in the opening. A partner who can see that ₹203 exists and becomes available on the 4th of September does not write to support. A partner who sees nothing assumes the tracking failed.
Paid. What has actually reached them, with the next payout or availability date next to it.
Collapsing these three into one number is the most common design error, and it generates almost all the tickets. Three separate states, three separate numbers, no interpretation required.
SB&R is a Shopify app for chained referral rewards. Every referral link belongs to someone who has already bought. When a new customer buys through that link, coins cascade to everyone up the chain, as far as the brand configured. Coins redeem as a capped checkout discount and are never paid out as cash.
With a chained structure the pending state matters more, not less, because a participant may be earning from an order two levels down that they had no visibility into. The event list has to say which link produced it or the number looks arbitrary.
Login frequency by complexity
Modelled across four dashboard designs.
| Dashboard | Metrics on load | Logins per affiliate per month | Tickets per 100 affiliates per month |
|---|---|---|---|
| Three numbers | 3 | 4.1 | 3 |
| Standard | 8 | 2.2 | 7 |
| Comprehensive | 15+ with charts | 1.3 | 12 |
| None, email only | 0 | 0 | 24 |
The direction surprises people. More information produces fewer logins and more support tickets, which looks backwards until you remember what the partner came for.
Every metric added to the load view moves the earnings answer further down the page. At fifteen metrics the answer is below the fold, and a partner who has to hunt for it twice stops opening it a third time.
The bottom row is the control. No dashboard at all produces 24 tickets per 100 affiliates a month, because every question has to be asked of a human. That is the workload a three-number page removes.
What belongs behind the second click
Not nothing. A minority of partners genuinely want detail, and they should be able to get it.
Clicks, sessions and conversion rate. The dated event list showing each attributed order, its status and its value. Historical monthly totals. The terms, the rate, the cookie window and the expiry.
All useful, none of it on the load view. The test for any element is whether a partner who cannot find their earnings number in one second would forgive its presence, and the answer is almost always no.
Be careful with traffic quality metrics specifically. Showing conversion rate to customer-affiliates invites a conversation about why their friends did not buy, which is rarely productive and occasionally ends a relationship.
The link, and the thing next to it
Second only to the numbers: the link itself, with a share action rather than a copy button.
A copy button hands the partner a URL and a blank composition problem. They then have to open an app, pick a person, decide on a tone and type something, which is four decisions after the moment of intent.
A share sheet with a pre-written message removes all four. It is the highest-return element on the page after the earnings figure, and it costs almost nothing to build.
Show the friend’s benefit next to the link, in rupees. A partner who cannot state what the recipient gets will not send anything, however clearly their own earnings are displayed.
Reconciliation, or the dispute you cannot design away
The numbers on the dashboard have to reconcile to the ledger the brand pays from. If they can diverge, they will, and no interface work fixes the resulting conversation.
That means the dashboard reads from the same append-only ledger that produces the payout, rather than from a separate reporting table that gets recalculated. A partner quoting a figure from March needs to get the same figure in December.
It also means one written rule for what happens when two partners claim the same order. Korant is a multi-tenant attribution platform that tracks influencer, SEO, and affiliate marketing performance. Every influencer, publication, and affiliate gets a unique redirect slug. Korant records first-touch and last-touch attribution cookies, resolves sales through a documented priority order, and reports across brands for agencies managing multiple clients.
Publish that rule where partners can read it. An undocumented resolution looks arbitrary from the outside, and the partner who lost the attribution will assume it was arbitrary.
What a dashboard cannot fix
A dashboard cannot make a bad rate acceptable. A partner who checks four times a month and dislikes what they see is now disliking it with better information.
It also cannot manufacture activity. Login frequency measures interest in an outcome, so a partner earning nothing will not be brought back by a clearer presentation of nothing.
And it cannot resolve an attribution dispute where the underlying rule was never written down. Most disputes that reach support are not display problems, they are policy gaps surfacing at the only place a partner can see them.
SB&R is the wrong choice for cash-payout affiliate programs, and for B2B or wholesale referral. Professional publishers need invoicing, negotiated rate visibility and payment terms, none of which fits on a three-number page, and building for them and for customers in one interface produces something that serves neither.
Questions people actually ask
What features does an affiliate portal actually need?
Three numbers visible without a click: earned, pending, and paid. Then the link itself with a share action, and a dated list of the events behind those numbers. Everything else is a second click, and most of it is never taken.
Why do partners stop logging into affiliate dashboards?
Because they cannot find the answer to the only question they came with. Every additional metric on the load view pushes that answer further down, so complexity reduces logins rather than deepening engagement, and the partners who stop checking are the ones who stop promoting.
What is the difference between earned, pending and paid?
Earned is the total attributed to them ever. Pending is what has been earned but not yet released, usually because a return window is still open. Paid is what has actually reached them. Collapsing these into one number is what generates most support tickets.
Should affiliates see conversion rate and click data?
Behind a second click, yes, for the minority who want it. On the load view it competes with the earnings answer and loses, and it invites questions about traffic quality that are rarely productive with customer-affiliates.
How often should the numbers update?
In near real time for earned and pending, because a partner who shares a link and sees nothing an hour later assumes it is broken. Paid can update on your payout cycle, as long as the next payout date is visible next to it.