We’ve added support for error categorization in the Objective-C Core SDK. Error details are now sent alongside each error sent to Mux and are no longer deduplicated. Watch time will continue to be recorded after an error event is received based on the playhead progression.
Objective-C Core GitHub Release
Objective-C Core SDK docs: sending error events
We’ve added support for error categorization in the Java Core SDK. Error details are now sent alongside each error sent to Mux and are no longer deduplicated.The error event API now allows an error context to be set on the error event directly. Watch time will continue to be recorded after an error event is received based on the playhead progression.
The Metrics, Views, and Errors APIs and reports now support the metric_filters[]
parameter that allows filtering the views included in the results based on one or more metric values. For example, a filter can be added to only report on views with a Rebuffering Percentage greater than 5% using the Dashboard UI or using the metric_filters[]
parameter (metric_filters[]=rebuffer_percentage>0.05
). This feature is available to customers on a Media plan.
We’re excited to announce that the Mux Data SDK for Media3 is now out of public beta! Version 1.0.0 of our SDK for Media3 has full feature parity with our ExoPlayer SDK, plus lots of internal improvements and the ability to automatically detect metadata of the media you play. If you’re ready to migrate over from the old ExoPlayer, check out our dev guide to update your Mux Data integration.
Read more:
Mux Data now supports Video Startup Failure Percentage in the Historical Dashboard & API. This metric indicates failures that occur prior to the user seeing the first frame of video, be it ads or content, helping identify issues that are specific to the video loading time.
Video Startup Failure Percentage was recently released for the Monitoring Dashboard & API, and is now supported in Historical, allowing customers to track this metric across significantly larger periods of time.
Mux Data can now track Video Startup Failure Percentage in the Monitoring Dashboard & API.
Video Startup Failure is defined as playback failures that prevent the user from seeing the first frame of video, be it video content or ads. This metric is a subset of Playback Failures.
At the event level, Video Startup Failures occur when a viewstart
, play
, or adbreakstart
event is triggered but an error
event occurs before playback begins, aka playing
or adplaying
event is not received, suggesting that playback never began.
Mux Data now has a new Monitoring Breakdown Timeseries API that lets you get metric breakdowns in a timeseries format, with 5-seconds interval data points. You can pass a `timeframe` parameter to specify the time range of the data you want, with its default being the 5 minutes period up to 15 seconds prior to the current unix timestamp. You may also use the `limit` parameter to control the number of breakdowns you would like to include in the individual 5-seconds data. For more information, please check out the API spec here.
Mux Data now supports exporting data for View Streaming Exports in JSON format. This makes it much easier to connect the data stream with data stores such as BigQuery and Snowflake. Customers can easily set it up by going to Mux Dashboard -> Settings -> Streaming Export -> New streaming export -> make sure to select “JSON” as the export format.
The fields that are included in the streaming export’s JSON format are identical to what we support in the protobuf format, which can be found in this repo. When new fields are made available, the export needs to be upgraded to receive new fields: Mux Dashboard -> Settings -> Streaming Export -> Click Upgrade to receive the new fields. For more schema management information, check out this guide.
You can now differentiate views that have ads from the ones that don’t in Mux Data. This is done by introducing a new boolean dimension called `view_has_ad`, which is available in both the API and the Mux Dashboard. The boolean value is determined by the existence of the `adplay` event: if the event is given, the `view_has_ad` value will be set to true, and vice versa.
When in the Monitoring page in the Mux Dashboard, open the filters and look for the dimension “View Has Ad”. When in the Metrics page in the Mux Dashboard, the same dimension can also be found in the breakdown table. When in an individual View page, the same field can be found under the “Ads” section.
The field is also available in the Streaming Export and requires the schema to be upgraded to V5.
This version of the Mux Data SDK for AVPlayer adds additional tracking for ad-related metadata, such as ad ID, creative ID, ad tag URL, and more. This update also fixes a bug on tvOS related to seeking.
Version 3.3.0 of the Mux Data SDK for ExoPlayer adds metadata for ad events, including ad ID, creative ID, ad tag url, and more.
This release of the Mux Data SDK for AVPlayer adds the ability to track the number of dropped video frames in a session, as well as adding 5 more custom dimensions to track whatever data is relevant to you and your audience.
The Mux Data View Details page has been enhanced to provide detailed information on failed or canceled requests. This is provided in the user interface for clients that track network level requests. See our documentation for more detail.
We are announcing the exciting and extensive release of the Mux Data SDK v3.0.0 for ExoPlayer. This update converts most of the SDK to Kotlin, removes long-deprecated methods, and adds API changes. A more simple SDK setup process no longer requires you to specify the screen size of your device. You may now pass your `ENV_KEY` through a constructor instead of supplying it to `CustomerPlayerData`. Finally, we removed exposed internal callback methods that likely will not impact you.
For the full list of API changes, check out the release notes on GitHub.
We have released the Streaming Exports for Mux Data Video Views to General Availability. This feature allows you to export Video Views, as they are completed by viewers, to your data infrastructure using a streaming data service, either Amazon Kinesis or Google Pub/Sub. Currently, Streaming Exports are available to customers on Media or custom plans. The docs have more detailed information on integrating and using the Streaming Exports data.
We’ve released v2.7.0
of our Mux Data SDK for ExoPlayer, and it’s a big one. We added support for setting dimension values from HLS session data, and fixed some bugs related to CDN detection. We also added support for ExoPlayer 2.17.1, and the Official Port of ExoPlayer for Amazon Devices. You can update to either version by following Step 1 of our Dev Guide. You can read more about this update in the Release Notes.
We’re pleased to announce the initial release of the Mux Data SDK for Bitmovin Player for Android. The first public version is v0.5.1, and it reports all playback events. Support for Bandwidth, Experiments, and Live Latency is being planned or investigated for the v1.0.0 release. Read more in our Integration guide for the Bitmovin Player Data SDK or the GitHub repository.
You will now see a Get Started page when viewing the Overview page for an environment that has not previously collected video view data. The Get Started page makes it easy to find the Mux SDK for your player, provides links to documentation, and makes the environment key that is needed for SDK integration easier to find.
We’ve added support for tracking experiment values via metadata such as X-SESSION-DATA
HLS tags. The tags override values of the dimensions we track. Once the session data tags on the main playlist are loaded by your player, you may pass them to MuxStats::setSessionData(List<SessionTag>)
in order to track the experiment values. Currently experiments are only supported for HLS streams.
You can now use the Overview page, the new landing page for Mux Data. This page contains an overall snapshot of the engagement, real-time viewership, and quality of experience for your video view activity. This change is rolling out to all users over the next few weeks.
You can now use Mux Data with Kaltura video players to collect engagement and quality of experience metrics. We’ve added new Mux Data SDKs for Kaltura web, iOS, and Android players. To configure and use the SDKs refer to the documentation: Kaltura web SDK, Kaltura iOS SDK, Kaltura Android SDK.