Skip to content

Commit c1faa7b

Browse files
Merge pull request #6476 from segmentio/ashton-huxtable-patch-5
Update to reflect support of email as identifier
2 parents e46a36d + c94904f commit c1faa7b

File tree

1 file changed

+2
-2
lines changed
  • src/connections/destinations/catalog/actions-braze-cloud

1 file changed

+2
-2
lines changed

src/connections/destinations/catalog/actions-braze-cloud/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
3232
- **REST Endpoint**: Your Braze REST Endpoint. For more information, see [API Overview](https://www.braze.com/docs/api/basics/){:target="_blank"} in the Braze documentation.
3333

3434
> info ""
35-
> Braze requires that you include a `userId` or `braze_id` for all calls made in cloud-mode. Segment sends a `braze_id` if the `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.
35+
> Braze now supports sending `email` as an identifier. Braze requires that you include `userId`, `braze_id`, or `email` for all calls made in cloud-mode. Segment sends a `braze_id` if the `userId` is missing. When you use a device-mode connection, Braze automatically tracks anonymous activity using the `braze_id` if a `userId` is missing.
3636
3737
> info "V2 Actions"
3838
> The V2 versions of each action include improved sync mode support. Only valid sync modes for each action are available. As a result, the `_update_existing_only` parameter is tied to the sync mode you select for the mapping. If you select the `update` sync mode, Segment passes `_update_existing_only: true` to Braze, and if you choose the `add` sync mode, Segment passes `_update_existing_only: false` to Braze.
@@ -50,4 +50,4 @@ Keep the following in mind if you plan to move to Braze (Actions) from the class
5050
Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be present in all events sent. If events are failing to send, please check your event mappings to make sure these fields are resolving to valid values.
5151

5252
### Missing events
53-
When an event is sent under an alias, the event may seem to be missing when the alias cannot be found in Braze. This may be due to incorrect search for the alias in Braze. To search for an alias in Braze, use the format "Alias Label:Alias Name". For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address (for example: "[email protected]"), use "email:test@email.com" to search for the alias in Braze.
53+
When an event is sent under an alias, the event may seem to be missing when the alias cannot be found in Braze. This may be due to incorrect search for the alias in Braze. To search for an alias in Braze, use the format "Alias Label:Alias Name". For example, if the "Alias Label" field is set as email and "Alias Name" field is set as email address (for example: "[email protected]"), use "email:test@email.com" to search for the alias in Braze.

0 commit comments

Comments
 (0)