You can now configure your Braze connector using the Fivetran REST API. This feature is in BETA and is available only for Standard and Enterprise accounts.
We have added support for SMS and Content Card message engagement events.
We have fixed an issue where API response time data was not being synced into the
timestamp column in the
SESSION_EVENT table. We will now sync this data into a new column,
time, and deprecate the
We have added the following columns to the tables below:
We have added primary keys and foreign keys to improve data integrity.
We have updated the Delete mechanism to keep historical data. Now, when you delete a row from the source table, we set the
_fivetran_deleted column value of the corresponding row in the destination to
We have added the following fields to the tables below:
We have added a new connection test to the Braze setup screen that helps you adopt security best practices. The test checks your bucket policy settings to make sure you have created your Role ARN using the given externalID when configuring your AWS S3 bucket. If you mistakenly create your Role ARN without using the given externalID, the configuration will now fail the test. You will have to correct your Role ARN configuration.
We now validate that the configured storage contains Braze Current files. You must configure Braze Current before you configure the Braze connector.
We treat the API key and role as passwords, so we don't display them on the screen to improve security.
Fixed an out of memory error that occurs when the number of files in the current Braze bucket is extremely large.
Braze is a platform for cross-channel marketing automation.