Streaming Video & Ads for Browser release notes

Streaming Video & Ads for Browser v3.0.0

Wed, 05 Mar 2025 00:00:00 +0000

New features & enhancements

New event types introduced

VideoAction: This event type represents standard actions related to video playback and interaction.
VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

PageAction
- The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New attributes introduced

We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation for more details.

Impact & actions required

Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
Update implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
Testing & validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional information

For more details on implementing these changes, refer to the updated documentation and integration guides available here. Should you have any questions or require further assistance, please reach out to our support team.

Streaming Video & Ads for Browser v3.1.0

Mon, 09 Jun 2025 00:00:00 +0000

Enhancements

Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

Distribution formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

Streaming Video & Ads for Browser v3.0.1

Sun, 27 Apr 2025 00:00:00 +0000

This minor release of the New Relic Bitmovin Tracker includes important change to error reporting.

Key changes

Error reporting update: The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward.

Upgrade notes

Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.

Streaming Video & Ads for Browser v4.0.0

Tue, 02 Sep 2025 00:00:00 +0000

Feature

Standalone agent

Decoupled from Browser Agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

Streaming Video & Ads for Browser v3.0.0

Wed, 05 Mar 2025 00:00:00 +0000

New features & enhancements

New event types introduced

VideoAction: This event type represents standard actions related to video playback and interaction.
VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

PageAction
- The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New attributes introduced

We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation for more details.

Impact & actions required

Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
Update implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
Testing & validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional information

Streaming Video & Ads for Browser v3.1.0

Mon, 09 Jun 2025 00:00:00 +0000

Enhancements

Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

Distribution formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

Streaming Video & Ads for Browser v3.0.1

Tue, 22 Apr 2025 00:00:00 +0000

This release of the New Relic Dash.js tracker includes important compatibility updates and a change to error reporting.

Key changes

Dash.js player compatibility: This version has been tested and confirmed to be fully compatible with the latest release of the Dash.js Player, ensuring seamless integration and accurate tracking.
Error reporting update: The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward.

Upgrade notes

Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.

Streaming Video & Ads for Browser v4.0.1

Wed, 18 Feb 2026 00:00:00 +0000

Bug fixes

Improved contentBitrate calculation

Issue: The contentBitrate attribute reported the target bitrate from the manifest instead of the actual measured throughput during playback.

Fix: Updated the bitrate calculation method to use getAverageThroughput() from dash.js. This captures the measured average throughput, providing a more accurate, real-time representation of the content consumption rate during playback.

Implementation details

Primary logic: Uses player.getAverageThroughput('video') to retrieve measured throughput
Fallback logic:
- Uses manifest bitrate if throughput measurement is unavailable
- Improves accuracy of video quality monitoring and analytics
Impact:
- More accurate bitrate reporting in New Relic video monitoring
- Better visibility into actual network conditions and video quality
- Improved debugging capabilities for playback issues

Streaming Video & Ads for Browser v4.1.0

Wed, 18 Feb 2026 00:00:00 +0000

What's new

This release introduces three new bitrate metrics providing comprehensive quality analysis for MPEG-DASH streaming, along with important improvements to existing bitrate calculations and dash.js v4/v5 compatibility.

New features

New bitrate metrics

contentManifestBitrate: Maximum combined (video + audio) bitrate from the MPD manifest. Represents the highest possible stream variant available.
contentMeasuredBitrate: Network estimated by the player's Adaptive BitRate (ABR) algorithm, based on measured download throughput. Use this metric to analyze ABR decision-making.
contentDownloadBitrate: Effective download throughput calculated from video segment request data (bytesDownloaded × 8 / downloadTime). This Provides real-time network performance monitoring.

Changes

Updated bitrate calculations

contentBitrate: Returns the video-only bitrate from the active track and excludes audio. Previous versions included combined bitrate.
contentRenditionBitrate: Returns the combined video and audio bandwidth of the active rendition to provide a complete quality picture.

