Skip to content

Commit bb78241

Browse files
authored
Merge pull request #514 from segmentio/repo-sync
repo sync
2 parents 285840c + 39173c9 commit bb78241

File tree

1 file changed

+1
-1
lines changed
  • src/connections/sources/catalog/cloud-apps/braze

1 file changed

+1
-1
lines changed

src/connections/sources/catalog/cloud-apps/braze/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Braze maintains this source. For any issues with the source, you can [contact th
2323
The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name. The schema name is the namespace you'll query against in a warehouse. The nickname can be anything, but Segment recommends sticking to something that reflects the source itself and distinguishes amongst your environments (for example, `Braze_Prod`, `Braze_Staging`, `Braze_Dev`).
2424
4. Copy the **Write Key** on the Overview page.
2525
5. To finish the setup, contact Braze Support or your Customer Support Manager to activate Currents in Braze.
26-
Braze Currents is only available in select Braze packages and can't be configured within Braze without assistance from your Braze Customer Success representative.
26+
- **Note:** Braze Currents is only available in select Braze packages and can't be configured within Braze without assistance from your Braze Customer Success representative. Select the appropriate **Supported Region** in the Braze Currents configuration if you are using a non U.S. Segment Region.
2727
6. Go back to Segment and click **Add Destinations** in your Braze source to add the destinations where you want to receive your Braze data.
2828

2929
Events are now sent to these destinations and automatically loaded into any warehouses you enabled.

0 commit comments

Comments
 (0)