Beacon (player beacon)
A player beacon, in video streaming, is a small data message that a video player sends to an analytics server to report playback events, such as play, pause, errors, quality changes and stalls. Beacons are sent automatically in the background while a video plays. Video analytics tools combine them to rebuild each viewing session and measure quality and engagement.
Why it matters
Beacons are how a business learns what actually happened in each viewer's player. Without them, playback problems on specific devices or networks stay invisible until users complain. The design of the beacon pipeline also affects data accuracy, battery use and how quickly problems show up on dashboards.
How it works
- An analytics SDK inside the video player listens for events such as play, pause, stall, error and quality change.
- Events are packed into small messages with details like timestamp, video, device and playback position.
- The SDK sends them to a collection server in the background, often in batches to save bandwidth.
- The server joins all beacons that share a view ID to rebuild the full viewing session.
What data does a video player beacon send?
A video player beacon sends details of what just happened during playback, plus context. Typical fields include the event type, timestamp, playback position, video ID, view ID, current bitrate or resolution, error codes and device, browser and network details. Some beacons also carry custom fields set by the business, such as subscription tier or experiment name.
Do player beacons slow down video playback?
Well designed player beacons do not noticeably slow playback. They are small, sent in the background and often batched, so they use little bandwidth. Browsers also provide a Beacon API (navigator.sendBeacon) built to send data without blocking the page. Problems usually come from sending too many events or running heavy code inside the player.
Where it's used
OTT services and live sports streamers rely on player beacons to spot when viewers in one region or on one device start hitting errors or stalls, so they can fix problems during an event.
Where it usually goes wrong, and how FastPix handles it
Homegrown beacon setups often miss events, send inconsistent fields across platforms or break when the player is updated, leaving gaps that make playback data hard to trust.
The FastPix Video Data SDK collects playback data from the player for every view, with up to 10 custom dimensions, so your team gets consistent playback data across platforms without building and maintaining its own beacon pipeline.
By the numbers
- The W3C Beacon specification defines asynchronous, non-blocking delivery of data from a web page, with requests guaranteed to be initiated before the page is unloaded. (W3C: Beacon)
- CTA WAVE's Common Media Client Data specification includes an optional event mode in which players send batched reports in an HTTP POST body, triggered by events such as play state changes or errors. (CTA WAVE: Common Media Client Data (CTA-5004-A))
