Release Version 2.34.1

In this release, we have addressed the following issues to improve the usage and functionality of our product features. 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

• Fixes and Improvements

Fixes and Improvements

Pipelines

• Improved Data Ingestion for Amazon S3

  • Hevo has enhanced the data ingestion process for Pipelines created with Amazon S3 as a Source. Previously, when the Create Event Types from folders option was enabled in these Pipelines, Hevo could ingest subfolders as separate Event Types only if the parent folder contained a maximum of 500 subfolders and files. If this limit was exceeded, all subfolders were merged into their parent folder and ingested as a single Event Type. This prevented parallel ingestion of data and increased ingestion time.

    With this enhancement, Hevo now ingests each subfolder as a separate Event Type, regardless of the total number of items within the parent folder, when the Create Event Types from folders option is enabled. This allows data to be ingested in parallel, reducing ingestion time.

    To enable this enhancement for your new and existing Pipelines, contact Hevo Support.

Sources

• Error Handling for Messages Object in Twilio

  • Fixed an issue in the Twilio integration where data ingestion for the Messages object would stop upon encountering error code 20004: Method not allowed. This error occurs when the API response contains an invalid page token. Without a valid page token, Hevo cannot fetch data from the next page during the API call.

    To address this issue, Hevo now restarts fetching data from the first page whenever this error occurs. This ensures that a valid page token is generated, allowing seamless data ingestion. However, this may increase the data ingestion time.

    This fix applies to all new and existing Pipelines.

• Handling Data Ingestion Issues in Amazon S3

  • Fixed an issue where, in some cases, Hevo incorrectly marked objects as FAILED. If there was an interruption while sending ingested files from Amazon S3 to Hevo’s internal processing system, the corresponding objects were marked as FAILED. As a result, these objects were excluded in subsequent ingestion runs.

    With this fix, Hevo now correctly handles such interruptions by automatically retrying ingesting the failed objects, ensuring successful data ingestion. This fix applies to all new and existing Pipelines.

    Note: If you observe this issue in your existing Pipelines, you must restart the historical load for the FAILED objects to ensure all data is ingested.

• Handling Data Mismatch Issue in Pinterest Ads

  • Fixed an issue where the AD_ACCOUNT_REPORT_MONTH object ingested incremental data on a daily instead of monthly. This issue occurred because the system did not reset the start date for ingestion to the first day of the current month at the end of each poll. As a result, the next poll fetched data from the date when the previous poll happened, leading to daily data ingestion.

    With this fix, the system now correctly resets the start date for ingestion, ensuring that incremental data is ingested on a monthly basis.

    This fix applies to new Pipelines created after Release 2.34.1. To enable the fix for your existing Pipelines, contact Hevo Support.

    Note: For existing Pipelines, if you observe a data mismatch in your Destination, you must enable the fix and then restart the historical load for the AD_ACCOUNT_REPORT_MONTH object to ensure all data is ingested accurately.

• Handling Ingestion Lag Issues in Google Ads, TikTok Ads, and Facebook Ads

  • Fixed an issue where data ingestion for Google Ads, TikTok Ads, and Facebook Ads was delayed due to time zone differences. The issue occurred because, by default, Hevo only uses Coordinated Universal Time (UTC) time to schedule data ingestion, regardless of the time zone of the Source account. As a result, data ingestion was initiated later than expected. For example, if a TikTok Ads account was set to Eastern Standard Time (EST), Hevo still processed data based on UTC. As midnight UTC corresponds to 7:00 PM EST, data ingestion for the previous day’s records would start several hours later, leading to delays.

    With this fix, Hevo now allows you to set a preferred time zone for Google Ads, TikTok Ads, and Facebook Ads to ensure ingestion aligns with the Source account’s time zone. To enable this for new and existing Pipelines, contact Hevo Support.

• Handling Missing Data Issue in Google Ads

  • Fixed an issue where Hevo was unable to ingest data from some Google Ads campaign types. This issue occurred because Hevo includes ad_group and ad_group_id fields in its queries for all campaign types. However, these fields are not supported for newer campaign types, which caused the Google Ads API to return an empty dataset instead of valid results. As a result, historical and incremental data ingestion was incorrectly marked as complete, even though no data was pulled. With this fix, Hevo first runs the query that includes the ad_group fields. If no data is returned, Hevo automatically retries with an updated query that excludes these fields. This ensures that data is correctly ingested for all campaign types. This fix is available for all new and existing Pipelines.

    Note: For existing Pipelines, if you observe missing data for any objects in your Destination, you must restart the historical load for them.

• Handling Missing media_id Field in Shopify

  • Fixed an issue where Hevo did not fetch the media_id field in the Product Variants V2 object after upgrading to Shopify API version 2024-10. This API version introduced the media_id field, which links product variants to their media details through the Product Media List object. Since Hevo did not fetch this field, users could not retrieve media details for product variants, leading to incomplete information.

    With this fix, Hevo now successfully retrieves the media_id field in the Product Variants V2 object. This fix applies to all new and existing Pipelines.

    Note: For existing Pipelines, if you need to retrieve the historical data for the media_id field, restart the historical load for the Product Variants V2 object. This may lead to higher Events quota consumption.