You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/actions-braze-cohorts/index.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,3 +53,18 @@ If you are creating multiple mappings in one Braze Cohorts destination, Segment
53
53
>A user can only be added to a cohort if the user already exists in Braze. This means that the Braze Cohorts destination should be used in parallel with the[Braze Cloud Mode (Actions) destination](/docs/connections/destinations/catalog/braze-cloud-mode-actions/) or the[Braze Web Mode (Actions) destination](/docs/connections/destinations/catalog/braze-web-device-mode-actions/), both of which can create users in Braze.
54
54
55
55
{% include components/actions-fields.html settings="true"%}
56
+
57
+
###Supplementing audience payloads
58
+
59
+
Event payloads sent using Computed Traits and Audiences will only contain the computed trait or audience key in question, in addition to the user identities`userId`,`anonymousId` and`email`. If you need supplemental fields from user profiles to map to Braze, consider using an Insert Function with the Engage Profile API. Using the Profile API, you can pull a user's traits from your Engage space within your insert function code before the event hits the destination. You can then use these traits to enrich the event payload sent to the destination.
60
+
61
+
When dealing with event payloads transmitted through Computed Traits and Audiences, keep in mind 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. View[event destinations](/docs/engage/using-engage-data/#event-destinations) for more information.
62
+
63
+
If you need to include additional fields from user profiles into your mappings, you can achieve this by using an[insert function](/docs/connections/functions/insert-functions/) 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: