Product Telemetry & Experimentation Management › Product Usage Analytics

Product Usage Analytics

BC-4280.30 Level 2 Software & Technology 29 providers 55 API surfaces 15 rated strong or better

Analytical views of product usage including funnels, retention cohorts, and feature engagement.

Product Usage Analytics (BC-4280.30) is a level-2 business capability under Product Telemetry & Experimentation Management in the Software & Technology model. The catalog holds 55 API surface(s) from 29 provider(s) that can perform some part of it, 15 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions
API Evangelist annotation. Audience: b2bconsumer

Product Usage Analytics: the analytics SDKs inside consumer apps (Amplitude, Firebase) in the fitness-nutrition blueprint.

This audience annotation is API Evangelist's, not part of the Turbo EA model — API Evangelist capability extension — https://apievangelist.com, CC BY-NC-SA 4.0.

Sub-capabilities

Funnel Analytics BC-4280.30.10

Funnel analysis of conversion and drop-off across product journeys.

no catalog coverage

Retention Cohort Analytics BC-4280.30.20

Cohort-based analysis of user retention over time.

no catalog coverage

Feature Engagement Reporting BC-4280.30.30

Reporting on engagement with specific features across the user base.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 7 Complete, well-documented, and agent-ready
Strong 8 Solid coverage with minor gaps
Developing 8 Usable, with meaningful gaps to close
Thin 5 Limited public surface area
Emerging 1 Early or largely undocumented
This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Product Usage Analytics. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →