Fixed an issue where Hevo failed to connect to the SurveyMonkey account when the account’s First Name and or Last Name fields were empty. Previously, Hevo was unable to process the NULL values returned for these fields, preventing the creation of Pipelines.
After the fix, Hevo handles NULL field values correctly, ensuring a seamless connection when configuring a new Pipeline.
Enhanced the retry mechanism for handling Model resets. Previously, if a Model encountered issues during reset, it could get stuck in the RESETTING state, requiring manual intervention.
After the improvement, Hevo now automatically retries resetting such Models up to two times when an interruption occurs, improving reliability and reducing manual effort.
Fixed an issue where data ingestion for the sent event object was failing due to an API timeout. This issue occurred because Hevo was attempting to retrieve a large volume of records in a single API call. Earlier, if the object contained too much data, the ingestion process would fail entirely, resulting in no records being ingested.
After the fix, Hevo now fetches data for the object in smaller batches through multiple API calls, preventing API timeout and ensuring consistent ingestion. To enable the fix for your new and existing Pipelines, contact Hevo Support.
Fixed an issue where the API call to fetch data for the Campaign report in Google Ads was failing. The issue occurred because the API request included the metrics.primary_impressions metric, which requires the adjusted_age_range and adjusted_gender segments to return data. As these segments were not part of the request, the API call failed, preventing data ingestion.
After the fix, Hevo removes the metrics.primary_impressions metric from the API request for the Campaign report, ensuring uninterrupted data ingestion. This metric can still be retrieved through custom reports that include the required segments. The fix applies to all new and existing Pipelines.
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.
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.
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 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.
After the fix, Hevo 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.
Fixed the following issues to ensure data accuracy and completeness for Stripe Sources.
Data Mismatch Issue: Fixed an issue where the paymentintent_ field in the Dispute object displayed NULL values instead of actual Source values. This issue occurred because Hevo incorrectly reset the fetched values for this field to NULL. After the fix, Hevo now correctly retains and populates the paymentintent_ field in the Destination, ensuring that Source values are reflected accurately.
This fix applies to all new and existing Pipelines. For existing Pipelines, if you observe a mismatch 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. After the 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.
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. As a result, some records from the previous day were skipped and captured later through a refresher task, causing delays in data availability.
After the fix, the offset now advances only after all data for the current day is fetched, ensuring no records are missed between incremental polls.
Effective August 14, 2025, Hevo has upgraded its Google Ads integration to support API v21. As part of this upgrade:
Some reports and fields are no longer supported and will not be ingested. As a result, corresponding Destination tables and columns are not updated.
New fields have been added to certain reports, ensuring that all the newly introduced resources, including attributes, metrics, and segments, are available in your reports.
Read Google Ads for more information on the affected reports and fields.
The upgrade process was seamless, with no downtime for your Pipelines. This change applies to all new and existing Pipelines.
Effective Release 2.39.3, the Facebook Ads, Facebook Pages, and Instagram Business integrations use v23.0 of the Marketing API to fetch your data. As part of this upgrade, the data type of certain fields in Facebook Ads objects has been updated. Read Facebook Ads for more information.
The upgrade process was seamless, with no downtime for your Pipelines. This change applies to all new and existing Pipelines created with Facebook Ads, Facebook Pages, or Instagram Business as the Source.
