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] 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"%}