Connecting product usage data
API-key setup, the event schema, and how usage signals map to the product-usage health factor.
Feeding product usage
The Product Usage health factor is only as good as the data behind it. There are three ways to feed it:
- Ingest API — in Admin Console → Developer → API Keys, create a key with the
ingest:writescope, then POST usage to/api/ingest/v2/events(or/feature-usage). Events carry an account identifier, a metric or feature, a timestamp, and a value. - Telemetry SDK — drop the
telemetry.jssnippet into your product to stream events as users act. Name events to match a Feature key (Admin → Catalogs → Features) so they also power adoption reports. - CSV import — Admin Console → Data → Import Data, entity Usage (columns like
dau,mau,featureAdoption,seatsActive, matched by account name + date).
However it arrives, usage rolls up nightly into the seat-utilization and adoption signals that feed the automated Product Usage measure.
Related: *How health scores are calculated* · *Connectors & Data Hub* · *API keys, the Developer API & MCP*
More in Health Scoring
- How health scores are calculated
- Configuring scorecard weights for your business
- Health thresholds: green, yellow, red
- Logging a health score manually
- Understanding health trends and velocity
- Health score overrides: when and how
- Churn & expansion scoring factors
- Predictive Scoring: churn & expansion config
- Per-product-line health