SaaS Affiliate KPI Dictionary Template: 9 Fields to Define
Use this SaaS affiliate KPI dictionary template to define nine fields and align affiliate metric definitions, source events, and reporting limits.
On this page (13)
What Should You Compare Before Choosing?
A SaaS affiliate KPI dictionary template gives every metric one shared definition before teams compare dashboard totals. It records the business question, source events, numerator, denominator, status rules, time basis, exclusions, owner, and known limits. That definition matters because partner platforms can use familiar labels for different events.
Quick answer: Create one dictionary row per metric. Define what is counted, which event proves it, when it belongs in a period, how refunds or reversals affect it, and who maintains the rule. Keep a version history and label fields that are unavailable or provisional. This template is a governance tool, not a new list of affiliate KPIs or a benchmark set.
A SaaS affiliate KPI dictionary template should live beside the report it explains, where analysts and decision-makers can find the same version.
| Field | What the team records |
|---|---|
| 1. Metric name and decision | The shared label and the decision it supports |
| 2. Unit of analysis | Partner, click, referral, customer, transaction, commission, or payout |
| 3. Source and event map | System of record, event names, identifiers, and joins |
| 4. Numerator rule | Events or records counted in the top of a ratio |
| 5. Denominator rule | Eligible records, exclusions, and matching cohort |
| 6. Status and reversal rules | Pending, approved, declined, refunded, modified, or reopened behavior |
| 7. Date basis and maturity | Event, action, lock, or reporting date and observation window |
| 8. Scope and segments | Currency, partner type, campaign, market, and exclusions |
| 9. Owner, refresh, and limits | Responsible owner, update cadence, version, and caveats |
How to use a SaaS affiliate KPI dictionary template
Affiliate platforms provide useful dashboards, but their labels are not automatically interchangeable. FirstPromoter's report fields guide distinguishes new referrals from new customers and says its revenue field includes new charges and renewals while taking refunds into account. It also documents limits for churn and active-customer reporting when customers reactivate or hold multiple subscriptions. Those details can change how a team interprets a report with the same everyday label.
Build the dictionary around the source event and business decision. A figure called "new referrals" should say whether it includes free users, trials, coupon-based referrals, or only paying customers. A figure called "revenue" should say whether renewals, refunds, credits, currency conversion, or taxes are included. The name alone does not answer those questions.
This template complements the affiliate program KPI guide for SaaS, which explains example measures. Here the focus is the reusable definition and change process behind any measure.
1. Metric name and decision
Choose a short name that distinguishes the measure from nearby metrics. Add one sentence explaining what decision it supports. For example, "paid customer count" might support an onboarding review, while "approved commission" may support payout reconciliation. Names such as "conversion" or "revenue" are too broad unless the definition immediately narrows them.
Keep the business question close to the metric. If no one can name a decision that changes when the value moves, the metric may be a diagnostic rather than a KPI. That is fine, but label it honestly so a dashboard does not imply strategic importance by default.
2. Unit of analysis
State the entity represented by one observation. Common units include partner, click, referral, customer, order, subscription, action, commission line, and payout. A row can count one customer or several transactions from that customer, so the unit changes the meaning of a total and any ratio built from it.
Also record the identifier used to de-duplicate records. Note whether a customer can appear under multiple partner IDs, whether one subscription can emit several billing events, and whether a partner can belong to more than one group. These rules prevent joins from silently multiplying counts.
3. Source system and event map
Name the system of record and the exact events or fields used. Record the event timestamp, external identifier, partner or campaign key, currency, and any bridge table required to join affiliate tracking to billing. If the source is a manual export, include the report name and export date.
Confirm the tracking mode, event names, and identifiers that are actually available in your account. If a required event or identifier is missing, mark the metric unavailable or build it from verified source records rather than assuming every report exposes the same inputs.
4. Numerator rule
Write the numerator as an inclusion rule that another analyst can apply. Define the qualifying event, the status required, and any deduplication logic. For a new-customer measure, specify whether a free signup, trial, first payment, or first approved transaction qualifies.
If a source platform has a built-in field, document its meaning before reusing the field name. FirstPromoter's report guide says a new referral can include a tracked person who is not yet a customer, while new customers have at least one sale. A team that calls both values "signups" could end up presenting two different numerators in one dashboard.
5. Denominator rule
Define the eligible population and the time window. For a rate, the denominator should belong to the same cohort and scope as the numerator. State whether the population is clicks, referred people, submitted transactions, approved partners, or another group. Also list which records are excluded and why.
Name the eligibility rule for immature cohorts. If a referral can take 30 days or more to become a customer, a recent cohort may not be comparable with one that has had months to convert. Mark the recent result as provisional or wait for a defined maturity window.
6. Status, refunds, and reversals
List the states that can appear and explain how a record moves between them. Typical states include pending, approved, declined, paid, refunded, modified, and reopened. Say whether the metric uses current status or status as of a past reporting date, and how a refund or reversal changes earlier values.
An affiliate action may be tracked on one date and locked for payment later. The Impact partner reporting guide describes fields including action date, lock date, status detail, sale amount, and changes or reversals. Record the event and status used so a reported total can be reproduced.
7. Date basis and cohort maturity
Choose one date rule for the metric: click date, referral date, billing event date, action date, approval date, lock date, or payment date. Store the timezone and calendar convention. State whether a dashboard shows activity that happened during the period or later outcomes attributed back to an earlier cohort.
Then write the observation window. For example, a click-to-customer measure could use the click's cohort and observe purchases for a defined number of days. Label a window as provisional when later events may still arrive. Do not compare a mature cohort with one that is still collecting referrals or commission adjustments.
8. Scope, segments, and exclusions
Record the scope needed to interpret the figure: program, campaign, partner type, geography, currency, product plan, customer type, and channel. Define treatment for internal tests, duplicate records, self-referrals, fraud holds, voided transactions, and missing identifiers. If a segment is unknown, keep an explicit unknown bucket rather than silently dropping those records.
Make exclusions visible in the dashboard or its documentation. A rate calculated only for paid subscriptions should not be labeled as all-customer conversion. A revenue figure excluding refunds should not be presented as net revenue. Clear labels let finance, marketing, and partner teams compare the same population.
9. Owner, refresh, and limits
Assign a business owner and a technical source owner. State how often the data refreshes, who reviews mapping changes, and when the definition was last approved. Keep a version number or change log with the date and reason for each update.
Add known limits in plain language. Examples include incomplete cross-device tracking, a platform field available only in one tracking version, late billing events, or a source that does not separate multiple subscriptions. If the definition changes, preserve the old version for historical reporting or recalculate old periods consistently. Never change the label alone and leave consumers to infer what moved.
Put the dictionary into the reporting workflow
Start with the metrics already used in finance and partner reviews. Copy each label into a shared sheet or documentation table, then ask marketing, finance, data, and partner operations to agree on the event and status rules. Resolve the source mapping before deciding whether a different dashboard is needed.
For software selection, compare the FirstPromoter, Rewardful, Tapfiliate, and PartnerStack program pages, then verify current platform capabilities in vendor documentation. Use the affiliate attribution QA checklist to test whether events and identifiers survive the referral-to-payment path.
Keep return-on-investment and payback definitions in their own rows. The SaaS affiliate program ROI calculation guide and affiliate program payback versus ROI comparison cover related decisions. Reuse their concepts only after your dictionary defines the source events, dates, and cost scope.
Use the SaaS affiliate KPI dictionary template as a shared reference, not proof that every platform measures a metric the same way. Publish the definition beside the report, review it when billing or tracking changes, and use the FindAffiliates directory to research relevant affiliate programs and tooling.
FAQ
What is an affiliate KPI dictionary?
It is a shared record of how each affiliate program metric is named, sourced, calculated, segmented, and maintained. It helps teams reproduce a result and see where different reports use different rules.
How do I create a SaaS affiliate KPI dictionary template?
Include the metric name and decision, unit, source events, numerator, denominator, status and reversal rules, date basis, scope and exclusions, owner, refresh cadence, version, and known limits.
How is a KPI dictionary different from a dashboard?
A dashboard displays results. A dictionary explains the definitions, source events, and caveats behind those results so users can interpret and compare them correctly.
How often should affiliate metric definitions be reviewed?
Review them when tracking, billing, commission policy, or reporting fields change, and on a regular schedule set by the data owner. Keep the prior definition and effective date for historical comparisons.
