From 2e6d71fa430439ba815c20014f005b7506ac8aef Mon Sep 17 00:00:00 2001 From: Nick Aguilar Date: Mon, 23 Sep 2024 15:35:35 -0700 Subject: [PATCH 1/3] Adds info about Braze V2 actions --- .../destinations/catalog/actions-braze-cloud/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md index e9cf33ac82..22f1f4f179 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -34,6 +34,11 @@ 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 V2 versions of each action include improved sync mode support. Only valid sync modes for each action will be available. Because of this the `_update_existing_only` parameter is now tied to the sync mode you select for the mapping. If you select the `update` sync mode, we will always pass `_update_existing_only: true` to Braze, and if you choose the `add` sync mode, we will always pass `_update_existing_only: false` to Braze. + +{% include content/connection-modes.md %} + {% include components/actions-fields.html settings="true"%} ## Migration from Braze Classic From 61dd32e5392e8b4e67849983cfdbf5e26e35036e Mon Sep 17 00:00:00 2001 From: Nick Aguilar Date: Mon, 23 Sep 2024 15:39:04 -0700 Subject: [PATCH 2/3] Removes unneeded git diff --- .../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 22f1f4f179..88cb03fe55 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -37,8 +37,6 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic: > info "V2 Actions" > The V2 versions of each action include improved sync mode support. Only valid sync modes for each action will be available. Because of this the `_update_existing_only` parameter is now tied to the sync mode you select for the mapping. If you select the `update` sync mode, we will always pass `_update_existing_only: true` to Braze, and if you choose the `add` sync mode, we will always pass `_update_existing_only: false` to Braze. -{% include content/connection-modes.md %} - {% include components/actions-fields.html settings="true"%} ## Migration from Braze Classic From 124bf5ae855cfd76dd212fed4593d8054f53cce1 Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Tue, 24 Sep 2024 12:55:27 -0500 Subject: [PATCH 3/3] minor rewording --- .../destinations/catalog/actions-braze-cloud/index.md | 2 +- 1 file changed, 1 insertion(+), 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 88cb03fe55..bceaa1e650 100644 --- a/src/connections/destinations/catalog/actions-braze-cloud/index.md +++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md @@ -35,7 +35,7 @@ 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 will be available. Because of this the `_update_existing_only` parameter is now tied to the sync mode you select for the mapping. If you select the `update` sync mode, we will always pass `_update_existing_only: true` to Braze, and if you choose the `add` sync mode, we will always pass `_update_existing_only: false` to Braze. +> 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. {% include components/actions-fields.html settings="true"%}