Release Version 2.43.2

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
• Fixes and Improvements

New and Changed Features

Sources

• Support for Full Load Ingestion for Facebook Ads Objects

  • Added support to ingest Ads, Ad Sets, and Ad Campaigns using Full Load mode instead of relying only on the updated_time field to fetch incremental changes for these objects. However, Facebook Ads does not reliably update this field, leading to stale or missing data and frequent data mismatch issues.

    With this enhancement, you can now enable Full Load ingestion for these objects, ensuring that Hevo replicates the complete dataset during each ingestion. This may result in an increased Event quota consumption. Read Facebook Ads for more information.

Fixes and Improvements

Sources

• Handling Refresher Task Failure Issues in Snapchat Ads

  • Fixed an issue where refresher tasks for Snapchat Ads failed on Daylight Saving Time (DST) transition days. This issue occurred because Hevo calculated the data window for each refresher run by adding a fixed 24-hour interval. On DST transition days, such as the fall-back day, the clock is set back by an hour, and the day becomes longer than 24 hours. In such cases, using a fixed 24-hour interval may result in an incorrect end timestamp, causing the refresher task to fail.

    With this fix, Hevo now calculates the data window based on the user’s time zone rather than a fixed time interval, ensuring that the date range is always computed correctly on DST transition days. To enable this fix for your new and existing Pipelines, contact Hevo Support.

User Experience

• Handling Issue with Disabling Custom Full Load Frequency

  • Fixed an issue where the Change Full Load Object Ingestion Schedule option remained enabled even after users attempted to disable it. This affected Pipelines created using the following Sources:

    • Amazon Ads
    • Facebook Ads
    • Jira Cloud
    • NetSuite SuiteAnalytics
    • Snapchat Ads
    • Zendesk

    With this fix, disabling the option now works correctly, ensuring all objects in the Pipeline follow the Pipeline ingestion schedule. This fix applies to all new and existing Pipelines.