Analytics Web Releases
Latest Releases
Stable
2.27.0
4/25/2022
Stable
5/16/2019
2.4.2
Added
- If using deferred license loading via the Player+Analytics bundling mechanism, the license key wasn't being updated in the samples.
Stable
5/13/2019
2.4.1
Added
- Ability to prevent initialization of the Analytics Module for Bitmovin Player v8 by setting
analytics: false
in the config.
Fixed
window.setInterval
leak whenplayer.destroy
was called in theadstarted
callback.- Removed confusing
console.error
on license responses that didn't specify an analytics key.
Stable
5/5/2019
2.4.0
Added
- TypeScript declaration files
- Ability to enable/disable the collector for specific sessions on each call of
player.load
- Starting with Bitmovin Player v8.10, Analytics will get the analytics license key automatically from the player, if a default license is specified in the dashboard.
Fixed
- Collector Sessions that initially started with enabled: false did not report playerStartupTime, pageLoadTime, startupTime. They now get sent with the first enabled startup sample.
Stable
4/14/2019
2.3.0
Added
- Added tracking of used
audioCodec
andvideoCodec
- Tracking of the client's supported video codecs
Fixed
- possible crash of ad module on Safari related to the viewport tracker
Stable
3/24/2019
2.2.0
Added
- Added
config
to analytics configuration - Configure backend url via
analyticsConfig.config.backendUrl
- Error segment tracking
- Sample now contains
errorData
JSON with additional information for Bitmovin 8 errors. - Bitmovin Player v8.3 compatibility
- Improvements to the Ad Module with 8.3 (FallbackIndex and Waterfall level)
Stable
1/16/2019
2.1.1
Added
version
property on all analytics instances to get analytics collector versionplayer.analytics.version
property to get analytics collector versionwindow.bitmovin.analytics.version
property to get analytics collector version
Fixed
- Bitmovin collector no longer pollutes the global scope when used in a requirejs/es6 context
Stable
1/13/2019
2.1.0
Added
- Added ads tracking (Bitmovin 8 only)
- Added bandwith measurements
- Sample now sends
web
in a platform field - AdSample now sends
web
in in the platform field - Sample now contains a
sequenceNumber
field
Changed
- Bitmovin7Adapter now checks if another analytics collector is already registered up
Fixed
- Looping a video (Calling
.play()
afterplaybackFinished
occured) did not correctly generate a new impressionId
Stable
10/23/2018
2.0.0
Added
AnalyticsPlayerModule
classAnalytics.version
returns the version of the analytics collector- Added support for native HTML5 Video playback via the
HTMLVideoElementAdapter
- Added specific adapter classes for each supported player technology
Bitmovin8Adapter
Bitmovin7Adapter
VideojsAdapter
ShakaAdapter
HlsAdapter
DashjsAdapter
HTMLVideoElementAdapter
Changed
- Setup API has been reworked to use JavaScript classes and specific adapters per player technology
Removed
.augment
syntax removed in favor of ES6 classes.register
syntax removed in favor of ES6 classeswindow.bitmovin.analytics
window.bitmovin.analytics.Players
window.bitmovin.analytics.CdnProviders
window.bitmovin.analytics.PlayerModule
window.bitmovin.analytics.version
- Automatic Player detection is deprecated in favor of explicit Adapter creation
Fixed
- Video Bitrate is now correctly reported before the first quality change events in all adapters
- Player version reporting has been improved.
- Fixed incorrect handling of
videoWindowWidth
andvideoPlaybackWidth
in HLS.js and Shaka. - When loading a new video with Bitmovin Player v7 and v8, a new impression id was assigned before the last sample of the old impression has been sent to the server.
- Fixed error being thrown when
hls.destroy()
is called because of a not correctly cleared timeout.
Known Issues
getPlayerVersion
will returnunkown
for video.js if included via npm or requirejs- Not calling
player.load
in the same code-path afternew bitmovin.player.Player()
will skew thePLAYER_STARTUPTIME
metric. - Bitrate Information is not collected when using Native Safari Playback using the
HTMLVideoElementAdapter
. This is due to the limitations of the Browser and not a bug. - The HTML5 adapters and the VideoJs adapter won't assign a new impression id on
Analytics.sourceChange()
- Destroying a Shaka instance will not correctly clear all event handlers on the VideoElement. Re-Using the VideoElement with another Shaka instance will lead to the impression being tracked twice
Stable
10/23/2018
1.7.4
Fixed
- Player detection for Shaka when loaded via require and
window.Shaka
is not available. - Player detection for HLS.js when loaded via require and
window.HLS
is not available. - Beta-Support for Shaka 2.3.7
- Beta-Support for HLS.js 0.7.11
Known Issues
- Shaka/HLS Adapter: Video width/heigth/bitrate is only available after the first videoQuality change event.
Stable
10/4/2018
1.7.3
Fixed
pageLoadType
was not correctly detected for subsequent sessions in the same playerplayerStartupTime
was reported asNULL
instead of0
for subsequent sessions in the same player- Internal improvements and refactorings