Release Notes

October 2025

We've added a new column, preheader, to the MESSAGE_VARIATION table. We've also added a new table, USER_PUSH_TOKEN.

September 2025

We no longer support historicSyncTimeFrame when creating connections using REST API configuration.

We have added two new columns, is_suspected_bot_click and suspected_bot_click_reason, to the SMS_EVENT table. These columns sync data that helps identify potential bot activity in SMS link clicks, improving data quality for fraud detection and analytics.

We have added two new columns, is_suspected_bot_click and suspected_bot_click_reason, to the EMAIL_EVENT table.

June 2025

We've added the created_at column to the USER table. This column contains the timestamp of when the user profile was created in Braze, in ISO 8601 format.

This allows you to better track the lifecycle of users and analyze registration patterns and tenure across your Braze user base.

March 2025

We have added a new field, Sync data from selected date, under the Historical Sync Time Frame dropdown in the setup form. This allows you to select the exact date up to which the backward sync will occur. The default value is Sync all historical data. You can edit the connection details and update the time frame for an existing connector.

This limit applies to the following tables:

ATTRIBUTION_EVENT
CAMPAIGN_CONTROL_ENROLLMENT_EVENT
CAMPAIGN_CONVERSION_EVENT
CANVAS_CONVERSION_EVENT
CANVAS_ENTRY_EVENT
CANVAS_EXIT_EVENT
CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT
CANVAS_EXPERIMENT_STEP_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
RANDOM_BUCKET_NUMBER_EVENT
SESSION_EVENT
SMS_EVENT
SUBSCRIPTION_EVENT
UNINSTALL_EVENT
WEBHOOK_EVENT
WHATSAPP_EVENT

We are gradually rolling out this feature to all connections.

October 2024

We have added a new field, Historical Sync Time Frame, to the connection setup form. This allows you to select how many months' worth of historical data you want to sync. For an existing connection, you can edit the connection details and set the time frame value. We have also added support for the historic_sync_time_frame field for connections created using the Create a connection endpoint. For more information, see our REST API config.

Historical sync limits apply to the following tables:

ATTRIBUTION_EVENT
CAMPAIGN_CONTROL_ENROLLMENT_EVENT
CAMPAIGN_CONVERSION_EVENT
CANVAS_CONVERSION_EVENT
CANVAS_ENTRY_EVENT
CANVAS_EXIT_EVENT
CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT
CANVAS_EXPERIMENT_STEP_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
RANDOM_BUCKET_NUMBER_EVENT
SESSION_EVENT
SMS_EVENT
SUBSCRIPTION_EVENT
UNINSTALL_EVENT
WEBHOOK_EVENT
WHATSAPP_EVENT

July 2024

We now support user profile exports configured with Google Cloud Storage. For more information, see our Braze documentation.

April 2024

We have added a new column, is_api_campaign, to the CAMPAIGN table.

March 2024

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

CONTENT_CARD_EVENT
EMAIL_EVENT
PUSH_NOTIFICATION_EVENT
SMS_EVENT
WEBHOOK_EVENT

February 2024

We have added two new columns, channel_content_cards and channel_sms, to the following tables:

CAMPAIGN
CANVAS
CANVAS_STEP

We are gradually rolling out these changes to all existing connections.

November 2023

We have added the following new tables:

SEGMENT
SEGMENT_MEMBER
SEGMENT_TAG
WHATSAPP_EVENT

To sync the SEGMENT_MEMBER table, you must select the USER table on the Schema tab of your connector details page.

Also, we now sync the following events types from Braze Currents in the WHATSAPP_EVENT table:

users.messages.whatsapp.Read
users.messages.whatsapp.Delivery
users.messages.whatsapp.Failure
users.messages.whatsapp.Send
users.messages.whatsapp.Abort
users.messages.whatsapp.InboundReceive

For more information, see Braze's Message engagement events.

May 2023

We have added two new tables, CANVAS_EXIT_EVENT and CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT.

We now support the CANVAS_EXPERIMENT_STEP_ENTRY_EVENT table.

We have added the following new columns to the CONTENT_CARD_EVENT table:

app_group_id
abort_log
abort_type
canvas_step_message_variation_id
canvas_step_message_variation_updated_at
dispatch_id

