Analytics & Reporting
Ship player and backend events straight to the analytics stack you already trust — Google Analytics / GA4, Conviva, Mux Data, Youbora (NPAW), Adobe Analytics, New Relic, mParticle or your own data warehouse — so product, ops and content teams work from one source of truth.
Own basic realtime analytics
Built-in live dashboard for concurrent viewers, top titles and playback health — no third-party required.
Google Analytics / GA4
Audience, acquisition and engagement reporting out of the box.
Conviva & Mux Data
Real-time QoE: rebuffering, startup time, bitrate and failures.
Youbora / Adobe
Plug into NPAW Youbora or Adobe Analytics for enterprise reporting.
New Relic
APM, backend traces and infrastructure alerts end-to-end.
mParticle
Customer data platform routing events to any downstream tool.
Warehouse export
Stream raw events to BigQuery, Snowflake or S3 for custom BI.
Quality of experience and product analytics are different jobs
QoE analytics answers whether playback worked: startup time, rebuffering ratio, average bitrate, playback failures and where each of them is concentrated by device, region and CDN. Product analytics answers whether the service works: which content is watched, how far into it people get, where they drop out of signup, what brings them back.
They need different tools and different audiences, and conflating them is why so many streaming dashboards get built and then ignored. Conviva and Mux Data are built for the first; GA4, Adobe and a warehouse are built for the second.
The event schema is the hard part
The value of any analytics stack comes from a consistent event schema across every platform. If the Roku channel emits a play event with different fields or different timing from the Android TV app, cross-platform reporting quietly becomes wrong - and it is very hard to notice, because the numbers still look plausible.
That means defining the events once - play, pause, seek, bitrate change, error, ad start, ad complete - with a shared payload, and implementing them the same way in every client. Doing it up front costs a fraction of what re-instrumenting six apps costs later.
Choosing a stack and staying compliant
Events can be shipped to whichever stack you already trust - GA4, Conviva, Mux Data, NPAW Youbora, Adobe Analytics, New Relic, mParticle - or streamed raw to BigQuery, Snowflake or S3 for your own BI. A built-in realtime dashboard covers concurrent viewers, top titles and playback health without requiring any third party.
Under GDPR, viewing behaviour tied to an account is personal data, so retention, the legal basis for processing and whether a given third-party tool is acceptable are decisions to make before instrumentation rather than after. Self-hosted or cookieless options - the approach this website itself uses with Matomo - avoid a consent banner entirely.
Frequently asked questions
- Do we have to use a third-party analytics platform?
- No. The platform includes a realtime dashboard for concurrent viewers, top titles and playback health. Third-party tools are an option when you need deeper QoE or product analysis.
- Can events go to our own data warehouse?
- Yes - raw events can be streamed to BigQuery, Snowflake or S3 alongside, or instead of, a hosted analytics product.
- How is GDPR handled?
- By deciding legal basis and retention before instrumentation, minimising what is collected, and choosing tools accordingly. Cookieless and self-hosted analytics remove the need for a consent banner in many cases.