Skip to content

Commit 3ad94e6

Browse files
committed
stakeholder feedback [netlify-build]
1 parent e0e5522 commit 3ad94e6

File tree

3 files changed

+137
-115
lines changed

3 files changed

+137
-115
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 94 additions & 72 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,15 @@ redirect_from:
99
> info "Linked Audiences is in private beta"
1010
> Linked Audiences is in private beta, and Segment is actively working on this feature. Some functionality may change before it becomes generally available. [Contact Segment](https://segment.com/help/contact/){:target="_blank"} with any feedback or questions.
1111
12-
With Linked Audiences, you can use the relational data you've defined in your Data Graph to build audiences and send them to your downstream destinations.
12+
With Linked Audiences, you can use the relational data you've defined in your Data Graph to build audiences and send them to your downstream [actions-based destination](/docs/connections/destinations/actions/#available-actions-based-destinations).
1313

1414
From the relationships you've defined between the profiles and entities in your warehouse, you can filter on an entity, profile trait, and audience membership conditions to create hyper-segmented audiences.
1515

1616
> info "Linked Audiences warehouse support"
17-
> At this time, Linked Audiences only supports Snowflake.
17+
> At this time, Linked Audiences only supports [Snowflake](/docs/unify/linked-profiles/setup-guides/snowflake-setup/).
18+
19+
> info "Linked Audiences permissions requirements"
20+
> You must have Workspace Owner or Unify Read-Admin, Entities Admin, and Source Admin permissions to set up Linked Audiences Activation.
1821
1922
> success ""
2023
> Before you build Linked Audiences, be sure you've defined entities in your [Data Graph](/docs/unify/linked-profiles/data-graph/).
@@ -24,84 +27,52 @@ From the relationships you've defined between the profiles and entities in your
2427

2528
To help you get started with Linked Audiences, consider the following best practices:
2629

27-
1. It may be helpful to first identify an entity that is directly associated with your users, such as `Accounts`, `Households`, or `Organizations`.
28-
2. From there you can define relationships between this entity with any of the other entities that may be associated with it, such as how `Accounts` can have the following: `Subscriptions`, `Purchases`, or `Carts`.
29-
3. You can create entity relationships up to six levels in depth. For example, an entity condition that queries for relationships between `Profiles`, `Accounts`, `Credit Cards`, and `Transactions` has four levels of depth.
30-
4. To further refine your audience, identify column values that you might also want to filter your entities by, or configure profile trait and audience membership conditions.
31-
32-
## Use cases
33-
34-
Below are some example use cases to help you learn more about Linked Audiences.
35-
36-
### Build an audience of cat owners who are also a part of the platinum membership tier
30+
- It may be helpful to first identify an entity that is directly associated with your users, such as `Accounts`, `Households`, or `Organizations`.
31+
- From there you can define relationships between this entity with any of the other entities that may be associated with it, such as how `Accounts` can have the following: `Subscriptions`, `Purchases`, or `Carts`.
32+
- You can create entity relationships up to four levels in depth. For example, an entity condition that queries for relationships between `Profiles`, `Accounts`, `Credit Cards`, and `Transactions` has four levels of depth.
33+
- To further refine your audience, identify column values that you might want to filter your entities by, or configure profile traits and audience membership conditions.
3734

38-
Build an audience with `Households` and `Pets` where:
39-
- `pets.type` = "cat"
40-
41-
And where:
42-
- `profile.audience_membership` = "Platinum membership tier"
43-
44-
In the Data Graph, `Households` and `Pets` are defined as entities and are represented as separate tables in your data warehouse.
45-
46-
Relationships are defined between:
47-
- `Profiles` and `Households`
48-
- `Households` and `Pets`
49-
50-
In the warehouse, `pets.type` is a column in the `pets` table. By filtering against the `pets.type` column for the "cat" value, marketers can return a list of users that have a cat.
51-
52-
Furthermore, filtering the audience against `profile.audience_membership` for "Platinum membership tier" will allow marketers to further refine their audience to only include users who are also a part of the platinum membership tier audience.
53-
54-
### Build an audience of users with premium subscriptions who are located in Canada
35+
## Step 1: Build a Linked Audience
5536

56-
Build an audience with `Accounts` and `Subscriptions`, where the following are true:
57-
- `subscription.status` = "active"
58-
- `subscription.tier` = "premium"
37+
You can build a Linked Audience from profiles associated with an entity, trait, or existing Audience.
5938

60-
And where:
61-
- `profile.country` = "Canada"
39+
![Choose your audience conditions](/docs/engage/images/conditions.png)
6240

63-
In the Data Graph, `Accounts` and `Subscriptions` are defined as entities. Relationships are defined between:
64-
- `Profiles` and `Accounts`
65-
- `Accounts` and `Subscriptions`
41+
1. Navigate to **Engage > Audiences**.
42+
2. Click **+ New audience**, then select **Audience**.
43+
3. On the Select Type screen, select **Linked audience**, then click **Next**.
44+
4. Select one of the following conditions to build your audience from:
45+
- **associated with an entity**: creates a condition that filters profiles associated with an entity.
46+
- **where profile trait**: creates a condition that filters profiles with a specific trait.
47+
- **part of an audience**: creates a condition that filters profiles that are part of an existing audience.
48+
5. Preview your audience, then click **Next**.
49+
6. Enter an audience name and description, then click **Create Audience**.
6650

67-
In the warehouse, `subscription.status` is a column in the `subscriptions` table. Marketers can refine their audience by filtering against the `subscription.status` and `subscription.tier` columns to return a list of users that have an active subscription to their premium offering.
51+
After creating the audience, you'll be redirected to the Overview page. By default, the audience is disabled. You'll need to manually enable the audience for the audience to compute.
6852

69-
Furthermore, filtering the audience against `profile.country` for "Canada" will allow marketers to further refine their audience to only include users who are located in Canada.
53+
> warning ""
54+
> Edits and deletes are not currently supported for Linked Audiences. Segment recommends recreating your existing Linked Audience. To disable an audience, navigate to the **Settings** tab of an audience and toggle the **Enabled** button off.
7055
56+
#### Custom Traits
7157

72-
### Build an audience of credit card holders with a certain number of transactions
58+
You can build Linked Audiences based on custom traits. These traits can be collected from your apps when a user completes a form or signs up using an [Identify](/docs/connections/spec/identify) call. You can view these traits in the Profile explorer, as well. Custom Traits are mutable and update to the latest value seen by the user's Identify events.
7359

74-
Build an audience with `Accounts`, `Credit Cards`, and `Transactions` where the following are true:
75-
- `credit_cards.name` equals "Owly Card"
76-
- `transactions.count` is greater than five
60+
> info ""
61+
> When a Linked Audience that previously generated Identify events is deleted, the data for the audience key is still attached to profiles that entered the audience, and becomes visible in Segment as a custom trait.
7762
78-
In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities. Relationships are defined between:
79-
- `Profiles` and `Accounts`
80-
- `Accounts` and `Credit Cards`
81-
- `Credit Cards` and `Transactions`
8263

83-
In the warehouse:
84-
- `credit_cards.name` is a column in the `credit_cards` table
85-
- `transactions.count` is a column in the `transactions` table
64+
#### Compute statuses
8665

87-
Marketers can create hyper-targeted user segmentations filtering by column values or attributes, such as "Owly Card" and integers.
66+
Engage displays the following compute statuses for Linked Audiences.
8867

8968

90-
## Step 1: Build a Linked Audience
69+
| Computation status | Description |
70+
|---------------------------|---------------------------------------|
71+
| Computing | Engage is computing the Linked Audience. |
72+
| Live | The Linked Audience is live. Users will enter in real-time as they meet entry criteria. |
73+
| Disabled | The Linked Audience is disabled. |
74+
| Failed | The computation was cancelled or failed to compute. Please contact [Segment support](https://segment.com/help/contact/){:target="_blank"}. |
9175

92-
Use the Audience overview page to build or maintain a Linked Audiences.
93-
94-
1. Navigate to **Engage > Audiences**.
95-
2. Click **+ New audience**, then select **Audience**.
96-
3. On the Select Type screen, select **Linked audience**, then click **Next**.
97-
4. Build your Linked Audience with profiles by selecting **associated with an entity**, **where profile trait**, or **part of an audience** conditions.
98-
5. Preview your audience, then click **Next**.
99-
6. Enter an audience name and description, then click **Create Audience**.
100-
101-
After creating the audience, you'll be redirected to the Overview page. By default, the audience is disabled. You'll need to manually enable the audience for the audience to compute.
102-
103-
> warning ""
104-
> Linked Audiences can't be edited or deleted. Create a new audience to update conditions. To disable an audience, navigate to the **Settings** tab of an audience and toggle the **Enabled** button off.
10576

10677

10778
## Step 2: Activate your Linked Audience
@@ -154,7 +125,7 @@ Example use cases:
154125

155126
#### Audience entered
156127

157-
Send an event when a profile enters the audience.
128+
Send a Track event when a profile enters the audience.
158129

159130
Example use cases:
160131

@@ -163,7 +134,7 @@ Example use cases:
163134

164135
#### Audience exited
165136

166-
Send an event when the profile exits the audience.
137+
Send a Track event when the profile exits the audience.
167138

168139
Example use cases:
169140

@@ -172,15 +143,15 @@ Example use cases:
172143

173144
#### Audience Membership Changed
174145

175-
Send events when a profile enters and exits the audience.
146+
Send an Identify event when a profile enters and exits the audience.
176147

177148
Example use case:
178149
- Update a user profile in a destination with the most recent audience membership.
179150

180151

181152
### Step 2c: Select an action
182153

183-
Select the destination action to call when the event happens.
154+
Select the destination action to call when the event happens. Make sure the action you selected is relevant to the type of event you previously selected. For example, if you selected **Audience Membership Changed**, be sure your action is also an Identify event.
184155

185156
Segment displays available actions based on the destination action you've connected with your Linked Audience.
186157

@@ -195,7 +166,6 @@ To configure your event:
195166
1. Select additional properties to include in each event.
196167
- As you're configuring your event, you can view a preview of the enriched event based on your property selections.
197168
2. Map your event from your audience to your destination.
198-
- You can preview what the event will look like in your destination.
199169
- [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) are pre-set destinations, so you won't need to map your audience to your destination.
200170
3. Select if you'd like to [send events for current profiles and entities in the audience](#send-events-for-current-profiles-and-entities-in-the-audience).
201171
- This is only available for the **entity added**, **audience entered**, and **audience membership changed** event types.
@@ -204,8 +174,6 @@ To configure your event:
204174

205175
#### Send events for current profiles and entities in the audience
206176

207-
Select if you'd like to sync existing profiles and entities in the audience with the **Send events for current profiles and entities in audience** checkbox.
208-
209177
This box is unchecked by default. If you leave this box unchecked, Segment only sends events for new profiles and entities that match the audience conditions.
210178

211179
However, if you select this checkbox, Segment will also send events for profiles and entities that currently match the audience description.
@@ -219,4 +187,58 @@ To confirm your destination is receiving events, Segment recommends that you log
219187
- Search for the `UserID` or `Event Name` (for example, `Entity Added`)
220188

221189

190+
## Use cases
191+
192+
Below are some example use cases to help you learn more about Linked Audiences.
193+
194+
### Build an audience of cat owners who are also a part of the platinum membership tier
195+
196+
Build an audience with `Households` and `Pets` where:
197+
- `pets.type` = "cat"
198+
199+
And where:
200+
- The user is a member of the "Platinum membership tier" audience
201+
202+
In the Data Graph, `Households` and `Pets` are defined as entities and are represented as separate tables in your data warehouse.
203+
204+
Relationships are defined between:
205+
- `Profiles` and `Households`
206+
- `Households` and `Pets`
207+
208+
In the warehouse, `pets.type` is a column in the `pets` table. By filtering against the `pets.type` column for the "cat" value, marketers can return a list of users that have a cat.
209+
210+
Furthermore, adding the audience membership condition will allow marketers to further refine their audience to only include users who are also a part of the platinum membership tier audience.
211+
212+
### Build an audience of users with premium subscriptions who are located in Canada
213+
214+
Build an audience with `Accounts` and `Subscriptions`, where the following are true:
215+
- `subscription.status` = "active"
216+
- `subscription.tier` = "premium"
217+
218+
And where the user is from Canada.
219+
220+
In the Data Graph, `Accounts` and `Subscriptions` are defined as entities. Relationships are defined between:
221+
- `Profiles` and `Accounts`
222+
- `Accounts` and `Subscriptions`
223+
224+
In the warehouse, `subscription.status` is a column in the `subscriptions` table. Marketers can refine their audience by filtering against the `subscription.status` and `subscription.tier` columns to return a list of users that have an active subscription to their premium offering.
225+
226+
Furthermore, adding the profile condition will allow marketers to further refine their audience to only include users who are located in Canada.
227+
228+
229+
### Build an audience of credit card holders with a certain number of transactions
230+
231+
Build an audience with `Accounts`, `Credit Cards`, and `Transactions` where the following are true:
232+
- `credit_cards.name` equals "Owly Card"
233+
- `transactions.count` is greater than five
234+
235+
In the Data Graph, `Accounts`, `Credit Cards`, and `Transactions` are defined as entities. Relationships are defined between:
236+
- `Profiles` and `Accounts`
237+
- `Accounts` and `Credit Cards`
238+
- `Credit Cards` and `Transactions`
239+
240+
In the warehouse:
241+
- `credit_cards.name` is a column in the `credit_cards` table
242+
- `transactions.count` is a column in the `transactions` table
222243

244+
Marketers can create hyper-targeted user segmentations filtering by column values or attributes, such as "Owly Card" and integers.

src/engage/images/conditions.png

15.3 KB
Loading

0 commit comments

Comments
 (0)