Bitmovin: what does a video player report besides the video request?

Is playing a video the same as measuring it?

Bitmovin supplies playback technology and a separate analytics collector. A player retrieves and displays media. A collector observes player events and sends measurement records. The two can be connected, but they serve different purposes. Bitmovin describes analytics setup as attaching a collector that listens to player events. Bitmovin collector setup.

Its analytics field reference includes buffering, startup timing, playback technology, approximate city/country, advertising fields and optional customer-provided user IDs or custom data. These are product capabilities, not a checklist of fields proven present in Buienradar. An app can configure different fields or omit optional ones. Analytics field reference.

What can viewing telemetry reveal?

Hypothetical example: an event sequence records a particular video starting, buffering twice and stopping halfway. That can diagnose a poor connection. If attached to a stable ID, repeated sequences can also describe what one installation watches and when it stops. The measurement can therefore have both a technical purpose and an interest in viewing behaviour. This is an explanation of possibilities, not an observed user history.

The important questions are what the app sends, which identifier accompanies it and whether the collector is required for playback. A video stream request itself also reveals network metadata to the service delivering it; removing an analytics collector does not remove that functional exchange.

What did we find in Buienradar?

Buienradar 7.4.8 passes enabled analytics configurations for both the Bitmovin player and its source. The identified analytics ingress is analytics-ingress-global.bitmovin.com. The same audit separately traces a Smartocto video-play request; that is another collector, not another name for Bitmovin. Pinned Buienradar audit, related media services.

What changes after patching?

Disable tracking changes the analytics configuration boundary so it returns the player/source without attaching the collector. Bitmovin licensing calls and content playback remain. It would be inaccurate to say “all Bitmovin traffic is blocked”: licensing has a continuing functional role.

This finding is based on the inspected configuration, code path and patched output. It does not establish the exact fields transmitted in a real viewing session, the provider's retention period or the behaviour of an unknown future remote player integration.

Evidence reviewed 28 October 2026. Read how tracking works and our methodology.