Release Version 2.34

Last updated on Mar 19, 2025
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.33.

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 Capturing Deletes in TikTok Ads (Added in Release 2.33.2)

    • Added support for capturing deleted records for the following TikTok report types: Ad, Ad Group, and Campaign. Previously, deleted records were not included in reporting objects because the TikTok Ad’s API automatically excluded deleted entities unless explicitly requested. With this enhancement, Hevo now ensures that even deleted records are included, allowing you to maintain complete data.

      This change applies to all new and existing Pipelines created with TikTok Ads. If you want historical data for deleted records in existing Pipelines, please contact Hevo Support.

  • Support for Discount Applications Object in Shopify (Added in Release 2.33.3)

    • Added support for replicating data from the discount_applications object as a child of the Order object in Shopify. This object is an ordered list that captures all discounts applied to an order, reflecting the sequence in which they were added.

      To enable this for any new or existing Pipelines, reach out to Hevo Support. For existing Pipelines, restart the historical load for the Order object to retrieve historical data for the discount_applications object.

  • Support for Simple and Kanban Board Types for Jira Cloud Source (Added in Release 2.33.3)

    • Hevo now supports data ingestion from Simple and Kanban board types for the Sprint object. This enhancement allows for more comprehensive data replication from a wider range of Jira boards.

      Board Type Description
      Kanban Organizes tasks into different stages to facilitate continuous tracking and workflow management.
      Simple Manages tasks without predefined stages, offering flexibility in task handling.

      To enable data ingestion for the above board types in your new and existing Pipelines, contact Hevo Support. As Sprint is a Full Load object, enabling data ingestion for these board types will lead to higher Events quota consumption.

  • Upgrade to Portfolios API v3 of the Amazon Ads API (Added in Release 2.33.2)

    • Effective February 28, 2025, the Amazon Ads integration is upgraded to use Portfolios API v3 to ingest data for the Portfolios object. Read Amazon Ads for more information on the affected fields. To avoid any data loss, we recommend making the necessary adjustments to accommodate these changes. The upgrade process will be seamless, with no downtime for your Pipelines.

  • Upgrade to Version 2024-10 of the Shopify API (Added in Release 2.33.1)

    • Effective February 24, 2025, the Shopify App integration is upgraded to use version 2024-10 of the Shopify API to fetch your data. The new API version impacts the ingestion of some objects. Read Shopify App.

      To avoid any data loss, we recommend making the necessary adjustments to accommodate these changes. The upgrade process will be seamless, with no downtime for your Pipelines. However, if you need the historical data for product_v2, product_variants_v2, or any of the new fields, you can restart the historical load for the respective object.

      This change applies to all new and existing Pipelines created with this Source.

Fixes and Improvements

Sources

  • Handling Authentication and Data Mismatch Issues in Stripe

    • Fixed an issue where Hevo was unable to retrieve the refundIds field from the Charge object due to a missing API key in the API call. The API key is required to authenticate the request for retrieving data from this field. Without the API key, the authentication failed, preventing historical data ingestion for the object.

      With this fix, Hevo now includes the API key in the API call, ensuring successful authentication and historical data ingestion for the Charge object. This fix applies to all new and existing Pipelines.

    • Fixed an issue in Stripe where records were being incorrectly updated due to an out-of-order event processing. Hevo previously relied solely on the Stripe Events API to fetch records, which does not guarantee event order. As a result, when multiple events had the same timestamp, records would be incorrectly overridden, leading to data mismatches. With this fix, Hevo now makes an additional API call to fetch the latest state of each record before updating the Destination table.

      If a data mismatch is observed for any object in an existing Pipeline, restart the historical load for that object.

  • Handling Data Mismatch Issue in Salesforce Marketing Cloud (Fixed in Release 2.33.3)

    • Fixed an issue where Hevo was unable to fetch data for the itemID field in the campaign_asset object due to a case mismatch. This issue occurred because the API attempted to access the itemId field instead of the correctly named itemID. As a result, Hevo loaded zero as the default value for this field into the Destination.

      With this fix, Hevo can now retrieve the data for the itemID field, ensuring accurate data is loaded into the Destination.

  • Handling Historical Data Ingestion in Amazon DocumentDB

    • Fixed an issue where historical data was not getting ingested when a large volume of data was present in the Source. Amazon DocumentDB requires the minimum value for each field’s data type in the Source objects to return data to Hevo. Previously, this required running a query to search through each record, which could be time-consuming and lead to query timeouts.

      With this fix, Hevo now provides predefined minimum values for all data types to Amazon DocumentDB while fetching data. This approach reduces the time needed to search through records and helps prevent query timeouts, ensuring that historical data is successfully ingested. To enable this fix for your new and existing Pipelines, contact Hevo Support.

  • Handling Incorrect Ingestion Mode Option for Redshift (Fixed in Release 2.33.2)

    • Fixed an issue where BinLog was incorrectly displayed as an available ingestion mode while configuring Redshift as a Source. With this fix, Hevo now correctly shows only Table and Custom SQL ingestion modes for Redshift.

  • Handling Incorrect Ingestion Mode Selection in SQL Server Source (Fixed in Release 2.33.2)

    • Fixed an issue in all variants of SQL Server Source that affected teams created after Release 2.19. In these cases, the Pipeline was incorrectly created in Table mode, even when Change Tracking was selected as the ingestion mode during SQL Server Source configuration. This issue occurred because the system did not capture the selected ingestion mode, resulting in the Pipeline to be created in Table mode by default.

      With this fix, the system now correctly captures the ingestion mode selection.

  • Handling Offset Not Updating Issue in Klaviyo (Fixed in Release 2.33.2)

    • Fixed an issue in Klaviyo where the timestamp-based offset for objects stopped updating after Hevo started the initial historical data load. Even during incremental loads, when Hevo began ingesting data, the offset remained unchanged. The following objects were affected:

      • Events
      • FlowActionService
      • FlowMessage
      • Flow
      • List
      • Profile
      • Segment

      With this fix, Hevo now updates the timestamp-based offset in real time as new Events are ingested. This fix applies to both new and existing Pipelines.

User Experience

  • Handling Incorrect Navigation in Jobs List (Fixed in Release 2.33.2)

    • Fixed a UI issue where clicking the arrow ( Arrow icon ) icon next to the Status column in the Jobs list incorrectly redirected users to the Pipeline Overview page. With this fix, Hevo now correctly displays the additional job details when the arrow icon is clicked.

  • Missing Redirect URL Issue for REST API Source (Fixed in Release 2.33.2)

    • Fixed an issue in the Hevo user interface (UI) that caused the Redirect URL field value to be reset to an empty string. As a result, users were unable to set up the OAuth 2.0 authentication method while configuring REST API as a Source. After the fix, the redirect URL is displayed correctly.

Documentation Updates

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

Destinations

Pipelines

Sources

Was this page helpful?

Tell us what went wrong