Release Version 2.40.2

Last updated on Sep 22, 2025

This is a minor release and will be integrated into the next major release. At that time, this release note will be merged into the next main release note.

The content on this site may have changed or moved since you last viewed it. As a result, some of your bookmarks may become obsolete. Therefore, we recommend accessing the latest content via the Hevo Docs website.

In this Release


New and Changed Features

Sources

  • Support for Engaged Views Metric in YouTube Analytics Source

    • Effective Release 2.40.2, YouTube Analytics has updated the report IDs for certain channel reports. As part of this update, Hevo now replicates the engaged_views metric for all YouTube Analytics Pipelines except for the following objects:

      • channel_video_viewer_demographic

      • channel_video_content_sharing_by_platform

      • channel_video_annotation

      • channel_video_card

      • channel_video_end_screen

      Read Schema and Primary Keys to learn more about the supported metrics.

      The engaged_views field provides the number of times a channel’s videos were watched beyond the initial few seconds. This is applicable to all new and existing Pipelines. For existing Pipelines, you may observe a delay as Hevo triggers new jobs to fetch updated reports. For more information, read Data Replication.

Fixes and Improvements

Sources

  • Handling Data Mismatch Issue in Microsoft Ads

    • Fixed an issue with the User Location Performance Report where there was a mismatch between the Source and Destination data. This happened because the __hevo_id field, which is a combination of multiple fields and serves as the primary key for the report, did not include the query_intent_location_id field. As a result, multiple records shared the same __hevo_id value, causing one record to overwrite another while loading data into the Destination.

      With this fix, Hevo now includes the query_intent_location_id field when generating the __hevo_id field. This ensures that each record has a unique primary key, preventing overwrites and ensuring that accurate data is loaded into the Destination. The fix applies to all new and existing Pipelines.

Tell us what went wrong