Compatibility improvements

getDashBitrate(): Fixed v4 compatibility issue. Version check now occurs before calling v5-only APIs, preventing errors on dash.js v4.x installations.
getManifestBitrate(): Introduced a smart version detection that uses getRepresentationsByType() on dash.js v5+ and falls back to getBitrateInfoListFor() on v4.x.

Bug fixes

Removed duplicate getPlayhead() method definition
Removed console.log statement from getTrack() error handler

Bitrate metrics overview

Attribute

Type

Description

contentBitrate

Video-only

Bitrate of the currently active video track

contentRenditionBitrate

Combined

Video + audio bandwidth of active rendition

contentManifestBitrate

Maximum

Highest quality variant from MPD manifest

contentMeasuredBitrate

Estimated

ABR algorithm bandwidth estimate

contentDownloadBitrate

Real-time

Effective download throughput

Streaming Video & Ads for Browser v4.0.0

Tue, 02 Sep 2025 00:00:00 +0000

Feature

Standalone agent

Decoupled from Browser agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

Streaming Video & Ads for Browser v5.0.1

Thu, 06 Aug 2026 00:00:00 +0000

Bug fixes

Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.

Streaming Video & Ads for Browser v3.0.0

Tue, 15 Apr 2025 00:00:00 +0000

New features & enhancements

New event types introduced
- VideoAction: This event type represents standard actions related to video playback and interaction.
- VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
- VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
- VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

PageAction
- The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New attributes introduced

We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation for more details.

Impact & actions required

Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
Update implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
Testing & validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional information

Streaming Video & Ads for Browser v3.1.1

Mon, 09 Jun 2025 00:00:00 +0000

Enhancements

Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

Distribution formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

Streaming Video & Ads for Browser v4.1.0

Sun, 05 Oct 2025 00:00:00 +0000

Feature

Added IMA Ad tracking capability

Improved Ad tracking capability for the agent with IMA ad tracking.

Streaming Video & Ads for Browser v4.0.0

Tue, 02 Sep 2025 00:00:00 +0000

Feature

Standalone agent

Decoupled from Browser agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

Streaming Video & Ads for Browser v4.1.1

Fri, 17 Apr 2026 00:00:00 +0000

What's changed

Documentation

README Overhaul: Restructured and expanded README with comprehensive installation guides, usage examples, best practices, configuration options, API reference, and support channels.

Improvements

Attributes Validation: Updated validation logic for custom attributes to enforce correctness at the tracker level.
Custom Attributes Limit: Added an enforced limit on the number of custom attributes that can be sent per event, preventing unexpected payload sizes.

Installation

npm install @newrelic/video-html5@4.1.1

Full changelog

Streaming Video & Ads for Browser v4.1.2

Mon, 29 Jun 2026 00:00:00 +0000

What's changed

chore: release updated by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/39
Fix/workflow by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/40
chore: add smart release detection and improve workflow triggers by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/41
fix: buffer end fix by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/44
Release/25 may2026 by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/45
chore: add release notes docs PR workflow by @ametku in https://github.com/newrelic/video-html5-js/pull/46
chore: release workflow updated by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/49
fix: address docs reviewer comments on release notes PR format by @mlychndnnr in https://github.com/newrelic/video-html5-js/pull/52
chore: trigger release-notes-docs-pr after release creation by @ametku in https://github.com/newrelic/video-html5-js/pull/56
chore(release): v4.1.2 by @github-actions[bot] in https://github.com/newrelic/video-html5-js/pull/50

New Contributors

@github-actions[bot] made their first contribution in https://github.com/newrelic/video-html5-js/pull/50

Full Changelog: https://github.com/newrelic/video-html5-js/compare/v4.1.1...v4.1.2

Streaming Video & Ads for Browser v5.0.0

Wed, 29 Jul 2026 00:00:00 +0000

What's changed

feat: Add Vega Video Monitoring support by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/58
Release/06 jul2026 by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/59
feat: Update html5 tracker version by @rajeevkumar-nr in https://github.com/newrelic/video-html5-js/pull/61

Full Changelog: https://github.com/newrelic/video-html5-js/compare/v4.1.2...v5.0.0

Streaming Video & Ads for Browser v5.0.1

Thu, 06 Aug 2026 00:00:00 +0000

Bug fixes

Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan (JP) region collector support for Vega/Fire TV tracking.

Streaming Video & Ads for Browser v3.0.0

Sun, 23 Feb 2025 00:00:00 +0000

New features & enhancements

New event types introduced

VideoAction: This event type represents standard actions related to video playback and interaction.
VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

PageAction
- The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New attributes introduced

Impact & actions required

Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
Update Implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
Testing & Validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional information

Streaming Video & Ads for Browser v3.1.0

Mon, 09 Jun 2025 00:00:00 +0000

Enhancements

Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

Distribution formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

Streaming Video & Ads for Browser v3.0.1

Sun, 27 Apr 2025 00:00:00 +0000

This release of the New Relic Shaka Tracker includes a change to error reporting.

Key changes

Error reporting update: The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward.

Upgrade notes

Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.

Streaming Video & Ads for Browser v4.0.1

Mon, 17 Nov 2025 00:00:00 +0000

Enhancements

Improved error logging

Improved error logging by mapping Shaka errors to the following attributes: errorCode, errorPlatformCode, errorMessage, errorStackTrace, errorSeverity.

This enhancement ensures cleaner, more structured error data in New Relic by extracting only the essential error attributes from Shaka Player errors, removing unwanted properties like the data array.

Updates

Fixed CONTENT_ERROR Event

Attached the error EventListener to the player instead of its tag, following Shaka's specifications, to fix the CONTENT_ERROR event.

Streaming Video & Ads for Browser v4.0.0

Tue, 02 Sep 2025 00:00:00 +0000

Feature

Standalone Agent

Decoupled from Browser agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

Streaming Video & Ads for Browser v4.0.2

Wed, 18 Feb 2026 00:00:00 +0000

Bug fixes

Fixed `contentBitrate` to accurately report stream bitrate

Issue: The contentBitrate attribute used estimatedBandwidth (the network capacity estimate) as its primary source, which didn't accurately represent the actual bitrate of the playing video stream.

Solution: Updated the bitrate calculation to prioritize streamBandwidth from Shaka Player statistics, which provides the actual content bitrate of the current video variant as defined in the manifest.

Impact: The contentBitrate attribute correctly reports the bitrate (in bits per second) of playing video stream rather than the estimated network bandwidth. This provides more accurate telemetry data for video quality monitoring and analytics.

Technical details

Changed the priority order in getContentBitratePlayback() method
Uses the stats.streamBandwidth as the primary source for content bitrate
Updated the DATAMODEL.md documentation to reflect the accurate definition

Streaming Video & Ads for Browser v4.0.3

Mon, 09 Mar 2026 00:00:00 +0000

This release introduces three new bitrate metrics for granular playback observability, QoE (Quality of Experience) support, and Shaka Player 5.x compatibility while maintaining backward compatibility with Shaka 4.x.

New bitrate metrics

Three new attributes are now available to provide deeper insight into streaming performance:

Attribute

Source

Description

contentManifestBitrate

stats.streamBandwidth

Total variant bitrate (video + audio) as declared in the manifest (Indicated Bitrate).

contentMeasuredBitrate

stats.estimatedBandwidth

Estimated network bandwidth measured by Shaka's ABR algorithm (Observed Bitrate).

contentDownloadBitrate

(bytesDownloaded × 8) / playTime

Effective download throughput across all downloaded media.

Additionally, contentBitrate uses track.videoBandwidth (video-only bitrate) to differentiate it from other metrics that report combined video and audio bandwidth.

Quality of Experience (QoE) support

QoE aggregate events are now supported via video-core. Enable them by setting qoeAggregate: true in the config:

