Course lesson · Senior-Leader
KPIs and the KPI Tree
A GEO KPI tree connects the outcome leadership cares about, usually pipeline or revenue, to the metrics that drive it, from AI referral conversions down to mention, citation and recommendation rates. It turns visibility data into a business story, shows which metrics the team can influence directly, and makes clear where attribution relies on assumptions rather than measurement.
In this lesson
- What a KPI tree is and why leaders need one
- Leading and lagging metrics
- A GEO KPI tree, level by level
- Being honest about attribution
- Exercise and quiz
Why do leaders need a KPI tree?
Executives don't fund "visibility"; they fund growth. Without a clear chain from activity to outcome, GEO reports become lists of metrics that went up or down. A KPI tree answers the question every leader asks: if this number improves, what happens to the business?
What are leading and lagging metrics?
| Type | Definition | GEO examples |
|---|---|---|
| Lagging | Outcomes that show results after the fact | Revenue, pipeline, customers |
| Intermediate | Behaviour that links visibility to outcomes | AI referral sessions, key events |
| Leading | Early signals the team can influence | Mention, citation and recommendation rates |
| Inputs | Work the team does | Pages refreshed, citations earned |
Leading metrics move first. Lagging metrics prove value. You need both.
What does a GEO KPI tree look like?
Revenue influenced by AI search
- Pipeline from AI-influenced leads
- AI referral key events (GA4, custom channel group (Google)) - Self-reported "AI assistant" leads (forms, sales notes)
- AI referral sessions
- Citation rate for priority prompts - Pages cited per engine
- AI visibility
- Mention rate - Recommendation rate - Share of voice vs competitors
- Inputs
- Priority pages refreshed - Third-party sources corrected or earned
Each level should have a named owner and a data source.
How do you define each KPI?
Write a formula, a source and a cadence for every metric:
| KPI | Formula (example) | Source | Cadence |
|---|---|---|---|
| Recommendation rate | Answers recommending you ÷ answers for priority prompts | Visibility scans | Monthly |
| Share of voice | Your mentions ÷ mentions of tracked brands | Visibility scans | Monthly |
| AI referral key events | Key events from the AI assistants channel | GA4 (Google) | Monthly |
| Self-reported AI leads | Leads choosing "AI assistant" ÷ all leads | CRM / forms | Monthly |
| AI-influenced pipeline | Pipeline value from the two lead sources above | CRM | Quarterly |
How honest should attribution be?
Very. Many people read an AI answer and never click, or come back later by searching your brand. So:
- State what's measured (clicks, self-reported sources) and what's estimated.
- Don't multiply visibility by made-up conversion rates to claim revenue.
- Report ranges for visibility rates, because answers vary (NIST).
- Use trends rather than single months.
Credibility is the most valuable asset a GEO leader has. One inflated claim can undermine every later report.
Which mistakes should you avoid?
- Too many KPIs: keep leadership's view to 3–5
- Vanity metrics: raw mention counts without context
- Metrics with no owner
- Changing definitions mid-year without restating history
- Treating correlation as causation without controls
How do you link the tree to targets?
Set a target only for metrics the team can influence, and express it as a direction plus a range. For example: "Raise recommendation rate on comparison prompts from about 15% to 20–25% by Q4." Leave the lagging metrics, revenue and pipeline, as tracked outcomes rather than hard GEO targets, because many other teams affect them. Review the targets each quarter alongside the roadmap.
A quick example
Illustrative. A B2B software company's tree starts with "AI-influenced pipeline". In Q3, self-reported AI leads are 6% of all leads, AI referral key events are up quarter on quarter, and recommendation rate for priority prompts is 22% (range 17–28%). The CMO sees one slide: the trend, the range and the actions planned to lift recommendation rate on comparison prompts.
KPI tree checklist
- [ ] Top-level outcome agreed with leadership
- [ ] 3–5 headline KPIs
- [ ] Formula, source, owner and cadence for each
- [ ] Leading and lagging metrics both included
- [ ] Attribution assumptions written down
- [ ] Ranges reported for visibility rates
- [ ] Definitions frozen for the year
Exercise
Build a KPI tree from AI visibility to pipeline.
- Write your top-level outcome.
- Add two or three intermediate metrics.
- Add three leading visibility metrics.
- Fill the definition table for each.
- Write two sentences on what you can and can't attribute.
Quiz
- What sits at the top of a GEO KPI tree?
a) Mention count b) A business outcome such as pipeline or revenue c) Pages published Answer: b
- What are leading metrics?
a) Early signals the team can influence b) Final revenue c) Last year's results Answer: a
- How should AI influence without clicks be handled?
a) Invent a conversion rate b) State assumptions and use self-reported data c) Ignore it Answer: b
- How many headline KPIs should leadership see?
a) 3–5 b) 25 c) 1 at most Answer: a
- Why freeze metric definitions?
a) So trends remain comparable b) To hide changes c) It's required by GA4 Answer: a
Next: Lesson 6: Reporting to the board
Sources
- Google, Custom channel groups in GA4
- Google, Key events in GA4
- NIST/SEMATECH, Confidence intervals for proportions
Questions
What is a KPI tree?
A diagram that breaks a business goal into the metrics that drive it, so each team metric connects visibly to an outcome leadership cares about.
Can AI visibility be tied directly to revenue?
Only partly. Clicks and self-reported attribution can be measured; much AI influence happens without a click, so state the assumptions.
How many KPIs should leadership see?
Usually three to five, with the rest available as supporting metrics.