Skip to content

Commit 890b9a9

Browse files
committed
Audience activation PM feedback
1 parent 06e8886 commit 890b9a9

File tree

2 files changed

+23
-23
lines changed

2 files changed

+23
-23
lines changed

src/unify/linked-profiles/data-graph.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -132,6 +132,7 @@ Use the following relationship, parameters, and examples to help you relate enti
132132
> warning ""
133133
> Snowflake schemas are case sensitive, so you'll need to reflect the schema, table, and column names based on how you case them in Snowflake.
134134
135+
135136
#### Relate Entity to Profile
136137

137138
| Parameters | Definition |

src/unify/linked-profiles/linked-audiences.md

Lines changed: 22 additions & 23 deletions
Original file line numberDiff line numberDiff line change
@@ -90,37 +90,38 @@ Use the Audience overview page to build or maintain a Linked Audiences.
9090

9191
## Step 2: Activate your Linked Audience
9292

93-
Use the Audience overview page to build or maintain Linked Audiences.
93+
You can use your Linked Audience to activate any [actions-based destination](/docs/connections/destinations/actions/#available-actions-based-destinations). The steps below provide instructions on how to add a destination to your Linked Audience(s), and send an event that best matches your use case.
9494

9595
> info ""
96-
> Note that [Braze](/docs/connections/destinations/catalog/braze-cloud-mode-actions/#available-presets), [Iterable](/docs/connections/destinations/catalog/actions-iterable/#available-presets), and [Customer.io](/docs/connections/destinations/catalog/customer-io-actions/#available-presets) all have preset mappings with many of the following steps already configured.
96+
> Segment has preset mappings for [Braze](/docs/connections/destinations/catalog/braze-cloud-mode-actions/#available-presets), [Iterable](/docs/connections/destinations/catalog/actions-iterable/#available-presets), and [Customer.io](/docs/connections/destinations/catalog/customer-io-actions/#available-presets) with many of the following steps already configured.
9797
98-
### Step 2a: Add an actions destination
98+
> warning ""
99+
> Some action destinations have limitations on nested objects, and the depth of the `_entity_context` property.
100+
101+
### Step 2a: Add an action destination
99102

100-
To activate your Linked Audience, you'll first need to add an actions destination.
103+
To activate your Linked Audience, you'll first need to add an action destination.
101104

102105
From the Add destination window, select your destination and click **Next**.
103106

104107
### Step 2b: Select event
105-
After adding an actions destination, select what type of event you want to send to the destination. Events update the destination about changes to your entity or audiences.
108+
After adding an actions destination, select what type of event you want to send to the destination. Events update the destination about changes to your entity or audiences. You can then use these actions to orchestrate campaigns in other tools.
106109

107110
You can send events:
108111
- When an entity on a profile changes:
109112
- [Entity Added](#entity-added)
110113
- [Entity Removed](#entity-removed)
111114
- Based on profile audience membership updates:
112115
- [Audience Entered](#audience-entered)
113-
- [Audience Entered and Exited](#audience-entered-and-exited)
116+
- [Audience Membership Changed](#audience-membership-changed)
114117
- [Audience Exited](#audience-exited)
115118

116119
> info ""
117120
> Note that you can't send events before you identify people. Ensure you're making the profile(s) known in the destination before you send events. You can do this by sending an `Audience Membership Changed` event first, or by creating an Identify event in Connections.
118121
119122
#### Entity added
120123

121-
Send an action to a destination when an entity associated with a profile matches the audience condition. Select your entity from the **Select entity** dropdown menu.
122-
123-
Use this action to orchestrate campaigns in other tools.
124+
Send a Track event when an entity matching the audience conditions is added. Select your entity from the **Select entity** dropdown menu.
124125

125126
Example use cases:
126127
- Send a reminder to a customer when a credit card associated with their profile has an outstanding balance.
@@ -129,45 +130,43 @@ Example use cases:
129130

130131
#### Entity removed
131132

132-
Send an event to a destination when an entity assoacited with the profile no longer matches the audience condition. Select your entity from the **Select entity** dropdown menu.
133-
134-
Use this action to orchestrate campaigns in other tools.
133+
Send a Track event when an entity is removed because it no longer matches the audience conditions. Select your entity from the **Select entity** dropdown menu.
135134

136135
Example use cases:
137136
- Send a confirmation to a customer when a credit card associated with their profile has been paid off.
138137
- Send a confirmation to the primary doctor when each of their associated patients completes their annual check up.
139138

140139
#### Audience entered
141140

142-
Send a Track event to a destination when a profile matches the audience condition. Use these events to orchestrate campaigns in other tools.
141+
Send an event when a profile enters the audience.
143142

144143
Example use cases:
145144

146145
- Send a congratulatory email when a travel qualifies for premium status.
147146
- Send a discount to all customers with a particular product on their wishlist.
148147

149-
#### Audience entered and exited
150-
151-
Send an Identify event when a profile enters or exits the audience.
152-
153-
Example use case:
154-
- Update a user profile in a destination with the most recent audience membership.
155-
156148
#### Audience exited
157149

158-
Send a Track event to a destination when a profile no longer matches the audience condition. Use these events to orchestrate campaigns in other tools.
150+
Send an event when the profile exits the audience.
159151

160152
Example use cases:
161153

162154
- Send an email to credit card owners to confirm that their credit cards have been paid in full.
163155
- Send a confirmation to a patient when they have completed all their pre-screening forms.
164156

157+
#### Audience Membership Changed
158+
159+
Send events when a profile enters and exits the audience.
160+
161+
Example use case:
162+
- Update a user profile in a destination with the most recent audience membership.
163+
165164

166165
### Step 2c: Select an action
167166

168167
Next, you'll select the destination action to call when the event happens.
169168

170-
Segement displays available actions based on the destination action you've connected with your Linked Audience.
169+
Segment displays available actions based on the destination action you've connected with your Linked Audience.
171170

172171
Visit the [destination actions docs](/docs/connections/destinations/actions/) learn more about destination actions, and view available actions for your destination.
173172

@@ -181,7 +180,7 @@ To configure your event:
181180
- As you're configuring your event, you can view a preview of the enriched event based on your property selections.
182181
2. Map your event from your audience to your destination.
183182
- You can preview what the event will look like in your destination.
184-
3. After configuring, click **Save** or **Save and enable** to enable your Linked Audience.
183+
3. After configuring, click **Save** to enable your Linked Audience.
185184

186185
After saving, you'll be redirected to a destination sidesheet where you can view all events and their corresponding actions.
187186

0 commit comments

Comments
 (0)