const options = {
  info: {
    beacon: 'xxxxxxxxxx',
    applicationID: 'xxxxxxx',
    licenseKey: 'xxxxxxxxxxx',
  },
  config: {
    qoeAggregate: true,
    qoeIntervalFactor: 2,
  },
};

const tracker = new ShakaTracker(player, options);

The following KPIs are tracked automatically:

KPI

Description

startupTime

Time from content request to content start (ms).

peakBitrate

Maximum contentBitrate observed during playback.

averageBitrate

Weighted average bitrate across the session.

hadStartupFailure

true if a content error occurred before content started.

hadPlaybackFailure

true if a content error occurred during playback.

totalRebufferingTime

Total time spent rebuffering (ms).

rebufferingRatio

Rebuffering time as a percentage of total playtime.

totalPlaytime

Total content playtime (ms).

numberOfErrors

Total number of errors during the session.

Shaka Player 5.x compatibility

The tracker is now compatible with both Shaka Player 4.x and 5.x:

getPlayerVersion() resolves version across both major versions.
onError() handles both Shaka player errors (e.detail) and HTML video element errors (e.target.error).
Sample files updated for Shaka 5.x (removed deprecated shaka.polyfill.installAll(), updated player instantiation).

Upgrade guide

Run the following following to update:

npm install @newrelic/video-shaka@4.0.3

To enable QoE, add qoeAggregate: true to your config options as shown above.

Dependencies

Requires @newrelic/video-core v4.1.1 or later for QoE support.

Streaming Video & Ads for Browser v5.0.1

Thu, 06 Aug 2026 00:00:00 +0000

Bug fixes

Updated the bundled @newrelic/video-core dependency to v5.0.1, adding Japan(JP) region collector support for Vega/Fire TV tracking.

Streaming Video & Ads for Browser v3.0.0

Tue, 15 Apr 2025 00:00:00 +0000

New features & enhancements

New event types introduced
- VideoAction: This event type represents standard actions related to video playback and interaction.
- VideoErrorAction: This event type captures errors that occur during video playback, providing detailed insight for troubleshooting.
- VideoAdAction: Dedicated event type for tracking actions related to video advertisements, ensuring better granularity and reporting.
- VideoCustomAction: A flexible event type for custom actions and interactions within video applications.

Deprecations

PageAction
- The PageAction event type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.

New attributes introduced

We have introduced a set of new attributes to enhance data tracking and analytics. These attributes provide additional context and details for the new event types, refer to the data model documentation for more details.

Impact & actions required

Transition from PageAction: Users currently tracking PageAction events should adapt their implementations to utilize the newly introduced event types. This change provides improved specificity and scope in tracking actions across video interactions.
Update implementations: Integrators should update their systems to leverage new attributes introduced with the release, which provide richer context and detail for event tracking.
Testing & validation: We recommend testing the implementation of new attributes and event types to ensure compatibility and correct data transmission.

Additional information

Streaming Video & Ads for Browser v3.0.1

Sun, 27 Apr 2025 00:00:00 +0000

Key changes

Error reporting update: The errorName attribute, previously used for identifying error description, has been deprecated. The errorMessage attribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize the errorMessage attribute going forward.

Upgrade notes

Users who rely on the errorName attribute for error analysis should plan to migrate to the errorMessage attribute to ensure continued functionality and access to detailed error information.

Streaming Video & Ads for Browser v3.1.0

Mon, 09 Jun 2025 00:00:00 +0000

Enhancements

Publishing to npm: The package can now be published to npm, making it easily accessible.

Build

Distribution formats: Added cjs, esm, and umd builds to the dist folder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.

Streaming Video & Ads for Browser v4.0.1

Fri, 26 Sep 2025 00:00:00 +0000

Bug fixes

Ad Bitrate for CSAI and DAI

Added methods to calculate Google IMA Ad bitrate for CSAI and DAI

Streaming Video & Ads for Browser v4.0.0

Tue, 02 Sep 2025 00:00:00 +0000

