Skip to content

Commit bf79dcb

Browse files
authored
add section on device id
1 parent e198149 commit bf79dcb

File tree

1 file changed

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

1 file changed

+8
-1
lines changed

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

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,4 +60,11 @@ Event payloads sent via Computed Traits and Audiences will only contain the comp
6060

6161
When dealing with event payloads transmitted through Computed Traits and Audiences, it's important to note that these payloads typically include only the specific computed trait or audience key in question in addition to user identities such as `userId` and `anonymousId`, as well as `email` if available, [for more information, see here](/docs/engage/using-engage-data/#event-destinations).
6262

63-
If your requirements involve including additional fields from user profiles into your mappings, you can achieve this by leveraging an [Insert Function](/docs/connections/functions/insert-functions/) in conjunction with the [Engage Profile API](docs/unify/profile-api/). With the Profile API, you can retrieve the traits associated with a user from your Engage space within your insert function code, all before the event reaches the Braze Cohorts destination.
63+
If your requirements involve including additional fields from user profiles into your mappings, you can achieve this by leveraging an [Insert Function](/docs/connections/functions/insert-functions/) in conjunction with the [Engage Profile API](docs/unify/profile-api/). With the Profile API, you can retrieve the traits associated with a user from your Engage space within your insert function code, all before the event reaches the Braze Cohorts destination.
64+
65+
### Braze Device ID
66+
67+
If you would like to use the `Device ID` mapping for the Cohort Destination you will need to ensure you have captured the Braze device_id which is not the same as the Segment device_id. Braze has some methods (linked below) that customers can use to capture the Braze device_id for use in the above workaround:
68+
- [Swift method](https://braze-inc.github.io/braze-swift-sdk/documentation/brazekit/braze/deviceid/)
69+
- [Android method](https://braze-inc.github.io/braze-android-sdk/kdoc/braze-android-sdk/com.braze/-i-braze/device-id.html)
70+
- [Web method](https://js.appboycdn.com/web-sdk/latest/doc/modules/braze.html#getdeviceid)

0 commit comments

Comments
 (0)