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
| associated with an entity | Creates a condition that filters profiles associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/). With this condition, you can navigate the full nested entity relationship and filter your audience on entity column values.
66
-
| not associated with an entity | Creates a condition that filters profiles that are not associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/).
67
-
| with [profile trait](/docs/unify/#enrich-profiles-with-traits)| Creates a condition that filters profiles with a specific trait. |
68
-
| without [profile trait](/docs/unify/#enrich-profiles-with-traits)| Creates a condition that filters profiles without a specific trait. |
69
-
| part of an [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are part of an existing audience. |
70
-
| not part of an [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are not part of an existing |
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 the event history. You can also filter on event property values.|
61
+
After creating your Linked Audience, you will be brought to the Overview page with the Linked Audience in a disabled state. It will not be running against your data warehouse and no events are being sent to destinations.
73
62
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.
63
+
On the Overview page, can view relevant audience information, such as Profiles in Audience, Run Schedule, Latest run, Next compute. You can edit or delete your Linked Audience.
75
64
76
-
### Linked Audience advanced profiles conditions
65
+
If you edit an audience with configured activation events, should 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.
77
66
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.
67
+
You can also clone your linked audience to the same space from the List and Overview pages. Cloning a linked audience creates a new linked audience in the builder create flow with the same conditions as the linked audience that was cloned.
79
68
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.
69
+
### Linked Audience conditions
81
70
82
-
#### Overview
71
+
The linked audiences builder sources profile trait and event keys from the data warehouse. This data must be synced to the data warehouse (through Profiles Sync) before you can reference it in the linked audience builder. If there is a profile trait that exists in the Segment Profile but hasn’t successfully synced to the data warehouse yet, it will be grayed out so that it can’t be selected.
83
72
84
-
You can view relevant audience information on the Overview page (Profiles in Audience, Run Schedule, Latest run, Next compute).
73
+
If you don’t see the value you’re looking for, you can manually enter it into the input field. Segment displays
74
+
the first 100 unique string entity property values from the data warehouse
75
+
If you want to opt out of displaying entity property values from the data warehouse, please contact Support.
76
+
the top 65 event property and context key values
77
+
the top 65 profile trait key values
85
78
86
-
#### Edit/Delete Audience
79
+
The linked audience builder also returns a subset of available entity property key values, event property and context key values, and profile trait key values that you can select in the input field drop-down so that you don’t need to type in the exact value that you want to filter on.
87
80
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.
81
+
You can only create nested entity conditions 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.
90
82
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.
83
+
As you're building your Linked Audience, you can choose from the following profiles conditions:
| with entity | Creates a condition that filters profiles associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/). With this condition, you can navigate the full, nested entity relationships, and filter your audience on entity column values.
94
88
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.
89
+
The event condition type supports these configurations:
90
+
at least: supports 1 or greater
91
+
exactly: supports 0 or greater*
92
+
at most: supports 0 or greater*
96
93
97
-
**Example:**
94
+
* When filtering by 0, you can’t filter on by entity properties or on additional nested entities.
98
95
99
-
96
+
| without entity | Creates a condition that filters profiles that are not associated with entity relationships defined in the [Data Graph](/docs/unify/linked-profiles/data-graph/).
97
+
| with [ trait](/docs/unify/#enrich-profiles-with-traits)| Creates a condition that filters profiles with a specific trait. |
98
+
| without [ trait](/docs/unify/#enrich-profiles-with-traits)| Creates a condition that filters profiles without a specific trait. |
99
+
| part of [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are part of an existing audience. |
100
+
| not part of [audience](/docs/glossary/#audience)| Creates a condition that filters profiles that are not part of an existing audience. |
101
+
| with [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.
100
102
101
-
#### Event Conditions
103
+
The event condition type supports these configurations:
104
+
at least: supports 1 or greater
105
+
exactly: supports 0 or greater
106
+
at most: supports 0 or greater
102
107
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
+
| without [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.|
108
109
109
-
#### Entity Conditions
110
+
You can also duplicate your conditions in the audience builder into the same condition group.
110
111
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.
112
+
#### Operator Selection
115
113
116
-
#### Negative Audiences
114
+
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.
117
115
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:
116
+
**Example:**
119
117
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.
118
+
122
119
123
120
#### Entity Explorer
124
121
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.
122
+
If you have defined entity conditions in your audience definition, then you will see a “Matched Entities” tab in the audience preview that helps define what entities qualified that user to be a part of the audience.
123
+
124
+
This information appears when you click the user profile generated from the audience preview. The contextual information encompasses entity relationships as well as entity column values that were used as filtering criteria in the audience definition. By default, we include the entity ID.The data being returned is truncated - 10 entities at each level, 6 levels of depth. If you want to opt out of this functionality, contact Support.
126
125
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
126
129
127
130
128
131
-
#### Dynamic references
129
+
#### Dynamic References
132
130
133
131
**Event Conditions**
134
132
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.
133
+
When filtering on event properties, you can dynamically reference the value of another profile trait, or enter a constant value. These operators support dynamic references:
134
+
equals, not equals, less than, greater than, less than or equal, greater than or equal, contains, does not contain, starts with, ends with.
137
135
138
136
**Entity Conditions**
139
137
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 and 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.
138
+
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),profile trait, or enter a constant value.
139
+
You can only dynamically reference properties of the same data type. Dynamic references are only supported for certain operators depending on the data type:
140
+
NUMBER data type: equals, not equals, less than, greater than, less than or equal, greater than or equal
141
+
STRING data type: equals, not equals, contains, does not contain, starts with, ends with
142
+
TIMESTAMP data type: equals, not equals, less than, greater than, less than or equal, greater than or equal
0 commit comments