Product Telemetry & Experimentation Management
Instrumentation, governance, and analysis of product usage telemetry, and the design and execution of feature experiments that shape product decisions.
Product Telemetry & Experimentation Management (BC-4280) is a level-1 business capability in the Software & Technology model. The catalog holds 39 API surface(s) from 16 provider(s) that can perform some part of it, 6 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.
Sub-capabilities
Product Telemetry Instrumentation BC-4280.10
Capture of product usage events from client and server runtimes against defined event schemas.
Telemetry Quality & Governance BC-4280.20
Schema governance, pipeline quality monitoring, and privacy filtering of product telemetry.
Product Usage Analytics BC-4280.30
Analytical views of product usage including funnels, retention cohorts, and feature engagement.
Experimentation Programme Management BC-4280.40
Methodology, design review, and adjudication of experiments that drive product decisions.
A/B Test Execution BC-4280.50
Configuration, targeting, and monitoring of running A/B and multivariate tests.
Customer Insight Synthesis BC-4280.60
Synthesis of quantitative and qualitative signals into product decisions and decision memos.
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.
- iOS exemplar 75.3
- Optimizely exemplar 72.8
- Matomo exemplar 69.1
- Netlify exemplar 68.8
- GitHub Copilot strong 64.7
- Openwork strong 55.9
- Uniform developing 52.4
- PostHog developing 51.4
- Pomo developing 48.5
- Posit developing 46.9
- Depict.AI developing 45.9
- Wispr AI developing 45.0
- GitLab CI/CD thin 37.0
- GrowthBook thin 30.2
- Dynamic thin 30.0
- Convert thin 29.7
Workflows that realise this capability
Arazzo workflows whose own sourceDescriptions call APIs that carry this
capability. The link is derived, not asserted: each workflow declares
x-realizes-capability-ids with the spec and confidence behind it.
-
GitHub Copilot Organization Metrics Report
— github-copilot
· Product Usage Analytics
BC-4280.30 -
GitHub Copilot Team Metrics Report
— github-copilot
· Product Usage Analytics
BC-4280.30