Skip to content

Commit 2f5f0c0

Browse files
cmastrcmastr
committed
LA advanced conditions
1 parent df3a791 commit 2f5f0c0

File tree

1 file changed

+21
-7
lines changed

1 file changed

+21
-7
lines changed

‎src/engage/audiences/linked-audiences.md

Lines changed: 21 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,22 @@ As you're building your Linked Audience, you can choose from the following profi
7171
| 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.|
7272
| 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.|
7373

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.
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.
75+
76+
### Linked Audience advanced profiles conditions
77+
78+
|Advanced Conditions |Description |
79+
|--------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
80+
|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. |
7590

7691
## Step 2: Activate your Linked Audience
7792

@@ -155,22 +170,21 @@ After building your Linked Audience, choose **Save and Enable**. You'll be redir
155170
To enable your audience:
156171
Select the **Enabled** toggle, then select **Enable audience**.
157172

158-
### Compute Now
173+
### Run Now
159174

160-
You can trigger a compute for your audience if you want to send events to your destination without waiting for the next scheduled compute run. To do so, select **Compute Now**. This triggers a compute for the audience and sends events downstream.
175+
You can trigger a run for your audience if you want to send events to your destination without waiting for the next scheduled run. To do so, select **Run Now**. This triggers a run for the audience and sends events downstream.
161176

162177
### Set a run schedule
163178

164179
Use the Audience Overview page to view the audience profile count, current run schedule, run status, and upcoming run time.
165180

166181
Determine when an audience should run and send data to enabled destinations with a run schedule:
167-
168182
- **Manual**: Trigger audience runs manually by clicking **Run Now** on the Audience Overview page.
169-
- **Interval**: Trigger audience runs based on a predefined set of time intervals. Supported intervals are: 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 6 hours, 8 hours, 12 hours, or 1 day. If you select this option, Segment runs your audience after you enable the audience.
170-
- **Day and time**: Trigger audience runs at specific times on selected days of the week. If you select this option, Segment runs your audience at the first selected date and time.
183+
- **Interval**: Trigger audience runs based on a predefined set of time intervals. Supported intervals are: 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours, 6 hours, 8 hours, 12 hours, 1 day. If you select this option, Segment will run your audience after you enable the audience.
184+
- **Day and time**: Trigger audience runs at specific times on selected days of the week. If you select this option, Segment will run your audience at the first selected date and time.
171185

172186
You can maintain your run schedule at any time from the audience's **Settings** tab.
173187

174188
You can also click **Run Now** on the Audience Overview page at any time (even if the run schedule is **Interval** Overview **Day and time**) to manually trigger a run on your warehouse and send data to enabled destinations.
175189

176-
There may be up to a 5 minute delay from the configured start time for audiences that are configured with the **Interval** and **Day and time** run schedules. For example, if you configured an audience with the **Day and time** compute schedule to run on Mondays at 8:00 AM, it can compute as late as Monday at 8:05 AM. This is to help Segment better manage system load.
190+
There may be up to a 5 minute delay from the configured start time for audiences that are configured with the **Interval** and **Day and time** run schedules. For example, if you configured an audience with the **Day and time** compute schedule to run on Mondays at 8am, it can compute as late as Monday at 8:05am. This is to help us better manage our system load.

0 commit comments

Comments
 (0)