From 28b0e13125397f67224957178ce3a9c194f207c2 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Mon, 30 Sep 2024 17:07:50 -0400 Subject: [PATCH 1/4] braze v2 --- .../catalog/actions-braze-cloud/index.md | 21 ++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index bceaa1e650..11e761334f 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -35,7 +35,26 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: > 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. > info "V2 Actions" -> 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. +> 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. + +## Actions v2 + +Segment’s v2 Actions, [Custom Object v2](#custom-object-v2) and [Custom Event v2](#custom-event-v2), support the following features: + +- **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data. +- **Dynamic dropdowns**: When creating or updating a mapping in the Segment app, the dropdown auto-populates all of the available properties directly from Braze. +- **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app. + +> warning "" +> You might need to reauthorize your Braze account to use all of the features associated with v2 Actions. + +### Sync modes + +Sync modes allow users to define how Segment should update the data in your destination. + +Sync modes available for v2 Actions include: +- **Upsert**: Update existing records and add new ones, if necessary. +- **Add**: Add records to a list, segment, or journey. {% include components/actions-fields.html settings="true"%} From fea83aca10fd85e4d617ba91db8c6c9277da3efe Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 1 Oct 2024 13:08:59 -0400 Subject: [PATCH 2/4] rm note --- .../destinations/catalog/actions-braze-cloud/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index 11e761334f..7e31cd88aa 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -34,8 +34,6 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: > info "" > 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. -> info "V2 Actions" -> 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. ## Actions v2 From e38788f1198daa32fb8ccf39ef9745efedd05ee4 Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 1 Oct 2024 15:58:05 -0400 Subject: [PATCH 3/4] [netlify-build] --- .../destinations/catalog/actions-braze-cloud/index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index 7e31cd88aa..9d47649438 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -68,3 +68,4 @@ Braze requires one of either `external_id`, `user_alias`, or `braze_id` to be pr ### Missing events 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: "test@email.com"), use "email:test@email.com" to search for the alias in Braze. + From 65077a624aaaacb0477aad277034b777d85723cc Mon Sep 17 00:00:00 2001 From: forstisabella <92472883+forstisabella@users.noreply.github.com> Date: Tue, 1 Oct 2024 20:24:19 -0400 Subject: [PATCH 4/4] [netlify-build] --- .../destinations/catalog/actions-braze-cloud/index.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index 8701774435..0db913dff1 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -37,8 +37,14 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: ## Actions v2 -Segment’s v2 Actions, [Custom Object v2](#custom-object-v2) and [Custom Event v2](#custom-event-v2), support the following features: - +Segment’s introduced the following v2 Actions to add additional functionality to the Braze Cloud Mode (Actions) destination: +- [Update User Profile v2](#update-user-profile-v2) +- [Track Event v2](#track-event-v2) +- [Identify User v2](#identify-user-v2) +- [Create Alias v2](#create-alias-v2) +- [Track Purchase v2](#track-purchase-v2) + +These Actions support the following features: - **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data. - **Dynamic dropdowns**: When creating or updating a mapping in the Segment app, the dropdown auto-populates all of the available properties directly from Braze. - **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app.