Release Version 2.41

Last updated on Oct 06, 2025
On This Page

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.

This release note also includes the fixes provided in all the minor releases since 2.40.

To know the complete list of features available for early adoption before these are made generally available to all customers, read our Early Access page.

In this Release

New and Changed Features

Sources

  • General Availability for Capturing Deletes in Stripe

    • Added support for the replication of deleted records for supported Stripe objects in all new and existing Pipelines. Previously, this feature was enabled only on request through Hevo Support.

      With this enhancement, Hevo now replicates deleted records in the Destination by setting the is_row_deleted column to True and the deleted_timestamp column to the timestamp when the record was deleted in Stripe.

      Read Data Replication and Source Considerations for more information.

  • Support for Engaged Views Metric in YouTube Analytics Source (Added in Release 2.40.2)

    • 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 in Release 2.40.2)

    • 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.

  • Handling Data Mismatch Issues in Stripe

    • Fixed the following issues to ensure data accuracy and completeness for Stripe Sources.

      • Data Mismatch Issue: Fixed an issue where the payment_intent field in the Dispute object displayed NULL values in the Destination instead of actual values from the Source. This issue occurred because Hevo incorrectly reset the fetched values for this field to NULL before populating them in the Destination, resulting in a data mismatch.
        With this fix, Hevo now correctly retains and populates the payment_intent field in the Destination, ensuring that Source values are reflected accurately. This fix applies to all new and existing Pipelines. For existing Pipelines, while all future loads are fixed, any rows previously displayed as NULL will remain unchanged. If you observe such mismatches in your Destination tables, restart the historical load for the Dispute object to backfill the correct values.

      • Missing Data Issue: Fixed an issue where some updates to the Events object were not captured during incremental ingestion. This issue occurred because Stripe can take up to an hour to make certain event updates available through its API. As Hevo advanced the offset in real time, a few delayed events were skipped.

        With this fix, Hevo now introduces a 1-hour buffer before advancing the event offset to ensure that no updates are missed. As a result, data from Stripe may appear in your Destination with a delay of up to 1 hour. No user action is required.

  • Handling Delay in Data Availability for Custom Reports in Facebook Ads (Fixed in Release 2.40.3)

    • Fixed an issue where Hevo skipped some records during incremental ingestion for custom reports. Earlier, if a Pipeline polled for data after midnight, the date offset was moved to the next day before collecting all records for the previous day. For example, if a Pipeline had a 30-minute ingestion frequency and an offset set to Sep 17, 2025, at 11:45 PM, the next poll on Sep 18 at 12:15 AM would advance the offset to Sep 18. As a result, records from 11:45 PM to midnight on Sep 17 were skipped and captured later through a refresher task, causing delays in data availability.

      With this fix, the offset now advances only after all data for the current day is fetched, ensuring no records are missed between incremental polls.

Documentation Updates

The following pages have been created, enhanced, or removed in Release 2.41:

Data Ingestion

Destinations

Getting Started

Introduction

Pipelines

Transform

Sources

Was this page helpful?

Tell us what went wrong