Skip to content

Commit 41077fb

Browse files
committed
draft [netlify-develop]
1 parent ec02d82 commit 41077fb

File tree

1 file changed

+13
-7
lines changed

1 file changed

+13
-7
lines changed

src/engage/audiences/linked-audiences.md

Lines changed: 13 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -55,13 +55,7 @@ To build a Linked Audience:
5555
Optionally, select a folder to add this audience.
5656
8. Click **Create Audience**.
5757

58-
### Maintaining Linked Audiences
59-
60-
After creating your Linked Audience, you will be brought to the Overview page with the Linked Audience in a disabled state. On the Overview page, you can view relevant audience information, such as Profiles in audience, Run schedule, Latest run, and Next run.
61-
62-
You can also delete Linked Audiences from the menu options or edit your Linked Audience in the Builder tab. If you edit an audience with configured activation events, you should disable or delete impacted events for your audience to successfully compute. Events are impacted if they reference entities that are edited or removed from the audience definition.
63-
64-
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.
58+
After creating your Linked Audience, you will be brought to the Overview page with the Linked Audience in a disabled state.
6559

6660
### Linked Audience conditions
6761

@@ -96,6 +90,7 @@ at most: supports 0 or greater.
9690

9791
*When filtering by 0, you can’t filter on by entity properties or on additional nested entities.
9892

93+
9994
#### Operator selection
10095

10196
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.
@@ -245,3 +240,14 @@ Delivery Overview shows you four steps in your data activation pipeline:
245240
- **Filtered at Destination**: The activation pipeline is rich with features that let you control which events make it to the destination. If any events aren't eligible to be sent (for example, due to destination filters, insert function logic, and so on), Segment will show them in Filtered at Destination.
246241
- **Failed Delivery**: Events that Segment attempted but failed to deliver to your destination. Failed Delivery indicates an issue with the destination, like invalid credentials, rate limits, or other error statuses received during delivery.
247242
- **Successful Delivery**: Events that Segment successfully delivered to your destination. You'll see these events in your downstream integration.
243+
244+
## Maintaining Linked Audiences
245+
246+
You can maintain your Linked Audience by accessing these tabs on the main page of your Linked Audience:
247+
248+
Tab name | Information
249+
-------- | -----------
250+
Overview | On this tab you can: <br>* View relevant audience information, such as Profiles in audience count, run schedule, latest run, and next run. <br>* Enable or disable, manually run, clone and delete audiences. <br>&nbsp;&nbsp;- *Note:* Cloning a linked audience creates a new linked audience in the builder create flow with the same conditions as the linked audience that it was cloned from. <br> * View the list of profiles in the audience with the Audience Explorer. <br>* View connected destinations and configured activation events.
251+
Builder | On this tab you can: <br>* View or edit your linked audience conditions. <br>&nbsp;&nbsp; - *Note:* If you edit an audience with configured activation events, you should disable or delete impacted events for your audience to successfully compute. Events are impacted if they reference entities that are edited or removed from the audience definition.
252+
Runs | On this tab you can: <br>* View information about the last 50 audience runs, such as start time, run duration, run result, and change summary. You can also view granular run stats to help you understand the duration of each step in the run such as: <br> &nbsp;&nbsp; - Queueing run: The time spent in the queue waiting for other runs to finish before this one begins. <br>&nbsp;&nbsp; - Extracting from warehouse: The duration of the audience query and data transfer from the source warehouse. <br>&nbsp;&nbsp; - Preparing to deliver events: The time taken to process and ready events for delivery to connected destination(s).
253+
Settings | On this tab you can view or edit the linked audience name, description, and run schedule.

0 commit comments

Comments
 (0)