Setting up Currents

This page outlines and describes the generic process for integrating and configuring Braze Currents.

Requirements

Using Currents with any of our partners requires the same basic parameters and connection methodology.

Each partner requires that Braze has permission to write and send data files to them, and Braze asks for the location they should write those files to, specifically bucket names or keys.

The following requirements are the basic, minimum requirements to integrate with most of our partners. Some partners will require additional parameters, which are listed in their respective partner documentation along with any nuances associated with these basic requirements.

Requirement	Origin	Access	Description
Account with partner	Arrange account with that partner or reach out to your Braze account manager for suggestions.	Check that partner’s site or reach out to that partner to sign up.	Braze will not send data to a partner if you don’t have access to that data through your company’s account.
Partner API Key or Token	Usually the partner’s dashboard.	Just copy and paste it into the designated Braze field.	Braze has a designated field for this in the integrations page for that partner. We need this to map where we are sending your data. It’s important to keep your Partner Keys or Tokens up to date; invalid credentials may result in disabling your connector, and dropping events.
Authentication Code/Key, Secret Key, Certification File	Contact a representative for your account with that partner. May also exist in the partner’s dashboard.	Copy and paste keys into the designated Braze field. Generate and upload .json or other certification files into the appropriate place in Braze.	Braze has a designated field for this in the integrations page for that partner. This gives Braze credentials and authorizes us to write files to your partner account. It’s important to keep your authentication details up to date; invalid credentials may result in disabling your connector, and dropping events.
Bucket, Folder Path	Some partners organize and sort data by buckets. This should be found in the partner’s dashboard.	If this is required, be sure to copy the bucket name or file path exactly into the designated space in Braze. We don’t want your data to get lost!	Though this is required for some partners, it’s important to get right when you do need it.

Setting up Currents

Step 1: Choose your partner

Braze Currents allows you to integrate through Data Storage using flat files or to our behavioral analytics and customer data partners using a batched JSON payloads to a designated endpoint.

Before you begin your integration, it’s best to decide which integration is best for your purposes. For example, if you already use mParticle and Segment and would like Braze data to stream there, it would be best to use a batched JSON payload. If you would prefer to manipulate the data on your own or have a more complex system of data analysis, it might be best to use Data Storage (Braze uses this method!)

Step 2: Open Currents

To get started, go to Partner Integrations > Data Export. You’ll be taken to the Currents integration management page.

Step 3: Add your partner

Add a partner, sometimes called a “Currents connector,” by selecting the dropdown at the top of the screen.

Each partner requires a different set of configuration steps. To enable each integration, refer to our list of available partners and follow the instructions on their respective pages.

Step 4: Configure your events

Choose the events you wish to pass to that partner by checking from the available options. You can find listings of these events in our Customer Behavior Events and Message Engagement Events libraries.

If needed, you can learn more about our events in our event delivery semantics article.

Step 5: Set up field transformations

You can use Currents field transformations to remove or hash a string field.

• Remove: Replaces the string field with [REDACTED]. This is helpful if your partner rejects events with missing or empty fields.
• Hash: Applys an SHA-256 hashing algorithm to the string field.

Selecting a field for one of these transformations will apply that transformation to all events in which that field appears. For example, selecting email_address for hashing will hash the email_address field in Email Send, Email Open, Email Bounce, and Subscription Group State Change events.

Step 6: Test your integration

You may test your integration or take a look at the sample Currents data in our Currents examples GitHub repository.

Testing Currents connectors

Test Currents connectors are free versions of our existing connectors that can be used for testing and trying out different destinations. Test Currents have:

• No limit to the number of Test Currents connectors you may build.
• An aggregate maximum of 10,000 events per seven-day rolling period. This event total is updated hourly on the dashboard.

After your Test Currents connectors reach the sending limit, your connector will not send events until the next seven-day period.

To upgrade your Test Currents connector, edit the integration in the dashboard and select Upgrade.

Updating Currents

To update your Currents connector after launching, do the following:

1. In Braze, navigate to Partner Integrations > Data Export.
2. Locate and your Currents connector in the list.
3. Select  Edit.
4. Make your changes.
5. Select Update Current.

This will not stop your existing export and will begin sending events according to your new selection.

IP allowlisting

Braze will send Currents data from the listed IPs.

For Instances US-01, US-02, US-03, US-04, US-05, US-06, and US-07:
127.0.0.1
23.21.118.191
34.206.23.173
50.16.249.9
52.4.160.214
54.87.8.34
54.156.35.251
52.54.89.238
18.205.178.15

For Instances EU-01 and EU-02:
127.0.0.1
52.58.142.242
52.29.193.121
35.158.29.228
18.157.135.97
3.123.166.46
3.64.27.36
3.65.88.25
3.68.144.188
3.70.107.88

For Instance US-08:
52.151.246.51
52.170.163.182
40.76.166.157
40.76.166.170
40.76.166.167
40.76.166.161
40.76.166.156
40.76.166.166
40.76.166.160
40.88.51.74
52.154.67.17
40.76.166.80
40.76.166.84
40.76.166.85
40.76.166.81
40.76.166.71
40.76.166.144
40.76.166.145