Braze Release Notes

June 2021link

We have added a new table, RANDOM_BUCKET_NUMBER_EVENT. For more information, see Braze’s Customer Behavior and User Events documentation.

December 2020link

We have added a new column, event_type, to the following tables:

• ATTRIBUTION_EVENT
• CAMPAIGN_CONVERSION_EVENT
• CAMPAIGN_ENROLLMENT_EVENT
• CANVAS_CONVERSION_EVENT
• CANVAS_ENTRY_EVENT
• CUSTOM_EVENT
• LOCATION_EVENT
• NEWSFEED_IMPRESSION_EVENT
• PURCHASE_EVENT
• SMS_EVENT
• SUBSCRIPTION_EVENT
• UNINSTALL_EVENT
• WEBHOOK_EVENT

November 2020link

We have fixed a problem with the canvas_step_id column’s foreign key in the MESSAGE_VARIATION table. We now map the MESSAGE_VARIATION.canvas_step_id column to the CANVAS_STEP table’s id column. Previously, we mapped it to the CANVAS table’s id column. We will re-sync the following tables to correct your existing data:

• CANVAS
• CANVAS_STEP
• CANVAS_STEP_SEQ
• CANVAS_TAG
• CANVAS_VARIATION
• MESSAGE_VARIATION

October 2020link

We have added two new tables, USER and USER_ALIAS. See Braze’s Export User endpoint documentation for more information.

We have also created foreign key relationships to the following tables that reference the primary key column user_id of the USER table:

• ATTRIBUTION_EVENT
• CAMPAIGN_CONVERSION_EVENT
• CAMPAIGN_ENROLLMENT_EVENT
• CAMPAIGN_CONVERSION_EVENT
• CANVAS_ENTRY_EVENT
• CONTENT_CARD_EVENT
• CUSTOM_EVENT
• EMAIL_EVENT
• IN_APP_MESSAGE_EVENT
• LOCATION_EVENT
• NEWSFEED_CARD_EVENT
• NEWSFEED_IMPRESSION_EVENT
• PURCHASE_EVENT
• PUSH_NOTIFICATION_EVENT
• SESSION_EVENT
• SMS_EVENT
• SUBSCRIPTION_EVENT
• UNINSTALL_EVENT

August 2020link

We have added a new primary key column, id, to the CANVAS_VARIATION table and added foreign key relationships to the following tables which reference this column:

• CAMPAIGN
• CARD
• CANVAS_CONVERSION_EVENT
• CANVAS_ENTRY_EVENT
• CONTENT_CARD_EVENT
• EMAIL_EVENT
• IN_APP_MESSAGE_EVENT
• PUSH_NOTIFICATION_EVENT
• SMS_EVENT
• SUBSCRIPTION_EVENT
• WEBHOOK_EVENT

We will re-sync the CANVAS_VARIATION table in order to populate this column.

May 2020link

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.

April 2020link

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 timestamp column.

We have added the following columns to the tables below:

• dispatch_id to the PUSH_NOTIFICATION_EVENT and EMAIL_EVENT tables
• channel and phone_number to the SUBSCRIPTION_EVENT table

February 2020link

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 TRUE.

We have added the following fields to the tables below:

• first_entry and last_entry to the CANVAS table
• conversion_behavior to the CAMPAIGN_CONVERSION_BEHAVIOR and CANVAS_CONVERSION_BEHAVIOR tables
• timezone to the CAMPAIGN_CONVERSION_EVENT, CAMPAIGN_ENROLLMENT_EVENT, CANVAS_ENTRY_EVENT, and EMAIL_EVENT tables

August 2019link

• 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.

July 2019link

Fixed an out of memory error that occurs when the number of files in the current Braze bucket is extremely large.

May 2019link

Braze is a platform for cross-channel marketing automation.

Link to Braze Documentation