Release Version 2.40

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

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

---

New and Changed Features

Sources

• Support for v21 of the Google Ads API (Added in Release 2.39.1)

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

• Upgrade to v23.0 of the Facebook Marketing API (Added in Release 2.39.3)

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

Fixes and Improvements

Sources

• Handling Data Ingestion Issue in File Storage Sources

  • Fixed an issue where, in some cases, ingestion from File Storage Sources was getting stuck. This issue occurred because Hevo incorrectly identified the character encoding of the files to be ingested and set it to an unsupported value, such as IBM424_ltr.

    With this fix, Hevo now defaults to the supported UTF-8 encoding when an unsupported character encoding is detected. This ensures that ingestion proceeds without interruptions. This applies to all new and existing Pipelines.

• Handling Incomplete Historical Loads in QuickBooks Online Source

  • Fixed an issue where historical loads from QuickBooks Online stopped before all records were ingested, leading to fewer records in the Destination than in the Source. This issue occurred because the query used to count the number of records to be ingested did not include the same conditions as the query used to fetch records. As a result, Hevo calculated a smaller record count than what actually existed in the Source, and stopped fetching data once that count was reached.

    With this fix, both queries now match correctly, ensuring that Hevo fetches the historical data accurately. This fix applies to all new and existing Pipelines. If you observe a data mismatch in your Destination tables, restart the historical load for the object.

• Handling NULL Values in the Destination for Nested Fields in MongoDB Source (Fixed in Release 2.39.2)

  • Fixed an issue where nested JSON fields of type ObjectID, BsonRegularExpression, and Symbol were incorrectly replicated as NULL in the Destination instead of their actual Source values. This issue occurred because Hevo did not previously support these data types in nested fields.

    With this fix, Hevo now correctly replicates these data types in nested fields, ensuring that the actual Source values are retained in the Destination. This fix applies to all new and existing Pipelines.

Documentation Updates

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

Data Ingestion

• Query Modes

• Selecting your Hevo Region

Destinations

• Event Exceeds Size Limits Supported by the Destination (New)

Events Usage

• Invalid Timestamp Value in Source Fields (New)

Getting Started

• Reauthorizing an OAuth Account

Pipelines

• Database Objects and Actions

• Schema Mapper

  • Limits on the Number of Destination Columns

• Why is there a delay in my Pipeline?

Sources

• Amazon Aurora MySQL

• Amazon Aurora PostgreSQL

• Amazon RDS MySQL

• Amazon RDS PostgreSQL

• Azure PostgreSQL

• Facebook Ads

• Facebook Page Insights

• Generic MongoDB

• Generic MySQL

• Generic PostgreSQL

• Google Ads

• Google Cloud PostgreSQL

• Google Cloud Storage

• Google Drive

• Google Sheets

• HubSpot

• Instagram Business

• MariaDB MySQL

• MongoDB Atlas

• Salesforce Bulk API V2

  • Ingestion Failed due to Missing Resource or Invalid Session

• Troubleshooting PostgreSQL

  • Pipeline failure due to replica queries being canceled (Deleted)

Transform

• SQL Models

  • Model Failure due to Table Unavailability

  • Working with SQL Models