Peer reviews

Author: cmastr

src/engage/audiences/linked-audiences.md

@@ -29,7 +29,7 @@ To help you get started with Linked Audiences, consider the following best pract
 
 ## Step 1: Build a Linked Audience
 
-You can build a Linked Audience from profiles associated with an entity, trait, event, or existing audience. You can also filter on profile traits and event history, and filter on warehouse entities mapped to the Data Graph.
+Linked Audiences allows you to filter based on properties such as profile traits, relational data mapped to the Data Graph, events, and existing audience membership. 
 
 ![Choose your audience conditions](/docs/engage/images/conditions.png)
 
@@ -44,10 +44,10 @@ You can build a Linked Audience from profiles associated with an entity, trait,
 
 After creating the audience, you'll be redirected to the Overview page. By default, the audience is disabled. Segment recommends that you take the following actions:
 1. Add a destination.
-2. Configure an [event emitter](#maintain-event-emitters).
+2. Configure and create [event selections](#maintain-event-emitters).
 3. Enable the audience. 
 
-This will trigger a compute for the audience (where the audience conditions will run on your data warehouse) and will send events downstream.
+This triggers a compute for the audience (where the audience conditions run on your data warehouse) and sends events downstream.
 
 #### Event Conditions
 
@@ -60,19 +60,6 @@ As you're building your Linked Audience, you can choose from the following event
 | Part of an audience     | Creates a condition that filters profiles that are part of an existing linked or classic audience. |
 | Performed event         | Creates a condition that filters profiles on their event history. |
 
-### Error states
-
-As you’re building or maintaining your audience, you may encounter an error or warning message about possible impacts to your audience. Below are some common reasons errors occur, along with suggested troubleshooting steps.
-
-| Error        | Description                           | Troubleshooting              |
-|---------------------------|---------------------------------------|-------------|
-| Column deleted from warehouse  | A column you're trying to use in the builder was deleted from your warehouse (for example, `account_balance`).          | Select a valid column in the audience builder, or re-add the deleted column in your warehouse.        |
-| Column data type changed in the warehouse  | A column data type in your warehouse has been changed. (For example, `account_balance` changed from a `number` to a `string`.)          | Update the column data type in your warehouse, or select a different column in the audience builder.        |
-| Table deleted from warehouse | A table you're trying to use has been deleted from your warehouse. (For example, the `accounts` table was deleted in your warehouse.)          | You can re-add the table to your warehouse, choose a valid table to use in the audience condition, or remove the audience condition entirely.     |
-| Entity deleted from Data Graph | A table you're trying to use has been deleted from your Data Graph. (For example, the `accounts` table was deleted in your Data Graph.) | You can re-add the missing entity in the data graph, remove the entity from the audience condition, or remove the audience condition entirely. Editing the audience definition may require you to update your event emitters. |
-| Entity removed from audience condition | An entity was removed from the audience condition. For example, an `accounts` entity was removed from audience condition. | Update your event emitters. Navigate to **Engage > Audiences** and select your destination to view and maintain event emitters.  |
-| Warehouse error | You have incorrect permissions or failed to connect to your warehouse. | Check your permissions to ensure you have a valid connection to the Data Graph and your warehouse. |
-
 #### Edit an audience
 To edit an audience:
 1. Navigate to **Engage > Audiences**, and select the audience you'd like to edit.
@@ -109,11 +96,11 @@ You can use your Linked Audience to activate any [actions-based destination](/do
 
 ### Step 2a: Add an action destination
 
-To activate your Linked Audience, first add an action destination.
+To activate your Linked Audience, first [add an action destination](/connections/destinations/actions/) in Connections.
 
 From Add destination, select your destination and click **Next**.
 
-### Step 2b: Select event
+### Step 2b: Add an event
 After adding a  destination to your audience, configure the data you would like to send to the destination. First, select a type of event you want to send to the destination. Events update destinations about changes to your entity or audiences and contain data that can be used in the downstream destination. 
 
 You can send events:
@@ -133,59 +120,47 @@ You can send events:
 
 #### Entity added
 
-Send a Track event when an entity branch at any level of a nested entity condition matches the audience condition. With this event, you must select the entity that triggers Segment to send the Track event.
+Send a Track event when an entity condition associated with a profile matches the audience condition. With this event, you must select the entity that triggers Segment to send the Track event.
 
-Example use cases:
+Example:
 - Send a reminder to a customer when a credit card associated with their profile has an outstanding balance.
 - Notify a traveler when a flight associated with their profile is delayed.
 - Notify a customer when a product associated with their profile's wishlist is back in stock.
 
 #### Entity removed
 
-Send a Track event when an entity associated with a profile no longer matches the audience conditions. With this event, you must select the entity that triggers Segment to send the Track event.
+Send a Track event when an entity condition associated with a profile no longer matches the audience condition. With this event, you must select the entity that triggers Segment to send the Track event.
 
-Example use cases:
+Example:
 - Send a confirmation to a customer when a credit card associated with their profile has been paid off.
 - Send a confirmation to the primary doctor when each of their associated patients completes their annual check up.
 
 #### Audience entered
 
 Send a Track event when a profile matches the audience condition.
 
-Example use cases:
+Example:
 - Send a congratulatory email when a traveler qualifies for premium status with a mileage program.
 - Send a discount to all customers with a particular product on their wishlist.
 
 #### Audience exited
 
 Send a Track event when a profile no longer matches the audience condition.
 
-Example use cases:
+Example:
 - Send an email to credit card owners to confirm that their credit cards have been paid in full.
 - Send a confirmation to a patient when they have completed all their pre-screening forms.
 
-#### Audience Membership Changed
+#### Audience membership changed
 
 Send an Identify event when a profile's audience membership changes.
 
-Example use case:
+Example:
 - Update a user profile in a destination with the most recent audience membership.
 
-#### Maintain event emitters
-
-Event emitters indicate when an audience or entity-related event should trigger a Segment event on a particular destination.
-
-To view event emitters, navigate to **Engage > Audiences** and select your destination. From the destination's **Events** tab:
-
-- Click **Add event** to add a new event
-- Enable or disable an event with the status toggle
-- Use the three dots icon to edit or delete an event
-
-Selecting **Edit event** allows you to update [event enrichments and mappings](#step-2d-configure-the-event).
-
 ### Step 2c: Select an action
 
-Select the destination action to call when the event happens. Ensure the action you selected is relevant to the type of event you previously selected. For example, if you selected **Audience Membership Changed**, ensure your action is also an Identify event.
+Select the destination action to call when the event happens. Ensure the action you selected is relevant to the type of event you previously selected. For example, if you selected **Audience membership changed**, ensure your action is also an Identify event.
 
 Segment displays available actions based on the destination action you've connected with your Linked Audience.
 
@@ -196,25 +171,26 @@ See [destination actions](/docs/connections/destinations/actions/) to learn more
 
 ### Step 2d: Configure the event
 
-Select additional user profile properties or entity column values to include in the event. This is where you select any additional context you want to send to the destination.
+Once you select an action, Segment will attempt to automatically configure the data fields that will be sent to the destination. You can review and adjust these settings before enabling this event. 
+- Enrich event (optional)
+- Map event 
+- Test event (optional)
 
-To configure your event:
+#### Enrich event
+Select additional profile traits or entity column values to include when the event is sent.
+These traits and properties can be associated with the profile or the entity  conditions that were defined in the audience definition.
+As you're configuring your event, click **Show Preview** to view a preview of the enriched event based on your profile and entity property selections.
+For example, if your profiles include traits that are required in your downstream destination, this is where you would make the appropriate selections.
 
-1. Select additional user profile properties or entity column values to include with each event. This is where you select the additional context you want to send to your destination.
-- As you're configuring your event, click **Show Preview** to view a preview of the enriched event based on your property selections.
-2. Map your event from your audience to your destination.
-- [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.
-3. You can optionally send a test event to your destination by clicking **Send test event to destination**. You can edit the User ID for the test event, and you'll also see a table with event fields and example values.
-- After sending the test, you'll receive a response from Segment and the destination, which allows you to see what data sent to your destination may look like.
-4. 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).
-- This is only available for the **entity added**, **audience entered**, and **audience membership changed** event types.
-4. To enable your Linked Audience, click **Save**.
+[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.
 
-#### Send events for current profiles and entities in the audience
+#### Test event
+You can optionally send a test event to your destination by clicking **Send test event to destination**. You can edit the User ID for the test event, and you'll also see a table with event fields and example values. After sending the test, you'll receive a response from Segment and the destination, which allows you to see what data sent to your destination may look like.
 
-This checkbox is unchecked by default. If you leave this box unchecked, Segment only sends events for new profiles and entities that match the audience conditions.
+#### Send events for current profiles and entities in the audience checkbox
 
-If you select this checkbox, Segment will also send events for profiles and entities that currently match the audience description.
+By default, Segment will  only send events for new profiles and entities that match the audience conditions. This means that when the event is created, it will not send events for profiles and entities that currently meet the audience criteria.
+If you want to send events for profiles and entities that currently meet the audience criteria, check this box. This is only available for the **entity added**, **audience entered**, and **audience membership changed** event types.
 
 ## Step 3: Confirm the payload in your destination