Feature

Standalone agent

Decoupled from Browser agent: The video agent now operates independently with its own harvesting logic. This separation reduces overhead and ensures that video data is collected and sent to New Relic without being tied to the browser agent's data collection schedule.

Streaming Video & Ads for Browser v4.0.2

Tue, 21 Oct 2025 00:00:00 +0000

Bug fixes

Content Bitrate detection enhancement

We've significantly improved the getBitrate() method with comprehensive Video.js technology support:

Key improvements

VHS (Video HTTP Streaming) API support: Added native support for HLS and DASH content bitrate detection
Enhanced bandwidth calculation: Implemented audio + video bitrate combination for accurate total bandwidth reporting
Extended tech support: Added fallback support for popular streaming libraries:
- Shaka Player
- HLS.js
- DASH.js
Improved reliability: Enhanced bitrate detection accuracy across different streaming technologies
Dynamic bitrate updates: Fixed issue where bitrate values remained static throughout video playback

Streaming Video & Ads for Browser v4.0.3

Fri, 21 Nov 2025 00:00:00 +0000

Bug fixes

Removed github token (f5f9ade)

Streaming Video & Ads for Browser v4.1.2

Wed, 13 May 2026 00:00:00 +0000

Highlights

Added MediaTailor SSAI tracker initialization on loadstart after source load detection.
Added DAI stream manager support through the stream-manager event.
Improved bitrate reporting with:
- Playback bitrate (AVERAGE-BANDWIDTH/BANDWIDTH)
- Manifest max bitrate
- Segment download bitrate
- Network throughput bitrate

Improvements

Refined ad and content event handling to avoid duplicate or incorrect content events while ads are active for following events:
- Pause/Resume
- Seek Start/End
- Buffer Start
Improved end-of-content handling for ad-enabled playback paths during IMA and Freewheel scenarios.
Added safer fallback logic for tech wrappers (Hls.js, Shaka, contrib-hls) when bitrate data is unavailable in VHS.

Technical notes

Tracker metadata and playback context methods remain aligned with Video.js/Brightcove integrations:
- Retrieves the title, ID, and duration from mediainfo when available.
- Retrieves source and rendition data from the active tech component when available.
Updated the Listener registration and unregistration to include ad and stream manager lifecycle events.

Streaming Video & Ads for Browser v4.2.0

Fri, 19 Jun 2026 00:00:00 +0000

Highlights

Explicit opt-in for AWS MediaTailor, with full support for custom CDN domains.
New config.ad.type API to choose between CSAI and SSAI (DAI, MT) ad tracking — no more URL-based guessing for SSAI.
End-to-end logging through nrvideo.Log, with active detection mode logged at startup.

Features

MediaTailor custom CDN support

Replaced URL-based auto-detection with explicit opt-in.

Enabled the tracker via mediatailor: true (or mediatailor: { trackingUrl, adSegmentPrefix }), supporting both default AWS hostnames and custom CDN domains.
Added MT_DEFAULT_AD_SEGMENT_PATH (/tm/) constant for AWS-recommended CDN ad-segment path; ad segments rewritten to a custom CDN domain under /tm/ are detected automatically.
Updated isMediaTailorSegment() to check the default AWS segments hostname, the /tm/ path, and an optional customer-supplied adSegmentPrefix.
Threaded adSegmentPrefix through HLS (VHS) and DASH manifest parsing.
Added explicit session initialization via mediatailor: { trackingUrl } for POST /v1/session/ flows.

Ad tracking configuration

Introduced config.ad.type to control ad tracker selection.

Exposed AD_TRACKING constant with CSAI (flat value covering IMA / Brightcove IMA / Freewheel / generic) and SSAI sub-types (DAI, MT).
Required an explicit sub-type for SSAI — each platform needs its own SDK and cannot be auto-detected.
Mapped SSAI.MT to imply mediatailor: true.
Added a fallback to CSAI auto-detection with a warning when config.ad.type is unset (backward compatible for v4.1.2 users).
Co-located segmentPrefix and trackingUrl under config.ad.
Added DaiAdsTracker to static exports.

