CMCDv2: Leveling Up Your Video Streaming Telemetry
Blog post from Fastly
Common Media Client Data (CMCD) was created to bridge the gap between video-player telemetry and CDN logs by attaching standardized key/value data to media requests, enabling streaming operators to correlate buffering, quality changes, network conditions, CDN performance, and viewer sessions across devices and providers. CMCDv1 also supports request hints that can help CDNs prefetch likely subsequent content, and its open adoption has improved interoperability among players, CDNs, and monitoring platforms. CMCDv2 remains backward-compatible with this Request Mode while expanding its metrics and adding Response Mode, which reports post-download information such as time to first and last byte and HTTP response codes, and Event Mode, which captures asynchronous playback events such as pauses, backgrounding, and manual quality changes. New measures include buffer targets, degradation severity and frequency, and distinctions between main content and advertising segments. Adoption may require updated player and analytics support, careful event selection and data-pipeline planning due to increased telemetry volume, and consideration of ad blockers when data is sent directly to third-party endpoints.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Real-time | 9 | 649 | 155 | 80 | -85% |
| Observability | 2 | 472 | 102 | 54 | -85% |
| Data Pipeline | 1 | 34 | 23 | 18 | -90% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.