Metrics & Analytics Dashboard Kit
A complete KPI tracking system for product managers covering engagement, retention, revenue, and growth metrics. Includes metric definition templates, dashboard layouts, reporting cadences, and executive summary formats.
Key Features
- Metric Definition Framework — Standardized definitions for every KPI to prevent misalignment
- Dashboard Layout Templates — Pre-built layouts for daily, weekly, and monthly views
- Funnel Analysis Templates — Acquisition, activation, retention, revenue, referral (AARRR)
- Cohort Analysis Guide — Week-over-week and month-over-month retention tracking
- Executive Metrics Brief — One-page metric summaries for leadership
- Alert Threshold System — Define warning and critical thresholds for every metric
What's Included
| File | Purpose |
|---|---|
dashboards/main.json |
Primary dashboard configuration |
alerts/rules.yml |
Alert threshold definitions |
templates/metric-definitions.md |
KPI definition template with ownership |
templates/dashboard-daily.md |
Daily operational dashboard layout |
templates/dashboard-weekly.md |
Weekly business review dashboard |
templates/dashboard-monthly.md |
Monthly strategic dashboard |
templates/funnel-analysis.md |
AARRR pirate metrics framework |
templates/cohort-analysis.md |
Retention cohort tracking template |
templates/exec-metrics-brief.md |
Executive summary format |
docs/overview.md |
Methodology and metric selection guide |
config.example.yaml |
Alert thresholds and reporting cadence config |
Quick Start
- Start with
templates/metric-definitions.md— define your top 5 North Star metrics - Choose your primary dashboard cadence (daily, weekly, or monthly)
- Map your funnel using
templates/funnel-analysis.md - Set alert thresholds in
alerts/rules.yml - Schedule your first Weekly Business Review using the weekly dashboard template
Template Examples
Metric Definition Card
Metric Name: Daily Active Users (DAU)
Category: Engagement
Definition: Unique users who perform at least 1 core action in a 24-hour period
Data Source: analytics.events WHERE event_type IN ('create', 'edit', 'share')
Owner: Product Manager — Growth
Target: 15,000 DAU by Q3
Alert: Warning < 12,000 | Critical < 10,000
Cadence: Reported daily, reviewed weekly
Segments: By plan tier, by platform, by acquisition channel
AARRR Funnel Dashboard
Stage | Metric | Current | Target | Status
----------------|-------------------------|----------|----------|--------
Acquisition | New signups/week | 1,240 | 1,500 | At Risk
Activation | Completed onboarding | 62% | 70% | At Risk
Retention | Week-4 retention | 34% | 40% | Off Track
Revenue | MRR | $48,200 | $55,000 | At Risk
Referral | Viral coefficient | 0.3 | 0.5 | Off Track
Overall Funnel Health: NEEDS ATTENTION
Priority Focus: Retention > Activation > Acquisition
Cohort Retention Table
Cohort | Week 0 | Week 1 | Week 2 | Week 4 | Week 8 | Week 12
-----------|--------|--------|--------|--------|--------|--------
Jan W1 | 100% | 68% | 52% | 38% | 28% | 22%
Jan W2 | 100% | 71% | 55% | 41% | 30% | --
Jan W3 | 100% | 65% | 49% | 36% | -- | --
Jan W4 | 100% | 72% | 58% | -- | -- | --
Feb W1 | 100% | 70% | -- | -- | -- | --
Trend: Week-1 retention stable (65-72%). Week-4 improving (+3pp MoM).
Usage Guide
Define Before You Measure: Use the metric definition card for every KPI. If two people define a metric differently, the dashboard is useless.
Start with 5 Metrics: Resist the urge to track 50 things. Pick your North Star metric and 4 supporting metrics that explain movement in the North Star.
Build the Funnel First: Map your AARRR funnel before building dashboards. The funnel tells you WHERE to look; dashboards tell you WHAT happened.
Cohort Everything: Aggregate metrics hide problems. A flat DAU number might mask declining retention offset by increased acquisition — cohorts reveal truth.
Automate Alerts: Set thresholds for every metric. You should hear about problems from alerts, not from your CEO.
Alert Threshold Configuration
metric: daily_active_users
warning_threshold: 12000
critical_threshold: 10000
comparison: below
window: 24h
notify: [pm-team, eng-oncall]
metric: error_rate
warning_threshold: 1.0
critical_threshold: 5.0
comparison: above
window: 1h
notify: [eng-oncall, eng-lead]
metric: p95_latency_ms
warning_threshold: 500
critical_threshold: 1000
comparison: above
window: 15m
notify: [eng-oncall]
Best Practices
- One metric, one owner — if nobody owns it, nobody investigates when it drops
- Define "core action" precisely — logging in is not engagement; creating/editing/sharing is
- Compare cohorts, not time periods — "retention improved" means nothing without cohort context
- Show trailing averages — daily metrics are noisy; use 7-day moving averages for trends
- Segment by default — "DAU is up" matters less than "DAU is up on iOS, flat on Android"
- Review thresholds quarterly — as your product grows, static thresholds become meaningless
- Automate what you review weekly — if you look at it every week, it should be a dashboard, not a query
This is 1 of 11 resources in the PM Toolkit Pro toolkit. Get the complete [Product Metrics Dashboard Templates] with all files, templates, and documentation for $39.
Or grab the entire PM Toolkit Pro bundle (11 products) for $129 — save 30%.
Top comments (0)