Measurement
Part of How to build affiliate marketing measurement that stands up
Why your affiliate marketing reporting dashboard disagrees with finance
Build an affiliate marketing reporting dashboard that stands up in review: pick the metrics, agree a claim window and keep evidence for every payout.
What to take away
- Online sales made up 27.2% of retail sales in Great Britain in January 2024, the ONS retail sales bulletin reports. An affiliate marketing reporting dashboard has to explain that demand, not just restate it.
- Agree metric definitions, the claim window and returns treatment before anyone builds a chart.
- Keep a dated dispute log, because most payout arguments concern timing rather than arithmetic.
- Store consent and disclosure evidence beside the numbers.
Start from the decisions, not the charts
A dashboard is a queue of decisions. Write the questions down before you choose a tool, because a panel nobody acts on is decoration.
Most English retail programmes ask the same questions. Which publishers bring new customers rather than repeat discount hunters? Where do returns erode commission?
The parent affiliate marketing measurement and reporting guide maps the wider evidence cycle, so read it before you rebuild definitions that already exist elsewhere in your programme.
Agree what one row represents
One row should equal one settled transaction, not one click. State whether the row carries gross order value or net of VAT, and whether it includes delivery.
Write the definition in the dashboard itself, because a tooltip or footnote is enough. If two teams export the same data and get different totals, nobody agreed the definition.
Name the owner and the refresh date
Every panel needs a named owner and a stated refresh time. A weekly report described as live is worse than an honest weekly one.
Show the last refresh date on the page. When a number looks wrong, ask when it was last rebuilt.
Build the path from click to settled commission
Commission is not the same as revenue. Build the path in stages: click, order, validation, settlement, payment. Each stage can lose rows, and each loss needs a reason code.
Reconciliation comes before presentation. If platform totals and your own order data disagree, publish both and explain the gap.
Match platform data to your own orders
Use the network's transaction ID as the join key wherever it is provided. Where it is not, join on order reference and accept a small unmatched pile.
Count unmatched rows monthly and query anything above a threshold you set in advance, for example 2% of transactions.
Handle reversals and late claims
Returns, cancellations and failed payments all reverse commission. Decide how long a transaction can be reversed before it counts as settled, then publish that rule.
Give publishers a way to raise a query with evidence. A short form plus a dated log resolves more disputes than a longer contract.
| Element | Before the review | After the review |
|---|---|---|
| Row definition | One click | One settled transaction |
| Claim window | Unstated | 60 days, published |
| Returns | Excluded from reports | Shown separately |
| Disputes | Email threads | Numbered log with evidence |
| Owner | The agency | Named programme manager |
Report channel by channel and keep the whole picture
Channel totals and publisher totals answer different questions, so keep both and label each one.
Blend them together and you cannot tell whether growth came from a new publisher or one large placement.
Add publisher-level evidence
Publisher rows show concentration. If three publishers generate most of the settled commission, the programme carries risk. Report your top ten publishers by settled commission beside the total.
Read affiliate marketing key metrics in England for the metric set behind these rows, then drop anything the team never acts on.
Keep email and social claims compliant
Promotions sent by email to individuals need consent that meets the ICO's guidance on direct marketing using electronic mail. Record where each consent came from and when.
Social placements carry their own rules. TikTok's advertising policies set out what commercial content may claim and when it must be labelled, so brief publishers before they post.
Common questions
How many metrics should a dashboard show?
Fewer than most teams start with. One headline figure, four or five supporting rows and a dispute count cover a normal retail programme.
How often should affiliate reporting be refreshed?
Weekly suits most programmes because networks settle on a lag. State the cadence on the page so nobody treats a weekly figure as final.
What belongs in a dispute log?
The date raised, the transaction reference, the reason and the outcome. The log turns recurring arguments into fixable causes.
Who signs off a change to a metric definition?
The programme owner, with the finance contact informed. Record the change and its effective date, then rebuild history where you can.
