Skip to content

Commit 7f27701

Browse files
author
markzegarelli
committed
DOC-377 Braze update
1 parent a3ebda2 commit 7f27701

File tree

1 file changed

+33
-3
lines changed
  • src/connections/destinations/catalog/braze

1 file changed

+33
-3
lines changed

src/connections/destinations/catalog/braze/index.md

Lines changed: 33 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -137,8 +137,6 @@ Segment sends Page calls to Braze as custom events if you have enabled either **
137137
> info "Tip"
138138
> Add Segment's open-source [Middleware](https://github.com/segmentio/segment-braze-mobile-middleware) tool to optimize your integration. This tool limits [Data Point](https://www.braze.com/docs/user_guide/onboarding_with_braze/data_points/) use by debouncing duplicate identify() calls from Segment. For more information, see the project's [README](https://github.com/segmentio/segment-braze-mobile-middleware/blob/master/README.md#how-does-this-work).
139139

140-
141-
142140
If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like:
143141
144142
```js
@@ -151,10 +149,42 @@ analytics.identify('ze8rt1u89', {
151149
152150
When you Identify a user, Segment passes that user's information to Braze with `userId` as Braze's External User ID.
153151
154-
If you are using a device-mode connection, Braze's SDK also automatically assigns a `braze_id` to every user. This allows Braze to capture anonymous activity from the device by matching on `braze_id` instead of `userId`. This applies to _device-mode connections_.
152+
If you are using a device-mode connection, Braze's SDK assigns a `device_id` and a backend identifier, `braze_id`, to every user. This allows Braze to capture anonymous activity from the device by matching on those identifiers instead of `userId`. This applies to _device-mode connections_.
155153

156154
To send anonymous user data in cloud-mode, you must manually include the user's `braze_id` in all your Segment API calls in the `integrations.Braze.braze_id` or `context.integrations.Braze.braze_id` object.
157155
156+
### Capture the braze_id of anonymous users
157+
158+
Pass one of the many identifiers that may exist on an anonymous user profile to the [Braze's User by Identifier REST endpoint](https://www.braze.com/docs/api/endpoints/export/user_data/post_users_identifier/){:target='_blank'} to capture and export the `braze_id`. These identifiers include:
159+
- email address
160+
- phone number
161+
- device_id
162+
163+
Choose an identifier that is available on the user profile at that point in the user lifecycle.
164+
165+
For example, if you pass device_id to the User by Identifier endpoint:
166+
167+
```js
168+
{
169+
"device_id": “{{device_id}}",
170+
"fields_to_export": ["braze_id"]
171+
}
172+
```
173+
174+
The endpoint returns:
175+
176+
```js
177+
{
178+
"users": [
179+
{
180+
"braze_id": “{{braze_id}}"
181+
}
182+
],
183+
"message": "success"
184+
}
185+
```
186+
187+
158188
> info "Tip"
159189
> Braze is complex. If you decide to use the `braze_id`, consider [contacting Segment Success Engineering](https://segment.com/help/contact/) or a Solutions Architect to verify your Braze implementation.
160190

0 commit comments

Comments
 (0)