We have added the following new columns to the EMAIL_EVENT table:

app_group_id
abort_log
abort_type
canvas_step_message_variation_id
canvas_step_message_variation_updated_at
device_id:DEVICE

We have added the following new columns to the IN_APP_MESSAGE_EVENT table:

abort_log
abort_type
ad_id
ad_id_type
ad_tracking_enabled
app_group_id
browser
canvas_step_message_variation_id
canvas_step_message_variation_updated_at
carrier
dispatch_id
resolution
version

We have added the following new columns to the PUSH_NOTIFICATION_EVENT table:

abort_log
abort_type
app_group_id
canvas_step_message_variation_id
canvas_step_message_variation_updated_at

We have added the following new columns to the NEWSFEED_CARD_EVENT table:

abort_log
abort_type
app_group_id
browser
carrier
resolution

We have added the following new columns to the SMS_EVENT table:

app_group_id
abort_type
abort_log
canvas_step_message_variation_id
canvas_step_message_variation_updated_at
timezone
url
short_url
user_agent

We have added the following new columns to the SUBSCRIPTION_EVENT table:

app_group_id
app_id
state_change_source

We have added the following new columns to the WEBHOOK_EVENT table:

abort_log
abort_type
app_group_id
canvas_step_message_variation_id
canvas_step_message_variation_updated_at
device_id
dispatch_id

We now sync the following events types from Braze Currents into the corresponding destination tables:

Event Type	Destination table
`users.messages.contentcard.Abort`	`CONTENT_CARD_EVENT`
`users.messages.email.Abort`	`EMAIL_EVENT`
`users.messages.inappmessage.Abort`	`IN_APP_MESSAGE_EVENT`
`users.messages.newsfeedcard.Abort`	`NEWSFEED_CARD_EVENT`
`users.messages.pushnotification.Abort`	`PUSH_NOTIFICATION_EVENT`
`users.messages.sms.Abort`	`SMS_EVENT`
`users.messages.webhook.Abort`	`WEBHOOK_EVENT`
`users.canvas.exit.PerformedEvent`	`CANVAS_EXIT_EVENT`
`users.canvas.exit.MatchedAudience`	`CANVAS_EXIT_EVENT`
`users.canvas.experimentstep.Conversion`	`CANVAS_EXPERIMENT_STEP_CONVERSION_EVENT`
`users.messages.sms.ShortLinkClick`	`SMS_EVENT`
`users.behaviors.subscription.GlobalStateChange`	`SUBSCRIPTION_EVENT`

For more information, see Braze's Message engagement events.

We have made the Folder (or Prefix) field mandatory in the connector setup form.

March 2023

You can now opt to create a new Braze connector without configuring a Braze Currents connection. Previously, you could only create a new connector to sync Braze Currents data using a cloud storage service. For more information, see our setup instructions. As a part of this improvement, we will also perform a one-time free re-sync of the following tables:

CAMPAIGN
CAMPAIGN_TAG
CANVAS
CANVAS_STEP
CANVAS_STEP_SEQ
CANVAS_TAG
CANVAS_VARIATION
CARD
CARD_EXTRA
CARD_TAG
MESSAGE_VARIATION

February 2023

The Braze connector now supports table blocking for all Braze tables. You can now choose which tables to sync and which to block from syncing to your destination. On your Connector Details page, go to the Schema tab and select or deselect the tables. If you want to sync a child table, you must include the parent table in the sync.

December 2022

We have added a new column, channel_in_app_message, to the CAMPAIGN, CANVAS, and CANVAS_STEP tables.

November 2022

We have added a new table, CANVAS_EXPERIMENT_STEP_ENTRY_EVENT. If you want to sync data for this table, contact our support team.

We have added the following new columns to the EMAIL_EVENT table:

bounce_reason
esp
from_domain
ip_pool
is_amp
is_drop
link_alias
link_id
machine_open

July 2022

The Braze connector now supports Azure Blob Storage. For more information, see our setup instructions.

June 2021

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

December 2020

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 2020

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 2020

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 2020

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 2020

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 2020

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 discontinue 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 2020

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 2019

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 2019

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

May 2019

Braze is a platform for cross-channel marketing automation.

Read our Braze connector documentation.