Release Version 2.31.2

Last updated on Jan 06, 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 v21.0 of the Facebook Marketing API

    • Effective Release 2.31.2, the Facebook Ads, Facebook Pages, and Instagram Business integrations use v21.0 of the Marketing API to fetch your data. Pipelines created with Facebook Ads, Facebook Pages, or Instagram Business do not require any action from the user.

      For Instagram Business, the new API version has removed the following metrics:

      Objects Metrics
      video_insights_lifetime_v2 - video_views
      user_insights_rolling_day - email_contacts
      - get_directions_clicks
      - profile_views
      - text_message_clicks
      - website_clicks
      - phone_call_clicks

      For Facebook Pages, the new API version has removed the following:

      • All metrics associated with these objects:

        Objects Metrics
        Page Call Phone Clicks - page_call_phone_clicks_logged_in_unique
        Page Consumption - page_consumptions_by_consumption_type
        - page_consumptions_by_consumption_type_unique
        - page_consumptions_unique
        Page Feedback - page_negative_feedback
        - page_negative_feedback_by_type
        - page_negative_feedback_by_type_unique
        - page_negative_feedback_unique
        Page Get Direction Clicks - page_get_directions_clicks_logged_in_unique
        Page Places Check In - page_places_checkin_total
        - page_places_checkin_total_unique
        Page Tab Views - page_tab_views_login_top
        - page_tab_views_login_top_unique
        - page_tab_views_logout_top
        Page Website Clicks - page_website_clicks_logged_in_unique
      • Specific metrics associated with these objects:

        Objects Metrics
        Page CTA Clicks - page_cta_clicks_logged_in_total
        - page_cta_clicks_logged_in_unique
        Page Fans - page_fans_online
        - page_fans_online_per_day
        Page Impressions - page_impressions_organic_unique_v2
        - page_impressions_by_country_unique
        - page_impressions_by_city_unique
        - page_impressions_by_locale_unique
        - page_impressions_organic_v2
        - page_impressions_by_story_type_unique
        - page_impressions_by_story_type
        - page_impressions_viral_frequency_distribution
        - page_impressions_by_age_gender_unique

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

      This change applies to all new and existing Pipelines created with Facebook Ads, Facebook Pages, or Instagram Business as the Source.

  • Support for Fetching Data using UpdatedAt Filter for the Marketo Leads Object

    • Added support for using the updated_at timestamp in refresher tasks for the Leads object in Marketo Source. This enhancement ensures that updates to older leads, created more than 3 months ago, are accurately synced to the Destination. Additionally, it addresses data mismatches due to previous dependency on the createdAt timestamp.

      The updated_at filter is available only for Marketo accounts that support querying with this field. For unsupported accounts, Hevo still depends on createdAt filter. To enable data fetching using the updatedAt timestamp, contact Hevo Support.

Fixes and Improvements

Sources

  • Handling Data Mismatch Issues in Shopify

    • Fixed an issue where Hevo was unable to uniquely identify records for the Abandoned Checkout Line Items object. This issue occurred because Hevo set the abandoned_checkout_id field as the primary key for the object after ingesting the Events. However, as the abandoned_checkout_id field values were not unique across all records, one record was overwritten by another, resulting in incorrect data being loaded into the Destination.

      To fix this, Hevo generates an additional index field to assign a unique id to each record with the same abandoned_checkout_id value. Now, both fields act together as the primary key, ensuring all records are uniquely identified and correctly loaded into the Destination.

      The fix applies to Pipelines created with Shopify as a Source after Release 2.31.2. If you observe a data mismatch for the Abandoned Checkout Line Items object in your existing Pipelines, contact Hevo Support.

Tell us what went wrong