Release Version 2.28.2

In this release, we have addressed the following issues to improve the usage and functionality of our product features. To know the list of features and integrations we are working on next, read our Upcoming Features 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.

In this Release

• New and Changed Features

• Fixes and Improvements

New and Changed Features

Destinations

• Support for Key Pair Authentication in Snowflake

  • Hevo now supports connecting to your Snowflake data warehouse Destination using a key pair for authentication, making the connection more secure. Instead of a database password, you can now provide a private key while configuring a new Snowflake Destination or modifying an existing one.

    

    Read Obtain a Private and Public Key Pair.

Fixes and Improvements

Sources

• Handling Data Mismatch Issues in Facebook Ads

  • Fixed an issue where the API call to fetch Ads data returned incorrect results if the polling job was interrupted for any reason before retrieving all records for a specific timestamp. This issue occurred because the next poll began fetching data from a timestamp later than the one being processed at the time of interruption, resulting in some records being missed. With this fix, if a poll is interrupted, data fetching will now resume from the same timestamp of the interrupted data, ensuring correct data in the Destination.

• Handling Data Mismatch Issues in Shopify

  • Fixed an issue where the API call to fetch the balance_transactions object returned incorrect results. This issue occurred because the system converted columns containing large numbers to a float data type. However, as the float data type cannot accurately handle large numbers, the values were altered during the conversion process. These altered values were then reverted to their original data type before being loaded into the Destination, causing data discrepancies. With this fix, Hevo ensures that the affected columns are correctly handled by converting them to a long data type, which can accurately store large numbers.

• Handling Data Mismatch Issues in Stripe

  • Fixed an issue where the API call to fetch the Charge object returned null values for the customer_id field, resulting in missing data. This issue occurred because the nested Refund object did not expand the customer Event, and as a result, the customer_id field was not included in the API call. With this fix, Hevo ensures that the customer_id from the Refund object is included as a parameter in the API call, ensuring that the data is loaded accurately into the Destination.