Merge pull request #6520 from segmentio/engage-audience-destinations-update

Engage Audience Destination Update [DOC-892]

Author: pwseg

src/_data/sidenav/main.yml

@@ -401,6 +401,8 @@ sections:
       title: Generative Audiences Nutrition Facts Label
     - path: '/engage/audiences/organization'
       title: Organize Audiences
+    - path: '/engage/audiences/send-audience-data'
+      title: Send Audiences to Destinations
 
   - section_title: Journeys
     description: "Learn how to create multi-step Journeys to tailor messages to your users."

src/engage/audiences/index.md

@@ -5,9 +5,6 @@ redirect_from:
   - '/personas/audiences'
 ---
 
-
-
-
 Audiences let you group users or accounts based on event behavior and traits that Segment tracks.
 
 You can build Audiences from core **tracking events**, **traits**, and **computed traits**. You can then sync Audiences to hundreds of [Destinations](/docs/connections/destinations/) or access them with the [Profile API](/docs/unify/profile-api).
@@ -26,6 +23,9 @@ You can build an Audience from existing events, traits, computed traits, or othe
 > warning ""
 > Editing an audience before the initial backfill is complete can create technical errors.
 
+> warning "Audience Keys"
+> Avoid using the same Audience Key twice, even if you've deleted the original Audience.
+
 ### Events
 
 You can build an Audience from any events that are connected to Engage, including [Track](/docs/connections/spec/track), [Page](/docs/connections/spec/page), and [Screen](/docs/connections/spec/screen) calls. You can use the `property` button to refine the audience on specific event properties, as well. 
@@ -85,32 +85,11 @@ If you have a B2B business, you might want to build an Audience of accounts. You
 See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information.
 
 
+## Send audiences to destinations
 
-## Send Audiences to Destinations
-With the help of Sources and Destinations in Segment's catalog, you can create and send Audiences and computed traits to third-party services.
-
-Segment's Connections pipeline first collects and sends events from your Source to your Destination. Built on top of Connections, Engage then uses the same Source events to let you create Audiences and computed traits within Segment. You can then send the Audience or computed trait you've built to your Destination(s).
-
-> info ""
-> Because Engage only sends Audiences and computed traits to Destinations, it doesn't replace a standard event pipeline. Connect a Source directly to a Destination if you want the Destination to receive all events that Segment gathers.
-
-### Connect your Audience to a Destination
+You can send audiences and computed traits to third-party services in Segment's [Destinations catalog](/docs/connections/destinations/).
 
-> warning "Audience Keys"
-> Avoid using the same Audience key twice, even if you've deleted the original Audience.
-
-Once you've previewed your Audience, you can choose to connect it to a Destination or keep the Audience in Segment and export it as a CSV file download.
-
-If you already have Destinations set up in Segment, you can import the configuration from one of your existing sources to Engage. You can only connect one Destination configuration per Destination type.
-
-When you create an Audience, Segment starts syncing your Audience to the Destinations you selected. Audiences are either sent to Destinations as a boolean user-property or a user-list, depending on what the Destination supports. Read more about [supported Destinations](/docs/engage/using-engage-data/#compatible-engage-destinations) in the Engage documentation.
-
-For account-level audiences, you can send either a [Group](/docs/connections/spec/group) call and/or [Identify](/docs/connections/spec/identify) call. Group calls will send one event per account, whereas Identify calls will send an Identify call for each user in the account. This means that even if a user hasn't performed an event, Segment will still set the account-level computed trait on that user.
-
-Because most marketing tools are still based at the user level, it is often important to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information.
-
-> info ""
-> When you connect a new Destination to an existing Audience, Engage will backfill historical data for that Audience to the new Destination.
+For step-by-step instructions on how to connect an audience to a destination, see [Send Audience Data to Destinations](/docs/engage/audiences/send-audience-data/).
 
 ## Understanding compute times
 

src/engage/audiences/send-audience-data.md

@@ -0,0 +1,67 @@
+---
+title: Send Audience Data to Destinations
+plan: engage-foundations
+---
+
+With the help of sources and destinations in Segment's catalog, you can create and send audiences and computed traits to third-party services.
+
+Segment's Connections pipeline first collects and sends events from your source to your destination. Built on top of Connections, Engage then uses the same source events to let you create audiences and computed traits within Segment. You can then send the audience or computed trait you've built to your destination(s).
+
+> info ""
+> Because Engage only sends audiences and computed traits to destinations, it doesn't replace a standard event pipeline. Connect a source directly to a destination if you want the destination to receive all events that Segment gathers.
+
+## Connect your audience to a destination
+
+Once you've previewed your audience, you can choose to connect it to a destination or keep the audience in Segment and export it as a CSV file download.
+
+When you create an audience, Segment starts syncing your audience to the destinations you selected. Audiences are either sent to destinations as a boolean user-property or a user-list, depending on what the destination supports. Read more about [supported destinations](/docs/engage/using-engage-data/#compatible-engage-destinations) in the Engage documentation.
+
+For account-level audiences, you can send either a [Group](/docs/connections/spec/group) call and/or [Identify](/docs/connections/spec/identify) call. Group calls send one event per account, whereas Identify calls send an Identify call for each user in the account. This means that even if a user hasn't performed an event, Segment will still set the account-level computed trait on that user.
+
+Because most marketing tools are still based at the user level, you'll usually want to map this account-level trait onto each user within an account. See [Account-level Audiences](/docs/engage/audiences/account-audiences) for more information.
+
+> info ""
+> When you connect a new destination to an existing audience, Engage will backfill historical data for that audience to the new destination.
+
+Follow these steps to connect an audience to a destination:
+
+1. Navigate to **Engage > Audiences**, then select the audience you want to connect.
+2. From the audience's overview page, click **+ Add destination**.
+3. Select the destination you want to connect to, then click **Add destination**. 
+4. Segment then begins its initial sync to the destination.
+
+## View connected destinations
+
+You can view a list of an audience's connected destinations in the destination list table of the audience overview tab. 
+
+![The Engage Destinations table showing two connected destinations](/docs/engage/images/destinations_table.png)
+
+The Destinations table contains information about the destination's matching mappings, status, and sync status.
+
+### Matching mappings
+
+[Actions destinations](/docs/connections/destinations/actions/) have mappings that can receive granular data from your audience. The **Matching mappings** column shows the number of mappings that match the data coming from the audience, as well as the number of enabled and disabled mappings. See [Working with mappings](#working-with-mappings) for more information.
+
+The Matching mappings column will show `Not applicable` for classic destinations.
+
+### Status columns
+
+The **Destination status** column shows `Connected`, `Disconnected`, or `Disabled`: 
+
+- `Connected` indicates that the destination is enabled and receiving data from the audience. 
+- `Disconnected` means that either the destination is disabled **or** the audience isn't sending it data.
+- `Disabled` means that the destination is disabled **and** the audience isn't sending it data.
+
+The **Sync status** column shows the current [compute status](/docs/engage/audiences/#compute-statuses) between the audience and connected destination.
+
+### Working with mappings
+
+You can add and access mappings within your audience's connected destination by following these steps:
+
+1. Navigate to **Engage > Audiences**.
+2. From the Destinations list, click the destination you want to work with, or click **+Add mapping**.
+3. In the destination's side panel, click **Matching mappings**.
+4. In the **Add Mapping** popup, select the mapping that you want to add.
+5. Segment then opens the destination's mappings tab. Add the mapping(s) you want, then click **Save**.
+
+Segment then returns you to the audience's destination side panel, which shows your new mapping(s).