Product Telemetry & Experimentation Management

BC-4280 Level 1 Software & Technology 20 providers 41 API surfaces 12 rated strong or better

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 41 API surface(s) from 20 provider(s) that can perform some part of it, 12 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

Sub-capabilities

Product Telemetry Instrumentation BC-4280.10

Capture of product usage events from client and server runtimes against defined event schemas.

8 providers, 8 API surfaces

Telemetry Quality & Governance BC-4280.20

Schema governance, pipeline quality monitoring, and privacy filtering of product telemetry.

2 providers, 2 API surfaces

Product Usage Analytics BC-4280.30

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

5 providers, 9 API surfaces

Experimentation Programme Management BC-4280.40

Methodology, design review, and adjudication of experiments that drive product decisions.

2 providers, 2 API surfaces

A/B Test Execution BC-4280.50

Configuration, targeting, and monitoring of running A/B and multivariate tests.

9 providers, 19 API surfaces

Customer Insight Synthesis BC-4280.60

Synthesis of quantitative and qualitative signals into product decisions and decision memos.

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 4 Complete, well-documented, and agent-ready
OptimizelyExperiments1 API78.0iOSAppStoreVersionExperimentTreatmentsAppStoreVersionExperiments2 APIs73.1NetlifysplitTest1 API68.1UnityEvents1 API67.9
Strong 8 Solid coverage with minor gaps
MatomoAbTesting1 API65.8GitHub CopilotCopilot Metrics1 API64.1AppLike GroupAppevents1 API59.2UniformTests1 API58.6PositInstrumentation1 API56.6OpenworkTelemetry1 API56.4Pomouser-activity1 API56.1FreshpaintEvents1 API55.1
Developing 5 Usable, with meaningful gaps to close
PostHogevent_schemaseventsexperiment_holdoutsexperiment_saved_metrics11 APIs51.1Wispr AIAnalyticsAnalytics RegistryTeam Insights3 APIs48.1GitLab CI/CDusage_data1 API45.3PypestreamInsights1 API42.6GameAnalyticsCollection1 API40.0
Thin 3 Limited public surface area
miso.aiExperiment APIs1 API37.0GrowthBookexperimentssnapshotsvisual-changesets3 APIs33.9ConvertExperience SectionsExperience VariationsExperiencesExperiences Reports7 APIs28.5

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.

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 Telemetry & Experimentation Management. 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 →