Logging improvements

Exposed VideojsTracker.Log as a static so UMD callers can set log level.
Added logging of the active ad segment detection mode at tracker startup.
Added logging of the matched ad segment detection path on the first ad break (once per session).
Added logging of which CSAI framework was auto-detected (BrightcoveIma / IMA / Freewheel / generic).
Replaced console.log/warn/error with nrvideo.Log across MediaTailor files.

Bug fixes

Fixed buffer end handling in tracker.
Fixed register-plugin.js silently dropping the options object and not forwarding it to the TrackerJS constructor.

Documentation

Updated the README and SSAI docs for custom CDN support, clarified when trackingUrl and adSegmentPrefix overrides are needed, and cleaned up sessionId references.
Corrected adSegmentPrefix references to config.ad.segmentPrefix in the SSAI troubleshooting docs.

Upgrade from 4.1.x

No breaking changes for CSAI users. If config.ad.type is unset, the tracker still auto-detects CSAI frameworks (with a one-time warning).
MediaTailor users must opt in explicitly. Replace any URL-pattern reliance with one of:
- mediatailor: true (default AWS hostnames + /tm/ path)
- mediatailor: { trackingUrl, adSegmentPrefix } (custom CDN / explicit session init)
- config.ad.type: AD_TRACKING.SSAI.MT
If you previously passed adSegmentPrefix at the top level, move it to config.ad.segmentPrefix.

Streaming Video & Ads for Browser v4.2.1

Tue, 11 Aug 2026 00:00:00 +0000

New features

Added optional automatic rendition/quality-level change tracking: integrates with the videojs-contrib-quality-levels plugin (when present) to report quality transitions along with the previous and new bitrates, with a graceful fallback when the plugin isn't loaded.

Streaming Video & Ads for Browser v5.0.0

Thu, 17 Sep 2026 00:00:00 +0000

Breaking change: This release adds a package.json#exports map. Deep imports into internal paths of this package will no longer resolve — only the root export (@newrelic/video-videojs-js) and the new /browser subpath are valid import targets. Update any direct deep-imports before upgrading.

New features

/browser subpath export: A @newrelic/video-videojs-js/browser entry point is now available that excludes unused Vega/connected-device code, reducing bundle size for browser consumers.
notifyAdSkipped() (MediaTailor): Host apps with a custom skip-ad UI can report a user-initiated skip. Emits the skipped ad-end event when in an ad; no-op otherwise. Mirrors the equivalent API on the iOS/Android trackers.
stopTracking() (MediaTailor): Reversible teardown that stops polling and unregisters listeners without disposing the tracker, so it can be resumed later. Shares the method name used by the iOS/Android trackers.
AD_ERROR events (MediaTailor): Non-terminal failures now surface as AD_ERROR events in NRDB with a semantic errorCode (NO_FILL, ADS_TIMEOUT, TRACKING_FETCH_FAILED, TOKEN_EXPIRED, MISSING_AVAIL_START, MANIFEST_TRACKING_MISMATCH) instead of only appearing in the debug log.
adPrimaryId attribute (MediaTailor): AD_START, AD_END, and AD_QUARTILE now carry adPrimaryId (the VAST creativeId, falling back to availId:adId) so count(DISTINCT adPrimaryId) counts true creatives, not per-avail ad IDs.

Improvements

@newrelic/video-core updated to 5.1.0, which includes a TypeScript conversion, upstream bug fixes, and dependency patches.
Configurable poll cadence (MediaTailor): config.ad.pollIntervalMs overrides the manifest-derived live poll interval (clamped to 100–5000 ms) for battery- or CPU-constrained clients. Behavior is unchanged when the option is omitted.
Tracking URL from HLS manifest (MediaTailor): The tracker now reads the tracking endpoint from an #EXT-X-DATERANGE CLASS="tracking" tag when present, removing the need to pass an explicit trackingUrl on non-AWS CDNs. An explicit option still takes precedence.
Source-change reset (MediaTailor): Swapping player.src() now resets the tracker — cancels in-flight fetches, clears the stale ad schedule, and re-derives the tracking endpoint — instead of continuing to poll the previous session's endpoint.

