Playback Error Tagging

JW Player's analytics track playback errors and buffering across every video and device type. A Beam agent reads that error data on a schedule, checks the error rate against the account's threshold, and applies an approved tag such as needs re-encode to any video that crosses it. The media team gets a notification with the affected video IDs. Videos with mixed or borderline error signals, or ones already flagged for another reason, get routed to a person instead of tagged directly. The agent does not touch encoding settings, players, or delivery configuration, it only applies tags within the rule the account has approved.

Playlist Membership Rules

JW Player organizes video into playlists built from tags and metadata fields like category or series. A Beam agent reads new and updated video metadata, checks it against the account's approved playlist rules, and adds or removes the video from the matching playlist. The content team gets a summary of what moved and why. Videos with missing, conflicting, or unusual metadata, like a title that could fit two categories, get routed to a person to sort instead of placed automatically. The agent works only within playlists and rules the account already has configured, it does not create new playlists on its own.

Viewer Drop-Off Alerts

JW Player analytics report where in a video viewers stop watching. A Beam agent reads drop-off data for recently published videos, compares it against the account's expected retention range, and sends an alert to the content team when a video falls noticeably short. The alert includes the timestamp where most viewers leave, so an editor can check pacing or a broken segment. Videos still in their first day of low counts, where drop-off data is not yet reliable, get held back until views accumulate. The agent does not edit or remove any video, it only reports on activity already in JW Player.