The most efficient way to capture detailed, real-time metrics is here: Standardized and without the complexity of client-side SDKs
The wait is over! We are thrilled to share that Common Media Client Data (CMCD) Version 2 has been officially released as CTA-5004-A by the Consumer Technology Association’s Web Application Video Ecosystem (WAVE).
This release represents a massive collaborative effort across the streaming industry. We are incredibly proud to have been an active contributor alongside industry leaders and partners in the working group that shaped this specification. It was a joint collaborative effort to push forward a standard that already sees substantial support across the streaming industy.
At EINBLIQ.IO, we have always championed lighter integration. Our 1-line adapters already make life easier, but CMCD v2 takes “low maintenance” to an entirely new level.
Here is why we see this as a pivotal moment for streaming analytics strategies:
The two disruptors in CMCD v2
While v1 was a great step forward for individual CDN optimization, v2 is a holistic analytics foundation without the need for client-side SDKs.
#1 A leap in metrics compared to CMCD v1
In the past, standardized data was often too thin for deeper debugging. CMCD v2 changes that by capturing a much richer dataset:
-
- True playback state tracking: We can now see exactly when a user is starting, buffering, seeking, or pausing, rather than deriving this on segment download flow and timing.
- Standardized error reporting: Player error codes are now passed natively, making root-cause analysis significantly easier and faster.
- Multi-content & ad support: The spec now natively handles complex streams, including Dynamic Ad Insertion (DAI), allowing you to distinguish performance between your primary content, ad breaks and the combined experience.
#2 Endpoint flexibility and real-time analysis
In v1, data was strictly piggybacked onto requests to the CDN
CMCD v2 introduces Event Mode:
-
- Direct-to-collector: You can now configure the player to also send data directly to a custom 3rd-party endpoint (like EINBLIQ.IO) via HTTP POST.
- True real-time: By bypassing the CDN log delay, you get a real-time view.
- Smart triggers: You decide when data is sent: periodically or triggered by specific events like buffer starvation or errors, giving you granular control over your data volume.
Business impact: Reducing the “maintenance tax”
We have witnessed the pain of maintaining heavy analytics SDKs: Every time a platform API changes or a player updates, engineering teams have to check and potentially adapted the tracking code.
CMCD v2 has the clear potential to replace proprietary analytics SDKs entirely. By moving the intelligence into a standardized format that players support natively, you dramatically reduce code complexity and maintenance overhead.
-
- Zero-day stability: When platforms update, the standard remains.
- Rapid onboarding: Because EINBLIQ.IO is built to ingest this standard natively, setup with us is possible in less than half a day. And don’t worry, SDK support is still given, e.g. for legacy hardware like HbbTV devices.
Looking ahead with EINBLIQ.IO
We didn’t just watch this standard emerge; we helped define it.
-
- See it in action: Check out our early CMCD v2 prototype
- Be a step ahead: We will soon be announcing the EINBLIQ.IO CMCD v2 Partner Program. This initiative is designed for streaming services who want to lead the charge in standardization, offering exclusive migration support and early access to our next-gen, SDK-less analytics.
For the first time, the streaming industry is ready to move to an efficient standardized analytics specification. This is relevant for everybody in the domain.
As active contributors to the new spec, we know exactly how to help you migrate away from legacy solutions and unlock the full potential of v2 quickly.
Want to discuss the specific potential of CMCD v2 for your setup?
📅 Schedule a quick call with us today.