Bug fixes

MediaTailor: Only the first ad in a multi-ad pod was tracked. The paging loop re-fetched the same avail on every page; the tracker now fetches the full window in a single tokenless request.
MediaTailor: The tracking endpoint could not be derived for implicit-session media-playlist URLs, so Tier-1 ad detection never ran for those sessions.
MediaTailor: config.ad.segmentPrefix was silently ignored because it was mapped to the wrong internal key.
MediaTailor: A DASH period was classified as an ad when only one of several representations resolved to an ad-marked URL. Classification now requires every representation to match.
MediaTailor: AD_END was not fired when a pod ended before its enclosing break boundary, causing completions to be undercounted.
MediaTailor: Pod-count mismatches between manifest and tracking data silently corrupted break geometry; the tracker now reconciles counts explicitly and emits MANIFEST_TRACKING_MISMATCH.
MediaTailor: Avails with a missing startTimeInSeconds were silently dropped, undercounting impressions in NRDB; the tracker now falls back to the first ad's start and emits MISSING_AVAIL_START.
MediaTailor: Live sliding-window re-merges duplicated or dropped ad breaks when start times jittered; breaks now deduplicate by stable identity (availId + availProgramDateTime).
MediaTailor: No-fill avails emitted phantom AD_START/quartile events; they now emit only break boundaries plus AD_ERROR(NO_FILL).
MediaTailor: Expired tracking pagination tokens (HTTP 400) were not handled; the token is now dropped and retried once before emitting TOKEN_EXPIRED and stopping polling.
MediaTailor: Manifest fetches did not re-check isDisposed after each await, risking state mutation on a disposed tracker.
AD_RESUME was fired on first play into an ad, not only after a genuine pause.
Disposing mid-ad did not emit the outstanding AD_END/AD_BREAK_END, leaving the break dangling.
DASH EventStream presentationTime values were treated as raw ticks instead of being converted to seconds, misplacing ads at wrong offsets.
HLS #EXT-X-CUE-OUT-parsed ad breaks did not initialize quartile flags, causing quartile events to fire more than once per ad.

Streaming Video & Ads for Browser v2.0.0

Tue, 22 Sep 2026 00:00:00 +0000

New features

/browser subpath export: A @newrelic/video-hls/browser entry point is now available that excludes unused Vega/connected-device code, reducing bundle size for browser consumers. A browser.js filesystem shim is also included for bundlers that don't honor the exports field.
Named export: { HLSTracker } is now available as a named export alongside the existing default export on both the root and /browser entry points.

Improvements

@newrelic/video-core updated to 5.1.0, which includes TypeScript declaration files, upstream bug fixes, and dependency patches.

Streaming Video & Ads for Browser v5.0.0

Thu, 24 Sep 2026 00:00:00 +0000

New features

/browser subpath export: A @newrelic/video-caf/browser entry point is now available that excludes the unused connected-device pipeline from the bundled @newrelic/video-core dependency, keeping the bundle lean. A browser.js filesystem shim is also included for bundlers that don't honor the exports field.
Named export: { CAFTracker } is now available as a named export alongside the existing default export on both the root and /browser entry points.

Improvements

@newrelic/video-core updated to 5.1.0, which includes TypeScript declaration files, upstream bug fixes, and dependency patches.

Streaming Video & Ads for Browser v2.0.1

Wed, 30 Sep 2026 00:00:00 +0000

Bug fixes

Fixed getSrc() returning the browser's temporary blob: URL instead of the actual manifest URL once HLS playback started. The tracker now reads the URL from the underlying Hls.js instance, so the real manifest URL is reported consistently during playback.