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/engage/audiences/linked-audiences.md
+75-13Lines changed: 75 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,24 +69,86 @@ As you're building your Linked Audience, you can choose from the following profi
69
69
| part of an [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are part of an existing audience. |
70
70
| not part of an [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are not part of an existing |
71
71
| that performed [event](/docs/glossary/#event)| Creates a condition that filters profiles that have a specific event in their event history. You can also filter on event property values.|
72
-
| that did not performed [event](/docs/glossary/#event)| Creates a condition that filters profiles that do not have a specific event in their event history. You can also filter on event property values.|
72
+
| that did not performed [event](/docs/glossary/#event)| Creates a condition that filters profiles that do not have a specific event in the event history. You can also filter on event property values.|
73
73
74
74
**Note:** you can only create nested entity conditions 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.
|Overview Page |View relevant compute information on the Overview Page (profiles in audience, run schedule, latest run status, next compute).
81
-
|Edit / Delete Audience | - Users can delete their rETL audience from the Overview page. Users can edit and save their previously created rETL audience on the Builder tab of the Overview page. If you edit an audience with configured activation events, you may need to disable or delete impacted events in order for your audience to successfully compute. Events are impacted if they reference entities that are edited and removed from the audience definition. |
82
-
|Operator Selection |Users can create audience definitions using either AND or OR operators across all condition levels. Users can switch between these operators when filtering on multiple entity or event properties, between conditions within a condition group, and between condition groups. Example: |
83
-
|Event Conditions | - at least \> supports 1 or greater, exactly > supports 0 or greater, at most > supports 0 or greater, does not support funnel audiences, unlike classic audiences, Users can’t select enrich their event payloads with event properties.
84
-
|Entity Conditions | - at least \> only supports 1 or greater, exactly > supports 0 or greater, at most > supports 0 or greater, when filtering by 0, you can’t filter on by entity properties or on additional nested entities.
85
-
|Negative Audiences | Negation of an entire entity group condition will not support activation and enrichment on the entities within that condition group. When a condition such as “Select all users associated with an entity with exactly 0 instances” is used: We will not allow any entity property filters to be applied to this condition group. We will not allow any more nested entities to be specified in this condition group |
86
-
|Entity Explorer | - If users have defined entity conditions in their audience definition, then they will see a “Matched Entities” tab in the audience preview in the creation flow that will help them understand what entities qualified that user to be a part of the audience when they preview the audience. This contextual information should appear when a user clicks into the user profile generated from the audience preview when configuring audiences. The contextual information a user sees in the Preview UI encompasses entity relationships as well as entity column values that were used as filtering criteria in the audience definition. We’re truncating the data that is being returned to us from Compute - 10 entities at each level, 6 levels of depth. By default, users will be opted-in and will see entity preview values through a flag (for Hybrid Spaces). If the customer wants to opt out of this functionality, then they will need to request the flag to be turned off.
87
-
|Dynamic References |Event Conditions - For event property values, users can either enter a Constant or dynamically reference a profile trait from the Segment profile. - When filtering on event properties, users can dynamically reference the value of another profile trait, or enter a constant value. Entity Conditions - When filtering on entity properties, users can dynamically reference the value of another entity column (from the same branch at the same level or above it) or profile trait, or enter a constant value. |
88
-
|Limits | Auto-populate Dropdown Entity Property Values - You can select property values from a drop-down so they don’t need to type in the exact value they want to filter their condition on. - By default, users will be opted-in and will see entity preview values through a flag (for Hybrid Spaces). If the customer wants to opt out of this functionality, then they will need to request the flag to be turned off. |
89
-
|Duplicate Conditions & Clone Audiences| - Users can duplicate their conditions in the audience builder in the same condition group. - Users can clone a rETL audience to the same Space from the List and Overview pages. - Cloning a linked audience will create a new linked audience in the builder create flow with the same conditions as the linked audience that was cloned. |
78
+
The Audience builder returns the portion of values from the data warehouse or incoming data stream that are the most commonly used, including some entity and event properties. However, if you don’t see the value you’re looking for, you can manually enter it.
79
+
80
+
Segment sources profile trait and event keys surfaced in the linked audience builder from the data warehouse and not from the Segment profile. This means that the data you want to reference has to be synced to the data warehouse through Profiles Sync before you can reference it in the linked audience builder, even if it already exists on the Segment profile.
81
+
82
+
#### Overview
83
+
84
+
You can view relevant audience information on the Overview page (Profiles in Audience, Run Schedule, Latest run, Next compute).
85
+
86
+
#### Edit/Delete Audience
87
+
88
+
You can delete your Linked Audience from the Overview page.
89
+
You can edit and save your previously created rETL audience on the Builder tab of the Overview page.
90
+
91
+
If you edit an audience with configured activation events, you may need to disable or delete impacted events for your audience to successfully compute. Events are impacted if they reference entities that are edited and removed from the audience definition.
92
+
93
+
#### Operator Selection
94
+
95
+
You can create audience definitions using either `AND` or `OR` operators across all condition levels. You can switch between these operators when filtering on multiple entity or event properties, between conditions within a condition group, and between condition groups.
96
+
97
+
**Example:**
98
+
99
+
100
+
101
+
#### Event Conditions
102
+
103
+
-*at least*: supports 1 or greater.
104
+
-*exactly*: supports 0 or greater.
105
+
-*at most*: supports 0 or greater.
106
+
- does not support funnel audiences, unlike classic audiences.
107
+
- can’t select enrich event payloads with event properties.
108
+
109
+
#### Entity Conditions
110
+
111
+
-*at least*: only supports 1 or greater
112
+
-*exactly*: supports 0 or greater
113
+
-*at most*: supports 0 or greater
114
+
- When filtering by 0, you can’t filter by entity properties or by additional nested entities.
115
+
116
+
#### Negative Audiences
117
+
118
+
Negation of an entire entity group condition will not support activation and enrichment on the entities within that condition group. When a condition such as “Select all users associated with an entity with exactly 0 instances” is used:
119
+
120
+
- Segment won't allow any entity property filters to be applied to this condition group.
121
+
- Segment won't allow any more nested entities to be specified in this condition group.
122
+
123
+
#### Entity Explorer
124
+
125
+
If you have defined entity conditions in your audience definition, then you see a “Matched Entities” tab in the audience preview that helps define what entities qualified that user to be a part of the audience.
126
+
127
+
This information appears when you click the user profile generated from the audience preview. The information encompasses entity relationships as well as entity column values that were used as filtering criteria in the audience definition. The data being returned is truncated - 10 entities at each level, 6 levels of depth. By default, you are opted-in to see entity preview values.
128
+
129
+
130
+
131
+
#### Dynamic References
132
+
133
+
**Event Conditions**
134
+
135
+
For event property values, you can either enter a Constant or dynamically reference a profile trait from the Segment profile.
136
+
When filtering on event properties, you can dynamically reference the value of another profile trait, or enter a constant value.
137
+
138
+
**Entity Conditions**
139
+
140
+
When filtering on entity properties, you can dynamically reference the value of another entity column (from the same branch at the same level or above it) or profile trait, or enter a constant value.
141
+
142
+
#### Limits
143
+
144
+
**Auto-populate Dropdown Entity Property Values**
145
+
146
+
You can select property values from a drop-down. By default, you are opted-in to see entity preview values.
147
+
148
+
#### Duplicate Conditions & Clone Audiences
149
+
150
+
You can duplicate your conditions in the audience builder in the same condition group.
151
+
You can clone a rETL audience to the same Space from the List and Overview pages. Cloning a linked audience will create a new linked audience in the builder create flow with the same conditions as the linked audience that was cloned.
0 commit comments