Customer Success dashboard data fields

Define the record before joining systems

Use one account snapshot per reporting date for the leadership view. Keep usage events, subscriptions and tickets in separate detail records. Joining every ticket to every usage event can multiply revenue and counts.

Maintain a mapping between the internal account ID and each system’s identifier. Do not join by company name alone. Decide how parent accounts, subsidiaries and multiple subscriptions roll up before reporting totals.

The field names and measurement rules below are Maestria’s proposed starting specification, not a universal standard or vendor export schema. Adapt them to your business model.

The minimum fields and their source systems

A customer relationship management (CRM) system can hold account ownership. Billing should own subscription amounts; product analytics should own observed activity. Record the actual source for every field, even when your tools differ.

Account identity and ownership

Account ID, source-system IDs, segment and responsible Customer Success Manager (CSM). Map these from your CRM or Customer Success platform. The owner must identify who acts, not merely who last edited the record.

Commercial exposure

Subscription ID, recurring revenue amount, currency, billing interval, subscription status and renewal date. Map amounts and status from billing; confirm contractual renewal dates against the contract system. Define treatment of discounts, one-time fees and currency conversion before summing exposure.

Customer outcome and milestone

Agreed outcome, onboarding start date, first-value milestone, milestone completion date and evidence link. Map these from the success plan or onboarding tracker. A completed setup task is not automatically evidence that the customer achieved value.

Adoption evidence

Critical workflow, eligible users or accounts, active users or accounts, observation window and last qualifying activity date. Map observed events from product analytics. Use the same eligibility unit in the numerator and denominator; login alone need not qualify as adoption.

Risk and unresolved support

Risk ID, reason, severity, detected date, open blocking-ticket IDs and evidence links. Map tickets from the helpdesk and account risks from the CS platform. Preserve the difference between an observed blocker and an inferred renewal risk.

Health and action

Health dimension, underlying measure, score, scoring-rule version, assessed date and validity limit. Add the action owner, next action, due date and closure evidence from the CS platform. A green score without fresh evidence should not hide an overdue action.

Data freshness and completeness

Source observation time, last successful sync, missing-field flag and reporting date. Map these from source records and your data pipeline. Keep “not collected,” “not applicable” and a genuine zero distinct.

Keep dashboard evidence links permission-controlled. Do not copy customer conversations, personal email addresses or agent instructions into a broad leadership view.

Write the metric contract beside the chart

For each measure, record its question, calculation, unit, eligible population, time window, source and refresh schedule. Also name the person responsible for resolving data disagreements.

• Adoption coverage: eligible accounts completing the defined critical workflow divided by eligible accounts in the same observation window.
• Open revenue exposure: recurring revenue attached to distinct accounts with an open qualifying risk, as of the reporting date. It is exposure, not predicted churn or realised loss.
• Overdue actions: open actions whose due date has passed, split by owner and severity. Report missing deadlines separately.
• Evidence coverage: eligible accounts with current required evidence divided by eligible accounts. Set validity limits before deciding whether evidence is current.

These are proposed definitions, not benchmarks. Show counts alongside percentages, exclude duplicate accounts and disclose exclusions. Do not combine revenue currencies without an explicit conversion policy.

Separate customer health from Maestria’s CS Score. Customer health describes account conditions; the CS Score describes reported agent or CSM practice. Neither establishes that an intervention caused retention.

Check the data before the CEO review

Trace a small review sample from each chart back to its source records. Reconcile recurring revenue with billing, check unmatched account IDs and inspect missing observation dates.

Agree how corrections and late-arriving events affect historical snapshots. Keep the original reporting date visible rather than silently mixing old risks with today’s revenue.

Begin with fields your team can maintain. Add a measure only when it changes a decision and someone owns its quality.

Turn the data into better CS practice

Use the AI-to-CSM handoff guide when a risk needs human judgment. It explains the context and ownership a transfer should preserve.

The free CS Assessment identifies gaps across 10 senior CSM skills. Assessment v1 scores reported practice; it does not connect systems or independently validate performance.

The Dashboard Blueprint turns assessment gaps and your business intake into dashboard specifications, not connected dashboard software.

Findings remain separate from these practical guides. There are no aggregated customer assessment findings yet.