What a KPI tree is
A KPI tree is a hierarchy with one outcome at the top and a chain of metrics beneath it, where every parent is a stated function of its children. The function is usually multiplication (orders equal sessions multiplied by conversion rate), sometimes addition (revenue equals new-customer revenue plus returning revenue), occasionally subtraction (net revenue equals gross revenue minus refunds). The rule that makes it a tree rather than a list is that the children fully explain the parent: if sessions and conversion rate both hold steady, orders cannot have moved.
That property is what distinguishes a tree from a scorecard. A scorecard lists metrics the team cares about; a tree says how they combine. When the outcome moves, the tree says which branch to look in and, by following the arithmetic down, which leaf. When a team proposes an initiative, the tree says which leaf it touches and, by following the arithmetic up, how much the outcome could move if the initiative works. Both directions — diagnosis down, planning up — depend on the arithmetic being explicit.
Choosing which outcome sits at the top is the job of the objectives and KPIs guide; the north-star-and-OKRs framing makes the same choice at organisation level. This page assumes the outcome has been chosen and shows how to decompose it. The KPI framework reference holds the standard metric definitions the leaves should align to.
The arithmetic between levels
Each level of the tree is connected to the next by a formula, and the formula must balance. Write it beside the parent node. The commonest forms in marketing:
| Relationship | Form | Typical use |
|---|---|---|
| Rate decomposition | Count equals a larger count multiplied by a rate | Orders from sessions and conversion rate; leads from form views and completion rate |
| Value decomposition | Value equals a count multiplied by a value per unit | Revenue from orders and average order value; pipeline from leads and average deal size |
| Additive split | Total equals the sum of segments | Revenue by channel, by market, by new versus returning customers |
| Funnel chain | Final count equals the first count multiplied by each stage rate in turn | Visits to product views to add-to-basket to checkout to purchase |
| Cost relationship | Cost per result equals spend divided by results | Cost per lead; acquisition cost (CACCost to acquire one new customer.) from spend and new customers |
| Lifetime relationship | Value per customer equals value per period multiplied by retention periods | Lifetime value (LTVTotal value a customer brings over time.) from average margin and expected tenure |
Two rules keep the arithmetic honest. First, every child of a multiplicative node must be measured on the same population and period as its siblings: a conversion rate computed on all sessions cannot sit beside a session count that excludes bots. Second, an additive split must be exhaustive and non-overlapping, or the parts will not sum to the whole and the tree loses its explanatory power. Where a segment is partially measured — offline orders, say — add an explicit "unattributed" child rather than letting the gap hide in the arithmetic. In a funnel chain, each stage rate, such as add-to-cart rateShare of sessions in which a product was added to the cart., must be computed on the count of the stage before it, or the product of the rates will not reproduce the final count.
An online retailer's revenue tree, with the numbers that balance
Revenue = Orders × Average order value
Orders = Sessions × Conversion rate
In March the retailer records 420,000 sessions, a conversion rate of 2.1% and an average order value of £58, giving 8,820 orders and £511,560 in revenue. In April, revenue falls to £469,800. Sessions are 435,000 (up), average order value is £60 (up), so the orders node must explain the fall: 7,830 orders implies a conversion rate of 1.8%. One level further down, the split by device, which is 40% desktop and 60% mobile in both months, shows desktop conversion rate unchanged at 3.0% and mobile down from 1.5% to 1.0%. The blended rate follows from the segments and their shares: 0.4 × 3.0% + 0.6 × 1.5% gives March's 2.1%, and 0.4 × 3.0% + 0.6 × 1.0% gives April's 1.8%. A funnel chain beneath mobile shows the add-to-basket rate flat and the checkout completion rate down from 48% to 32%. Because the device mix did not move, there is no second leaf to explain, and the tree has taken a £41,760 revenue shortfall to a single leaf — mobile checkout completion — in four steps, each a formula that balances. Had the mix shifted towards mobile, that shift would be a second leaf to report beside the mobile rate. Running the mobile checkout numbers through the conversion rate calculator confirms the arithmetic before anyone opens a ticket.
Inputs, outputs and guardrails
Not every node in a tree is the same kind of thing, and labelling the kinds prevents the most common misuse.
Outputs are the metrics that compose the outcome: orders, average order value, leads, pipeline. They are what the business wants to move, and nobody can move them directly — they are the result of the drivers beneath them. Reporting an output without its drivers tells the team what happened and nothing about why.
Inputs, or drivers, are the leaves: the metrics a named team can change through its own work. Paid media can change clicks and the cost per click; the content team can change organic sessions to a set of pages; the product team can change checkout completion. A leaf that no team owns is not a driver; it is an output that needs decomposing further, or an external factor to note and leave alone.
Guardrails are metrics that are not in the arithmetic but constrain it. Refund rate, unsubscribe rate, lead quality as judged by sales, customer acquisition cost against lifetime value, page speed. A tree that optimises orders without a refund guardrail will happily report growth that the finance team later reverses. Guardrails sit beside the tree with a threshold and an owner, and a driver initiative that breaches one is not a success however far it moved the outcome. The same discipline applies when a team adopts AI tools: the guide to measuring AI's impact on team output connects tasks such as product description drafts to the outcome drivers they feed, with defect and rework ratesThe share of items sent back from a review or launch gate to an earlier stage; each return carries a reason, so the pattern points to the step that failed. as guardrails.
Diagnostics are the measurements beneath a driver that explain its movement without being levers in themselves: the share of sessions on each device, the error rate on a form, the position of a keyword. They are read when a driver moves, and the interactive builder further down this page shows them as the fourth level.
A practical check on each leaf: can you name the person who would be asked to move it, and the action they would take? If not, it is not yet an input.
Building a tree for a revenue goal and a lead goal
The two commonest marketing outcomes decompose differently. Both trees below stop at the point where a named team owns the leaf; a diagnostic level beneath each leaf is implied.
A revenue goal for a transactional site:
| Level | Node | Formula or definition | Owner of the leaf |
|---|---|---|---|
| Outcome | Revenue | Orders multiplied by average order value (AOVAverage revenue per order.) | — |
| Output | Orders | Sessions multiplied by conversion rate (CVRShare of visits or clicks that convert.) | — |
| Driver | Sessions by channel | Additive split: paid search, paid social, organic, email, direct, referral | Channel managers |
| Driver | Conversion rate by device and landing page group | Rate per segment; additive weighting gives the blended rate | Conversion and product teams |
| Output | Average order value | Revenue divided by orders | — |
| Driver | Items per order | Basket composition, cross-sell placement | Merchandising |
| Driver | Average item price | Product mix, promotion depth | Merchandising and pricing |
| Guardrail | Refund rate; acquisition cost against lifetime value | Monitored, not decomposed | Finance with marketing |
A lead goal for a service or business-to-business company:
| Level | Node | Formula or definition | Owner of the leaf |
|---|---|---|---|
| Outcome | Sales-qualified leads | Marketing-qualified leads multiplied by qualification rate | — |
| Output | Marketing-qualified leads | Form submissions multiplied by the share that meet the qualification rule | — |
| Driver | Sessions to lead pages by channel | Additive split by channel | Channel managers |
| Driver | Lead page conversion rate | Submissions divided by sessions to lead pages | Conversion and content teams |
| Driver | Qualification rule pass rate | Share of submissions matching firmographic or intent criteria | Marketing operations with sales |
| Output | Qualification rate | Sales-qualified divided by marketing-qualified | — |
| Driver | Speed to first contact; lead routing accuracy | Operational process metrics | Sales operations |
| Guardrail | Cost per sales-qualified lead; sales-reported lead quality | Monitored, not decomposed | Marketing and sales leads |
The lead tree has a feature the revenue tree lacks: its outcome depends on another department's judgement. The qualification rate is owned jointly, and the tree should say so, because a marketing team judged on sales-qualified leadsA lead that sales has reviewed and accepted as a genuine opportunity to pursue. without influence over qualification will optimise the wrong leaf. The SEO KPIs and reporting guide shows the same decomposition applied to one channel, where the leaves become impressions, click-through and indexed pages. A business with recurring revenue needs a third shape, with first payments and churn beneath the revenue a cohort retains, which the guide to measurement for subscription businesses lays out with the systems that feed each level.
A lead goal raises its own questions about ownership and timing, which the KPI tree for lead generation answers with a pipeline root, source-split stage rates and named sales-side leaves.
The builder below shows a tree of each kind as four levels — objective, outcome, driver and diagnostic — with a note on each node saying how it is measured. Select a node to read its measurement and the drivers beneath it; use it to check that your own tree reaches a leaf a team can act on.
KPI tree builder
Reading a tree: finding the lever
A tree is read in two directions. Downwards, for diagnosis: the outcome moved, so which child moved, and which of its children, until the leaf. Upwards, for planning: a team proposes to move a leaf, so how much does the outcome move if they succeed. Both readings follow the same discipline.
Hold the siblings constant. At each level, ask which child changed and which did not. A multiplicative node with one child moving and the rest flat has one explanation; several children moving at once means the change has several causes, and each is followed separately. Resist the temptation to stop at the first child that moved.
Weigh the branches. Not every leaf has equal pull. In a funnel chain, a stage with a low rate and a large population has more room than a stage already near its ceiling; in an additive split, the largest segment moves the total most for a given rate change. The planning reading of the tree is a comparison of how much the outcome moves per unit of effort on each leaf, and that comparison is what the tree exists to make possible. A tree reads one period at a time; the tutorial on building a growth model in a spreadsheet adds the time dimension, carrying each month's new customers through activation and retention to compare leaves by their effect on the active base a year out.
Check the guardrails before celebrating. A driver that moved the outcome and breached a guardrail — orders up, refunds up faster — has not delivered, and the tree should show both in the same view.
Distinguish a lever from a symptom. Conversion rate fell because the mix of traffic shifted towards a colder channel: the leaf that moved is conversion rate, but the lever is the channel mix one branch over. Trees expose this when the segments are defined consistently across branches, which is the reason the measurement plan tutorial asks for dimensions to be defined before metrics are mapped to platforms. The guide to explaining a change in a marketing metric works through that mix and rate split step by step, then follows the change into segments and events and tests the explanation.
The reading improves with practice and with a habit: every time the outcome is reported, report the branch that explains it. The measurement planning hub places the tree as the second artefact in the sequence precisely because every later document — events, dimensions, checks — exists to make the tree readable. A written tree that leadership recognises is also one of the two gates in the marketing measurement audit scorecard, which rates whether budget decisions rest on evidence that traces back to it.
Common mistakes
- Leaves nobody owns. A tree whose bottom level is still outputs explains nothing; decompose until a team can act.
- Arithmetic that does not balance. Children measured on different populations or periods; additive splits that overlap or leave gaps. Check the formulas with real numbers before publishing the tree.
- Mixing rates and counts in an additive split. Segments of a count add; segments of a rate must be weighted by population.
- No guardrails. Optimising a single outcome without constraints produces growth the business later reverses.
- Too many levels. Decomposing past the point of action turns the tree into a glossary.
- One tree for several outcomes. Each outcome gets its own tree; shared drivers are noted, not merged.
- Confusing the leaf that moved with the lever. A rate can fall because of a mix change in a neighbouring branch; read sideways as well as down.
