Braze
Braze is a platform for cross-channel marketing automation.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | check | CAMPAIGN, CANVAS, CARD, SEGMENT, and SEGMENT_MEMBER tables |
| History mode | check | CAMPAIGN, CAMPAIGN_CONVERSION_BEHAVIOR, CAMPAIGN_TAG, CANVAS_STEP, CANVAS_STEP_SEQ, CANVAS_TAG, CANVAS_CONVERSION_BEHAVIOR, CANVAS_VARIATION, CARD, CARD_EXTRA, CARD_TAG, MESSAGE_VARIATION, SEGMENT, and SEGMENT_TAG tables |
| Custom data | ||
| Data blocking | check | |
| Column hashing | check | |
| Re-sync | check | |
| API configurable | check | API configuration |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API | check |
Setup guide
Follow our step-by-step Braze setup guide to connect Braze with your destination using Fivetran connectors.
Sync overview
You can opt to configure the Braze connector in two ways:
- with Braze Currents data using a cloud storage service
- without using a Braze Currents connection
Fivetran can sync historical data from Braze for as long as your Current has existed.
We sync the following event types from Braze Currents into the corresponding destination tables:
users.messages.pushnotification.Sendusers.messages.pushnotification.Openusers.messages.pushnotification.IosForegroundusers.messages.pushnotification.Bounceusers.messages.pushnotification.Abortusers.messages.email.Sendusers.messages.email.Deliveryusers.messages.email.Openusers.messages.email.Clickusers.messages.email.Bounceusers.messages.email.SoftBounceusers.messages.email.MarkAsSpamusers.messages.email.Unsubscribeusers.messages.email.Abortusers.behaviors.subscriptiongroup.StateChangeusers.behaviors.subscription.GlobalStateChangeusers.messages.inappmessage.Impressionusers.messages.inappmessage.Clickusers.messages.inappmessage.Abortusers.messages.webhook.Sendusers.messages.webhook.Abortusers.messages.newsfeedcard.Impressionusers.messages.newsfeedcard.Clickusers.messages.newsfeedcard.Abortusers.messages.contentcard.Sendusers.messages.contentcard.Impressionusers.messages.contentcard.Clickusers.messages.contentcard.Dismissusers.messages.contentcard.Abortusers.messages.sms.Sendusers.messages.sms.SendToCarrierusers.messages.sms.Deliveryusers.messages.sms.Rejectionusers.messages.sms.DeliveryFailureusers.messages.sms.CarrierSendusers.messages.sms.InboundReceiveusers.messages.sms.Abortusers.messages.sms.ShortLinkClickusers.campaigns.Conversionusers.canvas.Conversionusers.canvas.Entryusers.canvas.exit.PerformedEventusers.canvas.exit.MatchedAudienceusers.campaigns.EnrollInControlusers.behaviors.CustomEventusers.behaviors.Purchaseusers.behaviors.app.FirstSessionusers.behaviors.app.SessionStartusers.behaviors.app.SessionEndusers.behaviors.Locationusers.behaviors.app.NewsFeedImpressionusers.behaviors.Uninstallusers.behaviors.InstallAttributionusers.RandomBucketNumberUpdateusers.canvas.experimentstep.SplitEntryusers.canvas.experimentstep.Conversionusers.messages.whatsapp.Readusers.messages.whatsapp.Deliveryusers.messages.whatsapp.Failureusers.messages.whatsapp.Sendusers.messages.whatsapp.Abortusers.messages.whatsapp.InboundReceive
If Enable User Profile Exports is selected, we sync the SEGMENT_MEMBER, USER, and USER_ALIAS tables at the end of the sync. The User Profile Export does not provide a way for us to perform incremental updates, so we sync all user segments once a day. Therefore, you may notice longer sync times after enabling these tables. For larger user exports, we recommend creating a separate connector for these tables to avoid potential sync delays for other tables.
Schema information
This schema applies to all Braze connections.
To zoom, open the ERD in a new window.Schema notes
We use Braze Currents to retrieve data from the event tables.
We use the Braze API and your API key to retrieve data for the following tables:
CAMPAIGNCAMPAIGN_CONVERSION_BEHAVIORCAMPAIGN_TAGCANVASCANVAS_CONVERSION_BEHAVIORCANVASSTEPCANVASSTEPSEQCANVASTAGCANVASVARIATIONCARDCARDEXTRACARDTAGDEVICESEGMENTSEGMENT_MEMBERSEGMENT_TAGUSERUSER_ALIAS
To prevent data discrepancy in the DEVICE table, you must select the following event tables in the Schema tab on your Fivetran dashboard:
CONTENT_CARD_EVENTCUSTOM_EVENTEMAIL_EVENTIN_APP_MESSAGE_EVENTLOCATION_EVENTNEWSFEED_CARD_EVENTNEWSFEED_IMPRESSION_EVENTPURCHASE_EVENTPUSH_NOTIFICATION_EVENTSESSION_EVENTWEBHOOK_EVENTWHATSAPP_EVENT
To prevent data discrepancy in the MESSAGE_VARIATION table, you must select the CAMPAIGN and CANVAS_STEP tables in the Schema tab on your Fivetran dashboard.
Limit historical data sync
In the setup form, you can set a limit on the historical data you want to sync during historical syncs and initial syncs. This limit applies to the following tables:
ATTRIBUTION_EVENTCAMPAIGN_CONTROL_ENROLLMENT_EVENTCAMPAIGN_CONVERSION_EVENTCANVAS_CONVERSION_EVENTCANVAS_ENTRY_EVENTCANVAS_EXIT_EVENTCANVAS_EXPERIMENT_STEP_CONVERSION_EVENTCANVAS_EXPERIMENT_STEP_ENTRY_EVENTCONTENT_CARD_EVENTCUSTOM_EVENTEMAIL_EVENTIN_APP_MESSAGE_EVENTLOCATION_EVENTNEWSFEED_CARD_EVENTNEWSFEED_IMPRESSION_EVENTPURCHASE_EVENTPUSH_NOTIFICATION_EVENTRANDOM_BUCKET_NUMBER_EVENTSESSION_EVENTSMS_EVENTSUBSCRIPTION_EVENTUNINSTALL_EVENTWEBHOOK_EVENTWHATSAPP_EVENT