Release Version 2.31.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

• New and Changed Features
• Fixes and Improvements

New and Changed Features

Sources

• Support for Usage Record Summary object in Stripe

  • Hevo now supports ingesting data from the Usage Record Summary object. This enables capturing total usage details for a subscription item during a billing period, ensuring accurate usage data is available in the Destination.

Fixes and Improvements

Sources

• Handling Data Ingestion for Skipped Objects in Google Analytics 4

  • Fixed an issue where data from skipped objects was inadvertently being ingested during incremental loads. Since objects were processed in batches of five, skipping an object did not exclude its data from being ingested because the batch also contained other active objects. As a result, the entire batch, including the skipped objects, was ingested. This resulted in unnecessary consumption of Event quota and increased costs. With this fix, the system now excludes skipped objects from the batch before ingestion, ensuring only active objects are processed. The fix applies to all new and existing Pipelines.

• Handling Data Mismatch Issues in Shopify

  • Fixed an issue where the API call to fetch the Inventory Location object returned only 50 records, even when additional records were present. Since pagination was not available in the API call, by default, only 50 records could be retrieved per page. With this fix, pagination has been added. When there are more than 50 records, the system uses the link provided for the next page in the API response to fetch subsequent records until all records are retrieved.

  • Fixed an issue where Hevo set the id field as a primary key for the Fulfillment Lines object after ingesting the Events. As the id field values were not unique across all records, one data record was overwritten by another, resulting in incorrect data being loaded into the Destination. With this fix, Hevo now sets an additional field, fulfillment_id, along with the id field as the primary key to uniquely identify each data record. This ensures that all data is correctly loaded into the Destination. The fix applies to all new and existing Pipelines.

    Note: If you observe a data mismatch for the Fulfillment Lines object in your existing Pipelines, you must restart the object.

• Handling Data Mismatch Issues in Stripe

  • Fixed an issue where the price_id field was not included while parsing the API response for the Subscription Item object, resulting in incomplete data being fetched. With this fix, Hevo now includes the field during parsing, ensuring that all data from the object is fetched. The fix applies to all new and existing Pipelines.

    Note: You must restart the object in your existing Pipelines to include the price_id field and ensure all historical records are correctly loaded into the Destination. This may lead to higher Events quota consumption.