Braze Source

Ingest your event data from Braze into RudderStack.

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.

info
Currents is available as a self-serve product to any user with an entitlement or license. If you do not have a license, reach out to your Braze account team to get one.

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

Get started

  1. Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select Braze.
  2. Assign a name to your source and click Continue.
  3. Add the Braze event names and custom event names you want to map together. You can add multiple rows by clicking Add more. Then, click Continue.
Braze mapping
  1. Your Braze source is now configured. Go to the Settings tab of the source and note the Webhook URL:
Braze webhook URL
  1. In your Braze dashboard, go to Currents > + Create Currents > RudderStack Export.
  2. Enter an integration name, contact email, RudderStack webhook URL (in the Key field), and your RudderStack region.
  3. Select the events you would like to export and click Launch Current.

Supported events and properties

Braze uses RudderStack’s Event Streams 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 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.
In-App Message ClickedThe user clicked 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_idStringThe API identifier for the app on which the user receives a message/notification or performs some action.
send_idStringThe message ID specified for a particular campaign, if applicable.
campaign_idStringThe API identifier of the campaign associated with the event, if applicable.
canvas_idStringThe API identifier of the Canvas associated with the event, if applicable.
canvas_variation_idStringThe API identifier of the Canvas Variation associated with the event, if applicable.
canvas_step_idStringThe API identifier of the Canvas Step associated with the event, if applicable.
context.traits.emailStringThe email address that the email was sent to, in case of the Email events.
button_idStringThe ID of the button that the user clicked, in case of the In-App Message Clicked event.
card_api_idStringThe API identifier of the News Feed Card, in case of the News Feed Card Viewed and News Feed Card Clicked events.

Questions? Contact us by email or on Slack