Customer KPI Pack — Definitions, Templates & Decision Guidance

A practical, decision-focused catalog of customer, retention, funnel and CX KPIs with clear formulas, data requirements, ownership suggestions, tolerances/alert guidance, sample SQL/pseudocode, segmentation notes, and visualization examples. Designed so product, growth, and CX teams can pick and implement metrics that map directly to actions.

Welcome — Measure to decide, not to report

This KPI pack gives product, growth, CX and customer teams ready-to-use metric templates tied to decisions. Each KPI entry includes a clear definition and formula, data source guidance, suggested owners, tolerance bands or alert rules, and concrete actions that metric should trigger. Use these as practical starting points — adapt denominators, frequencies and thresholds to your product, business model and data availability.

How to use this pack

  1. Pick KPIs that are tied to a decision or policy (what should happen if the metric crosses a threshold?).
  2. Confirm data source and stability before operationalizing a KPI.
  3. Assign a clear owner who is accountable for data quality and the follow-up actions.
  4. Set tolerances/alerts and a documented playbook of actions for each band (green/yellow/red).
  5. Segment and cohort the metric when it matters (by acquisition channel, plan, geography, device).

Canonical KPI template (copy & reuse)

KPI name — short, outcome-focused.

Purpose — why this matters and what decision it supports.

Definition / Formula — numerator, denominator, time window. Example: "30-day retention = % of users active in 30 days after signup."

Frequency — daily / weekly / monthly / cohort

Data sources — event names, tables, IDs, unreliable sources to avoid.

Owner / steward — role (e.g., Growth PM, Product Analytics).

Tolerances & alert rules — green/yellow/red bands and change-based triggers (e.g., >5% week-over-week drop triggers investigation).

Decision guidance — specific actions for each band.

Segmentation / cohorts — suggested breakdowns.

Sample SQL / pseudocode — a short snippet for common implementations.

Visualization — recommended chart type and annotation notes.

Curated KPIs (grouped by outcome)

Acquisition & Activation

  • New Users (by acquisition channel)

    Definition: Count of new signups in window. Owner: Growth. Frequency: daily/weekly.

    Decision guidance: If a channel falls >25% below expected cohort size, pause/inspect expensive spend.

  • Activation Rate

    Definition: % of new users who complete a defined activation event within X days. Formula: activated_new_users / new_users (X-day window).

    Visualization: funnel conversion or stacked bar by channel. Action: low activation for a channel → prioritize onboarding experiment for that cohort.

  • Time to Activation (median)

    Decision guidance: longer times indicate UX friction; target improvements to reduce median.

Engagement & Habit

  • DAU / MAU and Stickiness (DAU/MAU)

    Use to detect engagement changes. Owner: Product/Analytics. Segment by plan or persona.

  • Core Action Frequency

    Counting the product's primary action per active user per week. Action: falling frequency → prioritize retention experiments.

Retention & Churn (cohort-based)

  • Retention curve (cohort retention)

    Definition: % of cohort active at each timepoint. Use cohort retention curves rather than single-point snapshots to understand long-term decay.

    Visualization: cohort retention heatmap or line chart. Action: compare cohorts by acquisition source to prioritize channels that deliver long-lived users.

  • Cohort Churn Rate

    Definition: 1 - retention for the cohort window. Use cohort methodology to avoid denominator drift.

    Sample pseudocode: create cohort by signup week, count active events in subsequent weeks, compute retention.

Financial & Unit Economics

  • ARPU / ARPPU

    Definition: revenue / active users (or paying users). Useful for tracking per-user monetization trends.

  • CLTV (multiple approaches)

    Approach A — Simple historical: average revenue per user × average customer lifetime (in months/years).

    Approach B — Cohort-based: sum of revenues from a cohort over X months / cohort size.

    Approach C — Predictive: model expected future revenue per customer (requires analytics modeling).

    Decision guidance: use cohort-based first; move to predictive when stable training data exists.

  • LTV : CAC

    Definition: CLTV divided by Customer Acquisition Cost. Rule of thumb depends on business model, but LTV:CAC < 1 indicates unsustainable acquisition.

    Decision guidance: set acquisition pacing or creative changes if ratio drifts below target.

Funnel & Conversion Metrics

  • Visit → Signup conversion
  • Signup → Activation conversion
  • Activation → Paying conversion
  • Track absolute conversion and relative drop between stages; instrument event-level data and funnel abandonment reasons where possible.

Customer Experience & Support

  • NPS / CSAT

    Include sample sizes, segment by cohort and stage, and attach verbatim feedback for qualitative insight.

  • First Response Time / Resolution Time

    Operational CX metrics that directly map to support staffing and SLA decisions.

Sample SQL / pseudocode snippets (illustrative)

Note: adapt to your event names and schema.

<!-- cohort retention pseudocode -->
SELECT cohort_week,
       weeks_after_signup,
       COUNT(DISTINCT user_id) AS active_users
FROM events
WHERE event_name = 'some_active_event'
GROUP BY cohort_week, weeks_after_signup;
  

Use rolling windows to compute week-over-week deltas and percent changes for alerting.

Recommended alert rules & tolerances (examples)

  • Immediate alert (red): metric falls >10% absolute OR >25% relative week-over-week for primary KPIs (e.g., activation rate, 28-day retention).
  • Warning (yellow): metric falls between 5–10% absolute or 10–25% relative week-over-week.
  • Green: within expected weekly variance; still monitor seasonality and cohort shifts.

Segmentation & cohort advice

Always segment by acquisition channel, plan type, geography, device, and any A/B experiment exposure. Look for hidden confounders such as bot traffic, duplicate accounts, or backend errors that can create misleading signals.

Common pitfalls & how to avoid them

  • Avoid ambiguous denominators — always document numerator and denominator precisely.
  • Do not rely on a single vanity metric without an associated decision rule.
  • Beware of mixing cohort and non-cohort calculations — cohort methods avoid denominator drift for retention/churn.
  • Ensure ownership and data quality responsibilities are explicit.

Suggested visualizations

  • Cohort retention curve / heatmap
  • Funnel conversion chart with step drop annotations
  • LTV by cohort line chart
  • Churn waterfall or stacked area showing reasons
  • Segmentation bar charts (channel, plan, geography)

Implementation checklist

  1. Choose 3–6 core KPIs with clear owners and decision rules.
  2. Implement stable event instrumentation for numerator/denominator.
  3. Create cohorted retention and funnel views in BI tool.
  4. Define alert thresholds and an incident/playbook for red/yellow events.
  5. Publish KPI definitions in a shared glossary and review quarterly.

Next steps & capability opportunities

Consider these practical enhancements:

  • Convert the KPI template into an Interactive form so teams can create and store KPI definitions (owner, formula, thresholds) and keep an organizational glossary.
  • Add calculators for CLTV and LTV:CAC to quickly test scenarios for different cohort assumptions.
  • Bundle this pack into a team collection that includes sample dashboards, SQL snippets, and alert playbooks for product/growth teams to copy and tailor.

Image search phrase: customer churn cohort chart, retention curve

Adapt these templates to your context — consistent definitions and clear decision links are the difference between noise and useful insight.


Discussion

Comments and conversation will live here.