On this page

Braze (Event Stream)

The Amplitude Activation Braze streaming integration forwards your Amplitude events and users to Braze with a few clicks.

Use cases

Event streaming sends a message to a customer immediately after they perform an action. For example:

  • Email a customer who abandoned their cart.
  • Congratulate a customer who completed a sticky action.

Set up the integration

Prerequisites

To configure streaming from Amplitude to Braze, you need the following information from Braze.

  • Braze API Endpoint: The Braze endpoint for REST operations.
  • Braze API Key: The Braze API key used for authentication. Refer to the Braze documentation for help determining your endpoint or locating your API key.
  • Braze App ID: The Braze App ID for the app receiving Amplitude events. Refer to the Braze docs for help locating your app ID.

Create a new sync

  1. In Amplitude Data, click Catalog and select the Destinations tab.
  2. Select Braze (Events · User Properties) or filter by Type > Events.
  3. Select Add Destination.
  4. Enter a sync name, then click Create Sync.

Enter credentials

  1. Select your Braze API Endpoint.
  2. Enter your Braze API Key.
  3. Enter your Braze App ID.
  4. If you use the Braze User Alias to identify your users on Braze, enter the Braze User Alias Label you plan to use. Otherwise, ignore this field.
  5. Check the Update Users Only option to update users that exist in Braze without creating new users. If you send alias-only user profiles, don't check this field. If you check Update Users Only, Amplitude doesn't create your alias-only user profiles in Braze. For more information, refer to the Braze documentation.

Configure mappings

This applies to both event and user forwarding.

  1. Select an Amplitude user property that corresponds to your Braze user ID, from the left dropdown.
  2. Select the type of your Braze user ID, from the right dropdown.
    • External ID: Any unique identifier for each user in Braze.
    • Braze ID: A unique identifier Braze provides for each user.
    • User Alias: An alternative unique identifier for each user in Braze.
    • Email: Using email as the identifier without an External ID or Braze ID may lead to unexpected behavior. For example, if Amplitude sends a user to Braze with an ID and the same email, Braze doesn't merge them, resulting in two separate users. To avoid this case, refer to the Braze User Profiles documentation. Braze also provides a Merge User API for merging users.

Configure event forwarding

Under Send Events, enable the toggle ("Events are sent to Braze") if you want to stream events to Braze. When enabled, Amplitude automatically forwards events to Braze when it ingests them. Amplitude doesn't send events on a schedule or on-demand using this integration.

  1. In Select and filter events, choose which events you want to send. Choose only the events you need in Braze.

Events for anonymous users

Braze requires that all events have an identifier present. If you selected events that might not have an identifier, add a filter to send only events where the identifier is present. Otherwise, your delivery metrics may be affected.

  1. (optional) In Select additional properties, select any more event and user properties you want to send to Braze. If you don't select any properties here, Amplitude doesn't send any. Amplitude sends these properties to Braze as Braze custom event properties.

Configure user forwarding

To stream user and property updates to Braze, enable Send Users. This setting creates or updates users in Braze when you update them in Amplitude with the HTTP V2 API or Identify API. This integration doesn't support scheduled or on-demand updates.

You can optionally select user properties to send to Braze in the Select additional properties field. Amplitude sends only the properties you select and only when one of them is updated. Amplitude sends these properties as Braze custom attributes.

Enable sync

When you finish your configuration, toggle the Status to Enabled at the top of the page and click Save.

Was this helpful?