diff --git a/src/connections/destinations/catalog/actions-braze-cloud/index.md b/src/connections/destinations/catalog/actions-braze-cloud/index.md
index fae5ae3012..0db913dff1 100644
--- a/src/connections/destinations/catalog/actions-braze-cloud/index.md
+++ b/src/connections/destinations/catalog/actions-braze-cloud/index.md
@@ -34,8 +34,31 @@ Braze Cloud Mode (Actions) provides the following benefit over Braze Classic:
 > info ""
 > 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.
 
-> 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.
+
+## Actions v2
+
+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.
+
+> 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"%}
 
@@ -50,4 +73,4 @@ Keep the following in mind if you plan to move to Braze (Actions) from the class
 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.
 
 ### 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.
\ No newline at end of file
+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.