Release Version 2.32.2

Last updated on Feb 03, 2025

This is a minor release and will be integrated into the next major release. At that time, this release note will be merged into the next main release note.

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


New and Changed Features

Sources

  • Migration to v5.0 of the Apple Search Ads Campaign Management API

    • Effective Release 2.32.2, Hevo has upgraded its Apple Search Ads integration to use v5.0 of the Campaign Management API to fetch your data. You are not required to take any action, as Pipelines created with Apple Search Ads have been migrated to the new API version.

      As part of the upgrade, Hevo has added support for the following fields in the Keyword Report object.

      Field Name Description
      suggested_bid_amount Specifies the monetary value in the given currency.
      suggested_bid_currency Indicates the organization’s default currency, as set in the Apple Search Ads UI.

      Note: If you need historical data for the newly supported fields in your existing Pipelines, you must restart the historical load for the Keyword Report object.

      This change applies to all new and existing Pipelines.

  • Salesforce Bulk API V2 as a Source

    • Salesforce Bulk API V2, an improved version of Salesforce, for handling large amounts of data, is now available as a Source in Hevo for all new and existing customers.

      To use this integration, you must authorize Hevo to access the Salesforce Bulk API V2 account from where you want to ingest the data. If you have an existing Pipeline that uses Salesforce Bulk API V1, you can upgrade it to V2.

      Salesforce Upgrade Pipeline

      Read Salesforce Bulk API V2.

  • Support for V18 of the Google Ads API

    • Enhanced the Google Ads integration to support Google Ads API Version 18 for both new and existing Pipelines. This upgrade ensures that all the newly added resources, including attributes and metrics, are added to your reports.

      You are not required to take any action, as existing Pipelines are automatically upgraded to V18 during the next poll.

      The new API version has removed the following attributes:

      Objects Attributes
      AdGroupAd - ad_group_ad.ad.discovery_carousel_ad.business_name
      - ad_group_ad.ad.discovery_carousel_ad.call_to_action_text
      - ad_group_ad.ad.discovery_carousel_ad.carousel_cards
      - ad_group_ad.ad.discovery_carousel_ad.description
      - ad_group_ad.ad.discovery_carousel_ad.headline
      - ad_group_ad.ad.discovery_carousel_ad.logo_image
      - ad_group_ad.ad.discovery_multi_asset_ad.business_name
      - ad_group_ad.ad.discovery_multi_asset_ad.call_to_action_text
      - ad_group_ad.ad.discovery_multi_asset_ad.descriptions
      - ad_group_ad.ad.discovery_multi_asset_ad.headlines
      - ad_group_ad.ad.discovery_multi_asset_ad.lead_form_only
      - ad_group_ad.ad.discovery_multi_asset_ad.logo_images
      - ad_group_ad.ad.discovery_multi_asset_ad.marketing_images
      - ad_group_ad.ad.discovery_multi_asset_ad.portrait_marketing_images
      - ad_group_ad.ad.discovery_multi_asset_ad.square_marketing_images
      - ad_group_ad.ad.discovery_video_responsive_ad.breadcrumb1
      - ad_group_ad.ad.discovery_video_responsive_ad.breadcrumb2
      - ad_group_ad.ad.discovery_video_responsive_ad.business_name
      - ad_group_ad.ad.discovery_video_responsive_ad.call_to_actions
      - ad_group_ad.ad.discovery_video_responsive_ad.descriptions
      - ad_group_ad.ad.discovery_video_responsive_ad.headlines
      - ad_group_ad.ad.discovery_video_responsive_ad.logo_images
      - ad_group_ad.ad.discovery_video_responsive_ad.long_headlines
      - ad_group_ad.ad.discovery_video_responsive_ad.vide
      Campaign - campaign.discovery_campaign_settings.upgraded_targeting

      Note: Hevo no longer supports ingesting data for the attributes metrics listed in the table above, so the corresponding Destination columns are also not updated.

      The new API version includes the following new attributes:

      Objects Attributes
      AdGroupAd - ad_group_ad.ad.demand_gen_carousel_ad.business_name
      - ad_group_ad.ad.demand_gen_carousel_ad.call_to_action_text
      - ad_group_ad.ad.demand_gen_carousel_ad.carousel_cards
      - ad_group_ad.ad.demand_gen_carousel_ad.description
      - ad_group_ad.ad.demand_gen_carousel_ad.headline
      - ad_group_ad.ad.demand_gen_carousel_ad.logo_image
      - ad_group_ad.ad.demand_gen_multi_asset_ad.business_name
      - ad_group_ad.ad.demand_gen_multi_asset_ad.call_to_action_text
      - ad_group_ad.ad.demand_gen_multi_asset_ad.descriptions
      - ad_group_ad.ad.demand_gen_multi_asset_ad.headlines
      - ad_group_ad.ad.demand_gen_multi_asset_ad.lead_form_only
      - ad_group_ad.ad.demand_gen_multi_asset_ad.logo_images
      - ad_group_ad.ad.demand_gen_multi_asset_ad.marketing_images
      - aad_group_ad.ad.demand_gen_multi_asset_ad.portrait_marketing_images
      - ad_group_ad.ad.demand_gen_multi_asset_ad.square_marketing_images
      - ad_group_ad.ad.demand_gen_video_responsive_ad.breadcrumb1
      - ad_group_ad.ad.demand_gen_video_responsive_ad.breadcrumb2
      - ad_group_ad.ad.demand_gen_video_responsive_ad.business_name
      - ad_group_ad.ad.demand_gen_video_responsive_ad.call_to_actions
      - ad_group_ad.ad.demand_gen_video_responsive_ad.descriptions
      - ad_group_ad.ad.demand_gen_video_responsive_ad.headlines
      - aad_group_ad.ad.demand_gen_video_responsive_ad.logo_images
      - ad_group_ad.ad.demand_gen_video_responsive_ad.long_headlines
      - ad_group_ad.ad.demand_gen_video_responsive_ad.videos
      - ad_group_ad.ad_group_ad_asset_automation_settings
      AdGroup - ad_group.exclude_demographic_expansion
      - ad_group.fixed_cpm_micros
      - ad_group.target_cpv_micros
      Campaign - campaign.brand_guidelines_enabled
      - campaign.demand_gen_campaign_settings.upgraded_targeting
      - campaign.fixed_cpm.goal
      - campaign.fixed_cpm.target_frequency_info.target_count
      - campaign.fixed_cpm.target_frequency_info.time_unit
      - campaign.keyword_match_type
      - campaign.target_cpv
      - campaign.video_campaign_settings.video_ad_inventory_control.allow_in_feed
      - campaign.video_campaign_settings.video_ad_inventory_control.allow_in_stream
      - campaign.video_campaign_settings.video_ad_inventory_control.allow_shorts

      The new API version includes the following new metrics:

      Objects Metrics
      Campaign - metrics.general_invalid_click_rate
      - metrics.general_invalid_clicks
      Customer - metrics.general_invalid_click_rate
      - metrics.general_invalid_clicks
      GenderView - metrics.search_impression_share
      KeywordView - metrics.phone_calls

Fixes and Improvements

Destinations

  • Handling Failed Events due to Connection Reset in SQL Server

    • Fixed an issue where Events that failed due to a connection reset while loading to the Destination had to be manually replayed. This issue occurred because the connection to the Destination was interrupted, causing Events to be lost if not replayed within seven days. With this fix, Hevo now automatically replays Events that fail due to a connection reset, ensuring successful data loading. This fix applies to all new and existing Pipelines.

Sources

  • Handling Null Values in HSTORE Data for PostgreSQL Source

    • Fixed an issue affecting all variants of PostgreSQL Source in which HSTORE data was incorrectly displayed as NULL. This issue occurred because Hevo did not recognize the HSTORE data type when defined under specific schemas. In PostgreSQL, HSTORE is used to store key-value pairs and can exist in different schemas such as shared_extensions and public. Earlier, Hevo recognized only HSTORE data when the data type was defined as shared_extensions.hstore, causing a failure when it was defined as public.hstore. With this fix, Hevo now checks for the word hstore in the data type, regardless of how it is written, ensuring that HSTORE data from public.hstore is correctly identified.

Tell us what went wrong