Skip to content

Commit 3a7a8b2

Browse files
authored
clarifying mappings link
1 parent 3fc3830 commit 3a7a8b2

File tree

1 file changed

+1
-1
lines changed
  • src/connections/destinations/catalog/actions-braze-web

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ Braze web-mode (Actions) provides the following benefits over Braze (Classic):
3030
> warning "Mapping settings"
3131
> Some events require specific property names to map correctly into Braze.
3232
> For example, purchase events must use a `products` array with `product_id` and `price.
33-
> See [Braze-web settings mappings](#braze-web-settings-mapping) for the full list of requirements before setting up mappings.
33+
> See [Braze-web settings mappings](#braze-web-settings-mapping) for "Device-web" for the full list of requirements before setting up mappings.
3434
4. In the **Settings** tab, configure the connection settings. **API Key**, **SDK Endpoint**, and **REST Endpoint** are required settings.
3535

3636
After setting up your Braze web-mode (Action) destination in the Segment app, Segment's Analytics.js library starts asynchronously loading the Braze SDK on your page and sending data. Data appears in the Segment CDN in about 45 minutes.

0 commit comments

Comments
 (0)