Release Version 2.27.3

In this release, we have addressed the following issues to improve the usage and functionality of our product features. To know the list of features and integrations we are working on next, read our Upcoming Features 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.

In this Release

• Early Access Features
• New and Changed Features
• Fixes and Improvements

---

Early Access Features

Destinations

• Support for Key Pair Authentication in Snowflake

  • Hevo now supports connecting to your Snowflake data warehouse Destination using a key pair for authentication, thus making the connection more secure. This method allows you to provide a private key instead of a database password while configuring your Snowflake Destination. You can contact your Hevo account executive or the Support team to enable the Key Pair Authentication feature for your team.

    Request Early Access

    Refer to the Early Access page for the complete list of features available for early access.

---

New and Changed Features

Sources

• Support for Exports API in Amazon Ads Source

  • Effective Release 2.27.3, Hevo uses the Exports API for data ingestion related to core objects of Sponsored Products. Amazon Ads will deprecate the Snapshots API, which Hevo previously used, on October 15, 2024. To ensure continued support for existing functionalities, Hevo will automatically migrate your existing Amazon Ads Pipelines to the new API.

    The API update impacts data ingestion for the following objects:

    Objects	Changes
    Ad Groups	- Source object schema is changed and substituted by new object, Ad_Groups_V2.
    Campaigns	- Source object schema is changed and substituted by new object, Campaigns_V2.
    Campaigns Negative Keywords	- Source object is deprecated, and the data has been moved to the Product_Targeting_V2 object. You can filter this data type within the object using the targetType field.
    Keywords	- Source object is deprecated, and the data has been moved to the Product_Targeting_V2 object. You can filter this data type within the object using the targetType field.
    Negative Keywords	- Source object is deprecated, and the data has been moved to the Product_Targeting_V2 object. You can filter this data type within the object using the targetType field.
    Negative Product Targeting	- Source object is deprecated, and the data has been moved to the Product_Targeting_V2 object. You can filter this data type within the object using the targetType field. - Child objects negative_product_targeting_expression and negative_product_targeting_resolved_expression are removed.
    Product Ads	- Source object schema is changed and substituted by new object, Product_Ads_V2.
    Product Targeting	- Source object schema is changed and substituted by new object, Product_Targeting_V2. - Product_Targeting_V2 contains data for Negative Product Targeting, Negative Keywords, Keywords, and Campaigns Negative Keywords data types. You can filter the data within the object for these data types using the targetType field. - Child objects product_targeting_expression and product_targeting_resolved_expression are removed.

    In your existing Pipelines, the older objects you had selected for ingestion will be marked as completed, and the corresponding new objects will be added.

    This change applies to all new and existing Pipelines created with Amazon Ads as the Source.

Fixes and Improvements

Sources

• Handling Data Mismatch Issues in Facebook Ads

  • Fixed an issue in Facebook Ads whereby the API call to fetch the attribution values returned incorrect data in the Destination when multiple action types were present in the attribution list. This issue occurred due to incorrect parsing of attribution values, where all action types used the same key, leading to overwritten values and only the last action type being returned. With this fix, each action type now has unique values based on the selected attribution settings, ensuring correct data in the Destination.

    This fix applies to all new Pipelines created after Release 2.27.3. Contact Hevo Support to enable the fix for your existing Pipelines.