Academy · Tracking plan · Guide
A tracking plan decides what gets measured
before anyone writes a line of code.
A tracking plan is a table: which event, when it fires, which properties it carries and who owns it. Without one, every team measures something different under the same name. This guide builds one for a fictional software product, an agency website and a shop.
Where do you want to make progress?
Events trial_started and project_created
A tracking plan decides what gets measured
before anyone writes a line of code.
Event, trigger, properties, owner.
A tracking plan is a table: which event, when it fires, which properties it carries and who owns it. Without one, every team measures something different under the same name. This guide builds one for a fictional software product, an agency website and a shop. Four columns are enough to start. One naming scheme, such as object_action in the past tense, stops "signup", "Sign Up" and "registered" from becoming three different numbers.
What you need.
- A list of the five most important questions the team wants to answer with numbers.
- An agreed naming scheme everyone involved knows.
- A test environment where you can check events before they go live.
- Event: object_action (example trial_started)
- Trigger: exactly when it fires (example Trial account confirmed by email)
- Properties: only what questions need (example plan, source)
- Owner · status: person · planned, implemented, verified (example Product team · verified)
The learning path
Questions, events, verification.
From questions to events
Write down your five most important questions, such as "How many trial accounts create a first project?". Derive the events they need: trial started, project created. Everything else waits.
- Events trial_started and project_created
- Property plan on both
- Two rows in the plan, each with an owner
Two rows in the plan, each with an owner
If you get stuck
When the number doesn't fit.
How many events does a plan need?
As few as possible. A plan with twenty well-kept events is more useful than one with two hundred that nobody checks.
An event counts twice. What now?
It usually fires in two places, such as the browser and the server. Decide in the plan where it fires, and check the number against a second source like your list of accounts.
Can Peak Analytics evaluate events?
Not yet. Event, website and product analytics are planned. Today the preview evaluates business records in Peak: orders, receipts, tasks, goals and files. A tracking plan still helps, because it fixes the vocabulary for every tool.
Your quality check
Before you apply it to your numbers.
Tick what you have checked. Your selection stays in this view only.
0 of 3 points checked
What this article is based on.
Editorial page with fictional examples (Taktwerk Software (fictional), Harbourview Agency (fictional), Nordwind Travel Goods (fictional)). The guide describes an approach; where Peak Analytics covers a step today, the page says so explicitly. No measurements, no customers, nothing is sent or saved.
- Editorial demo
Synthetic numbers in the browser. No real data is read, computed or saved.
- Checked evidence
Peak Analytics is a preview: pivot over orders, receipts, tasks, goals and files; count, sum, average, minimum, maximum; day to year; CSV export; sharing a released snapshot; largest value as a task.
peak-one app/w/[scope]/apps/analytics, lib/bi/model.ts, lib/views/pivot.ts, lib/bi/share.ts · checked 2026-10-29
The question first, then the event.
A plan that is maintained is worth more than piles of raw data nobody can explain.
Frequently asked questions
Do I need Peak Analytics for this guide?
No. The guide works with any spreadsheet. Peak Analytics is a preview; where it covers a step today, the page says so.
What goes into a tracking plan?
For each event: name, trigger, properties, owner and status. Four or five columns are enough to start.
Which naming scheme makes sense?
A single one for everyone, such as object_action in lower case and past tense, like trial_started. Which one matters less than everyone using it.
Does Peak Analytics evaluate events?
Not yet. Event, website and product analytics are planned. The preview evaluates orders, receipts, tasks, goals and files in Peak.