Release Version 2.46

Last updated on Mar 09, 2026
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.45.

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

  • Support for Automatically Restarting Historical Load after OpLog Expiry in MongoDB (Added in Release 2.45.2)

    • Introduced the option to automatically restart the historical load if the Oplog or Change Stream expires in your Pipeline. This option is available during Source configuration and when editing an existing Pipeline. When enabled, Hevo restarts the historical load for all active objects, preventing Pipeline failures and eliminating the need for manual intervention.

  • Support for Company-to-Company Association Object in HubSpot

    • Added support for ingesting data from the Company to Company association object. This object captures relationships between companies in your HubSpot account, such as parent–subsidiary associations. To ingest data for this association object in new and existing Pipelines, contact Hevo Support to enable it.

  • Support for the Latest LinkedIn Marketing API

    • Effective Mar 09, 2026, the LinkedIn Ads integration is upgraded to use Version 202601 to ingest data. This upgrade introduces support for retrieving data from the Posts API, enabling ingestion of posts associated with LinkedIn Ads sponsored accounts.

      As part of this update:

      • The Posts object is now supported.

      • The Video Ads object has been deprecated and replaced by the Posts object.

      The upgrade process will be seamless, with no downtime for your Pipelines. To ingest the historical data for the Posts object in an existing Pipeline, you must restart the historical load for the object.

      Read LinkedIn Ads for more information about the affected objects.

  • Support for Version 2026-01-15 of the Klaviyo v2 API

    • Effective Release 2.46. Hevo has updated the Klaviyo v2 integration to support API version 2026-01-15. This update expands subscription consent handling and update the structure of certain Campaign and Message responses.

      Key updates include:

      • Additional subscription channels and consent types, including mobile push, WhatsApp, and SMS transactional data, are now supported for the Profiles object.

      • The locale field is now extracted for Profiles.

      • The Campaign API schema now includes fields related to sending strategy and tracking options.

      • Message fields for Campaign Messages and Flow Messages are now retrieved from the definition object.

      • The data field returned by the Flow Actions API is now captured.

      • Support for mobile push campaigns has been added.

      This upgrade was applied seamlessly and did not require downtime or configuration changes. This change applies to all new and existing Pipelines.

User Experience

  • Hevo SaaS Offering on Snowflake Marketplace (Added in Release 2.45.1)

    • Introduced the Hevo SaaS offering via Snowflake Marketplace, enabling customers to subscribe with customized pricing, contract terms, or payment schedules. Customers can contact Hevo Support to request a private offer. Existing Snowflake Marketplace Capacity Drawdown (MCD) credits can be used toward the purchase.

Fixes and Improvements

Sources

  • Handling Events Loading Issue in LinkedIn Ads (Fixed in Release 2.45.1)

    • Fixed an issue where Events were not loaded for Ad Analytics object in some Pipelines. This issue was introduced in Release 2.43.3, when Hevo added support for the audience_penetration and average_dwell_time fields. While querying these fields, Hevo did not include dateRange, which is required to derive the date value. The date and campaign_id fields together form the composite primary key for the object. Since the query excluded dateRange, Hevo could not derive the date value, resulting in NULL. As date cannot be NULL, the Events failed validation and were not loaded.

      With this fix, Hevo now includes dateRange when querying for audience_penetration and average_dwell_time. This ensures that the date value is properly derived, the composite primary key is valid, and all Events are loaded as expected. This fix applies to all new and existing Pipelines. To ingest the missing data in existing Pipelines, restart the historical load for the Ad Analytics object.

  • Handling Pipeline Failures for Sharded Clusters in OpLog Mode in MongoDB (Fixed in Release 2.45.1)

    • Fixed an issue where Pipelines could be created with sharded MongoDB clusters using OpLog mode, even though this configuration is not supported. This issue occurred because each shard in a sharded cluster maintains its own OpLog, making it difficult for Hevo to read and manage them. As a result, such Pipelines failed during ingestion.

      With this fix, Hevo no longer allows you to create Pipelines that use sharded clusters with OpLog mode. To create a Pipeline with a sharded cluster, use Change Stream mode instead.

Documentation Updates

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

Getting Started

Sources

Was this page helpful?

Tell us what went wrong