Enhancements
- Publishing to npm: The package can now be published to npm, making it easily accessible.
Build
- Distribution formats: Added
cjs,esm, andumdbuilds to thedistfolder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.
Enhancements
- Publishing to npm: The package can now be published to npm, making it easily accessible.
Build
- Distribution formats: Added
cjs,esm, andumdbuilds to the dist folder, ensuring compatibility withCommonJS,ES Modules, andUMDmodule formats.
Enhancements
- Publishing to npm: The package can now be published to npm, making it easily accessible.
Build
- Distribution formats: Added
cjs,esm, andumdbuilds to thedistfolder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.
Enhancements
- Publishing to npm: The package can now be published to npm, making it easily accessible.
Build
- Distribution formats: Added
cjs,esm, andumdbuilds to thedistfolder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.
Enhancements
- Publishing to npm: The package can now be published to npm, making it easily accessible.
Build
- Distribution formats: Added
cjs,esm, andumdbuilds to thedistfolder, ensuring compatibility with CommonJS, ES Modules, and UMD module formats.
This minor release of the New Relic Bitmovin Tracker includes important change to error reporting.
Key changes
- Error reporting update: The
errorNameattribute, previously used for identifying error description, has been deprecated. TheerrorMessageattribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize theerrorMessageattribute 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.
This release of the New Relic Shaka Tracker includes a change to error reporting.
Key changes
- Error reporting update: The
errorNameattribute, previously used for identifying error description, has been deprecated. TheerrorMessageattribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize theerrorMessageattribute going forward.
Upgrade notes
- Users who rely on the
errorNameattribute for error analysis should plan to migrate to theerrorMessageattribute to ensure continued functionality and access to detailed error information.
Key changes
- Error reporting update: The
errorNameattribute, previously used for identifying error description, has been deprecated. TheerrorMessageattribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize theerrorMessageattribute going forward.
Upgrade notes
- Users who rely on the
errorNameattribute for error analysis should plan to migrate to theerrorMessageattribute to ensure continued functionality and access to detailed error information.
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
errorNameattribute, previously used for identifying error description, has been deprecated. TheerrorMessageattribute is now the standard for conveying detailed error descriptions. Please update any monitoring or logging systems that rely on error information to utilize theerrorMessageattribute 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.
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
PageActionevent type has been deprecated. Users should transition to using the newer event types that offer enhanced tracking capabilities and specificity.
- The
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
PageActionevents 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.