Every OTT viewer-analytics program starts the same way: put an SDK in every app. One for iOS, one for Android, half a dozen smart TV families, and two generations of set-top box. Each integration costs engineering weeks. Each one slows an app release.
For operators running their own CDN, there is a simpler answer: skip the SDK entirely. Every OTT session, live or VOD, already passes through that CDN. With CMCD, the delivery layer now sees what the player sees. PILOT Analytics turns your CDN into the measurement layer: player-level insight on every device, with nothing to install in any app.
The SDK Tax Gets Paid Three Times
SDK-based OTT analytics bills you in three currencies: license fees, integration engineering on every platform, and slower app releases forever after. The work never finishes. Every player update, app release, or SDK version bump reopens it.
The return on that spend is partial coverage. Legacy set-top boxes and minority smart TV platforms rarely justify the integration cost, so they stay dark. Yet those devices are over-represented in support tickets. The viewers you most need to see are the ones the SDK model leaves out.
There is a data-ownership cost too. SDK vendors typically process viewer telemetry in their cloud, on their retention terms. Server-side analytics runs against your own CDN logs, in your own deployment. Your viewer data stays yours.
CMCD Turns the CDN Into Your Analytics Agent
CMCD (Common Media Client Data, the CTA-5004 specification) changed the economics. Players attach standardized playback telemetry to the requests they already send. The major open-source and commercial players now ship it as a configuration option. Enabling CMCD is a flag, not a development project.
PILOT Analytics reads those signals alongside the CDN logs and reconstructs every OTT session server-side. Each session record carries rebuffering events with duration, the full bitrate history, and pause, seek, and trick-play behavior. It captures audio language switches, subtitle usage, and the device, brand, and player software behind each user agent. Sessions are classified as live, VOD, catch-up, or nPVR, so timeshifted audiences stop hiding inside linear numbers. A network dimension separates an ISP peering problem from a platform problem.
No agents are installed in any app. Coverage starts the day the analytics attaches to the CDN, and it includes every device that ever requests a stream from it.
One Data Set for Every Team That Argues About Quality
The same session records feed seven views, each answering a different budget holder’s question. Operations watches delivery health: concurrent sessions, throughput, delivered volume, cache hit ratio, and HTTP errors. Content and commercial teams read engagement: unique viewers, viewed hours, and channel and asset rankings, with timeshift viewing counted as what it is.
Product teams see which devices, brands, and player stacks carry the audience, which settles device-support prioritization with evidence. Support teams search any viewer’s session and get a per-session experience grade, its bitrate history, and its error pattern. “It buffers sometimes” becomes a diagnosable event with a timestamped cause. Security teams get fraud detection: credential sharing and session hijacking surfaced in real time, connected to enforcement in NEA CDN®, with watermarking IDs tied to sessions for piracy investigations.
One pipeline, one data model, and no reconciliation meetings about whose number is right.
Deployment Is No Longer a Platform Project
Analytics platforms have a habit of becoming their own infrastructure project. The recent PILOT Analytics releases went after this directly. Configuration moved from deployment files into the user interface, including the collection agents themselves. The operations team that uses the system now tunes it, without a Kubernetes specialist in the loop.
It deploys on premises or on AWS, runs on a single node where the footprint demands it, and upgrades through PILOT Manager like the rest of the Ateme stack. The cost scales with your CDN estate, not with the number of device platforms marketing wants to launch next year.
Where an SDK Still Earns Its Keep
Server-side visibility ends at the delivery layer, and the boundary deserves honesty. UI navigation, content discovery, DRM license failures, and ad-SDK errors happen entirely on the client. They never touch a CDN log. CMCD depends on players sending it; where a player predates CMCD support, sessions still reconstruct from delivery logs with less playback-state detail. And where no subscriber identifier is passed, unique-viewer counts rest on derived identifiers that shared IP addresses can blur.
If you already run an instrumented app estate you trust, server-side analytics is the cross-check and the coverage extension for everything you could not instrument. If you are deciding where the next analytics dollar goes, the calculus has shifted.
One Question for the Next Budget Round
What did viewer measurement cost in engineering weeks last year, and what share of your audience can it still not see? Your CDN already knows the answer to the second question. The interesting decision is how much you are prepared to keep spending on a second copy of data it already holds.
Explore related insights
About the Author
CDN Product Manager & OTT Streaming Solutions Manager at Ateme
Mark brings 18+ years of experience in OTT streaming & Content Delivery Networks. With a background spanning product management, solution architecture, and business development, he helps content owners, telcos & network operators navigate modern streaming infrastructure, from CDN strategy and live video delivery to cloud-native OTT platform design.
At Ateme, Mark leads product direction for the NEA CDN portfolio and drives OTT & streaming solution strategy for major telcos and network operators worldwide, having previously spent 5 years as a Global Solution Architect. Prior to Ateme, he held solution architecture and business development roles at Velocix, part of Nokia/Alcatel-Lucent’s IP Video division.