Braze is a customer engagement platform that helps you better understand your customers' in-app behavior and use the insights to improve your users' app experience.

You can send your Braze events to RudderStack by leveraging Braze Currents.

This guide will help you set up Braze as a source in RudderStack.

Getting started

Follow these steps to set up your Braze source in the RudderStack dashboard:

  1. Go to your RudderStack dashboard and click on Add Source. From the list of Event Stream sources, select Braze.
  2. Assign a name to your source and click Continue.
  3. Your Braze is now configured. Note the source Write key required to configure the webhook URL.
Braze source write key
  1. To complete the setup, contact Braze's support team to activate Currents in your Braze account.
Currents is available in select pro and enterprise-level Braze packages and can be configured only with the Braze team's assistance. For support, you can contact their Customer Success team.

Supported events and properties

Braze uses RudderStack's Event Stream functionality to send events to RudderStack. These events can then be transformed and routed to your preferred destinations, including your data warehouse.

The following table lists all the Braze events supported by RudderStack:

Event nameEvent description
Application UninstalledThe user uninstalled the application.
Campaign ConvertedThe user performed the primary conversion events for a Campaign within its conversion window.
Canvas ConvertedThe user performed the primary conversion event for a Canvas within its conversion window.
Canvas EnteredThe user was entered into a Canvas.
Campaign Control Group EnteredThe user was enrolled in a Campaign control group.
Email SentAn email was successfully sent to the user.
Email DeliveredAn email was successfully delivered to the user.
Email OpenedThe user opened an email.
Email Link ClickedThe user clicked a link within an email. Note that the email click tracking feature must be enabled.
Email BouncedTriggered when Braze attempts to send an email but the receipient's email server does not accept it.
Email Soft BouncedTriggered when Braze attempts to send an email but the recepient's email server bounces it temporarily because of reasons like full inbox, email server down, etc.
Email Marked As SpamThe user marked an email as spam.
Email UnsubscribedThe user clicked on the unsubscribe link within an email.
Subscription Group State ChangedThe user's subscription group status changed to Subscribed or Unsubscribed.
Push Notification SentA push notification was successfully sent to the user.
Push Notification TappedThe user tapped on a push notification.
iOS Foreground Push OpenedThe user received an iOS push notification while the app was open.
In-App Message ViewedThe user viewed an in-app message.
News Feed ViewedThe user viewed the Braze News Feed.
News Feed Card ViewedThe user viewed a card within the Braze News Feed.
News Feed Card ClickedThe user tapped or clicked on Braze News Feed card.
Webhook SentA webhook message was sent.

The following table lists the properties included in the events mentioned above:

Property nameProperty typeDescription
app_idStringRefers to the app's API identifier on which the user receives a message/notification or performs some action.
send_idStringRefers to the message ID specified for a particular campaign, if applicable.
campaign_idStringRefers to the API identifier of the campaign associated with the event, if applicable.
canvas_idStringRefers to the API identifier of the Canvas associated with the event, if applicable.
canvas_variation_idStringRefers to the API identifier of the Canvas Variation associated with the event, if applicable.
canvas_step_idStringRefers to the API identifier of the Canvas Step associated with the event, if applicable.
context.traits.emailStringRefers to the email address that the email was sent to, in case of the Email events.
button_idStringRefers to the ID of the button that the user clicked, in case of the In-App Message Clicked events.
card_idStringRefers to the API identifier of the News Feed Card, in case of the News Feed Card Viewed and News Feed Card Clicked events.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

Contents