Release Version 2.51
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.50.
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
Getting Started
Support for Creating AWS VPC Peering Connections from the Hevo Dashboard
NewYou can now create AWS VPC peering connection requests and monitor their status directly from the Hevo dashboard, eliminating the need to contact Hevo Support. This simplifies and speeds up the process of establishing secure, private connectivity between Hevo and your AWS-hosted Source or Destination database.
Connecting Through AWS VPC Peering →Support for Edge Specific Regions
NewHevo now supports adding new Hevo regions on request, so you can create Edge Pipelines closer to your infrastructure or to meet data residency and compliance requirements. If Hevo isn’t currently available in an AWS region you need, contact Hevo Support to request it. Regions enabled this way support Edge Pipelines and Destinations only. Standard Pipelines are not supported in these regions, and the Standard tab is disabled for that region in the Hevo UI. Once enabled, the new region appears in your account’s region selector.
Selecting your Hevo Region →Sources
Support for Facebook Ads as a Source (Edge)
NewHevo now supports Facebook Ads as a Source for creating Pipelines. Facebook Ads is Meta’s advertising platform that lets you create, manage, and measure ad campaigns across Facebook, Instagram, Messenger, and the Audience Network. You can replicate data from your Facebook Ads account, including Ads Insights reports and custom reports, into your Destination.
Facebook Ads →Support for Fathom as a Source (Edge)
NewHevo now supports Fathom as a Source for creating Pipelines. Fathom is an AI-powered meeting assistant that automatically records, transcribes, and summarizes video meetings on platforms such as Zoom and Google Meet. You can replicate data from your Fathom account to your Destination using Fathom’s REST API.
Fathom →Support for Google Ads as a Source (Edge)
NewHevo now supports Google Ads as a Source for creating Pipelines. Google Ads is Google’s advertising platform that helps you create and manage ad campaigns across Google Search, YouTube, and other Google properties. You can replicate data from your Google Ads account, including account and campaign details, ad group and ad performance metrics, audience and keyword data, and custom reports, into your Destination.
Google Ads →Support for Google Analytics 4 as a Source (Edge)
NewHevo now supports Google Analytics 4 as a Source for creating Pipelines. Google Analytics 4 is Google’s web and app analytics platform that helps you track and understand customer behavior across your websites and applications. You can replicate data from your Google Analytics 4 property, including account and property metadata, custom dimensions and metrics, and prebuilt and custom reports, into your Destination.
Google Analytics 4 →Support for PostgreSQL Database Version 18 (Edge)
NewIntroduced support for creating Pipelines with PostgreSQL database version 18. This applies to Pipelines created with any variant of the PostgreSQL Source.
Support for Private App Authentication in HubSpot (Edge)
NewHevo now supports connecting to your HubSpot account using the access token and client secret of a private app registered in your account, eliminating the need to authorize through the OAuth flow. Since you own the app, its scopes and access token can be granted, modified, or revoked at any time, giving you greater control over the permissions granted to Hevo.
HubSpot →Transformations
Removed Support for Transformations
NewHevo no longer supports Transformations, including Python and drag-and-drop Transformations. Creating and editing Transformations is disabled for all accounts.
As part of this update:
-
Existing Transformations will continue to run as part of your Pipeline, but cannot be edited.
-
New Transformations cannot be created. The option to create a Transformation has been disabled.
Recommended alternatives:
-
dbt Models: For code-based transformation.
-
SQL Models: For SQL-based transformations on your Destination data.
To update your script or migrate your transformations to dbt or SQL Models, contact Hevo Support.
Transformations (Edge)
Support for dbt-Based Data Transformation in Destinations
NewHevo now supports running dbt models on raw data loaded into your Destination, allowing you to build clean, analytics-ready tables for reporting and analysis. With this feature, you can connect a GitHub repository containing your dbt project, set up staging and production environments, and create jobs to execute your dbt models on your Destination data. Jobs can be triggered on a schedule, on demand, or automatically when a selected Pipeline finishes syncing.
Transformations →User Experience
Updated Destination List View UI
EnhancedThe Destination List View has been redesigned into a tabular format, giving you a clearer view of all your Destinations, including their type, connected Pipelines, connected Activations, and status, all on a single page. This increases navigability and makes it easier to find and manage your Destinations.

Fixes and Improvements
Sources
Handling Historical Load Failure in Marketo
Fixed an issue where Hevo could not ingest the complete historical data for the Activities object, resulting in missing records in the Destination. This issue occurred because Marketo imposes a daily limit on the amount of data its API can export. Hevo requested data for one month at a time, which exceeded this limit and caused ingestion to stop.
With this fix, Hevo now requests historical data in smaller, configurable time windows (a few hours at a time) instead of a full month, keeping API requests within Marketo’s daily limit. The ingestion progress is tracked after each request. When the limit is reached, ingestion pauses and automatically resumes the next day from where it stopped. This process continues until all historical data is successfully ingested, ensuring that no data is missed.
Note: If your Activities object contains a large volume of data, or you are experiencing issues with the historical load, contact Hevo Support to enable the fix for your Pipeline.