Add link to new page

Author: pwseg

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).
@@ -88,31 +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
-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).
+## Send audiences to destinations
 
-> 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