--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/engage/audiences/send-audience-data#article headline: Send Audience Data to Destinations description: Connect Segment Engage audiences and computed traits to third-party destinations, view connected destinations, and manage destination mappings. url: https://www.twilio.com/docs/segment/engage/audiences/send-audience-data inLanguage: en dateModified: 2026-08-14T15:32:24.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Send Audience Data to Destinations * FREE: x * TEAM: x * BUSINESS: ✓ * ADDON: ✓ Engage Foundations requires a Business tier account and includes Unify. See the [available plans](https://segment.com/pricing), or [contact Support](https://segment.com/help/contact/) 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). > \[!NOTE] > > 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/segment/engage/using-engage-data/#compatible-engage-destinations) in the Engage documentation. For account-level audiences, you can send either a [Group](/docs/segment/connections/spec/group) call and/or [Identify](/docs/segment/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/segment/engage/audiences/account-audiences) for more information. > \[!NOTE] > > 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. ![Destinations table with Trade Desk CRM and Braze Cloud Mode connected and live.](https://docs-resources.prod.twilio.com/fef7ee26bc371105a1e98dbde5934cba9375c15d0c835e2a57d3e462a61f8357.png) The Destinations table contains information about the destination's matching mappings, status, and sync status. ### Matching mappings [Actions destinations](/docs/segment/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/segment/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). > \[!TIP] > > Use Segment's [Duplicate mappings](/docs/segment/connections/destinations/actions/#duplicate-mappings) feature to create an exact copy of an existing mapping. The copied mapping has the same configurations and enrichments as your original mapping. ### Self-service resyncs A resync sends the current state of a computation — an Audience, Computed Trait, or Journey — to its connected destination. Segment sends the complete set of users for that computation to the destination, ensuring that the destination is up to date with the current data in Segment. A resync differs from a [replay](/docs/segment/guides/what-is-replay/). A replay resends events that occurred during a specified time range, whereas a resync sends the present state of all users, not only recent changes. #### When to trigger a resync You might need to trigger a resync in the following situations: * You change Trait Enrichment or ID Sync settings for an existing audience destination and want the updated configuration applied to users who are already present in the destination. For details, see [Resyncs](/docs/segment/engage/trait-activation/#resyncs). * You connect a new destination to an existing audience and want to send its current membership to the destination, rather than only membership changes that occur after the destination is added. Note that adding a destination through the Segment UI resyncs automatically. For details, see [Connect your audience to a destination](/docs/segment/engage/audiences/#connect-your-audience-to-a-destination). * You enable ID Sync on a destination (for example, Google Ads Remarketing Lists) after it has already started receiving data from an audience and want the newly available identifiers applied to existing users. For guidance, see [Troubleshooting](/docs/segment/connections/destinations/catalog/adwords-remarketing-lists/#troubleshooting). You can trigger a full resync of an audience's membership data to a destination directly from the Segment app. To trigger a resync: 1. Go to **Engage > Audiences**, then select the audience you want to resync. 2. From the audience's overview page, go to the **Destinations** section. 3. Click the three-dot menu (**⋮**) on the destination you want to resync. 4. Select **Full resync**. Resyncs are scoped to the individual activation. Segment only re-sends data for that specific activation. You can also trigger resyncs with the [API](https://docs.segmentapis.com/tag/Activations) by setting `performResync: true` when you create or update an activation. > \[!WARNING] > > Segment doesn't send a notification when a resync finishes. To confirm that your destination contains the updated data, check the destination directly. The time required depends on the destination's rate limits. See [Rate limits on Engage Event Destinations](/docs/segment/engage/using-engage-data/#rate-limits-on-engage-event-destinations) for destination-specific limits. > > You can submit multiple resyncs per workspace, but Segment processes a limited number at a time and queues the rest. Triggering additional resyncs doesn't accelerate processing. See [Engage Default Limits](/docs/segment/engage/product-limits/#audiences-and-computed-traits) for the current resync concurrency limit. ![Destinations table with the three-dot menu open on a destination, showing the View Delivery Overview and Full resync options.](https://docs-resources.prod.twilio.com/903c3f2c5f6259c6ab8760ffca254d3be543a5609cd9d7a8242440b72b7fcf9a.png)