Skip to content

Commit d9e8bd4

Browse files
committed
Add screenshot against my will
1 parent 8c3502a commit d9e8bd4

File tree

2 files changed

+15
-2
lines changed

2 files changed

+15
-2
lines changed

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

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,16 @@ Segment's Connections pipeline first collects and sends events from your source
1212
1313
## Connect your audience to a destination
1414

15-
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.
15+
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.
16+
17+
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.
18+
19+
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.
20+
21+
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.
22+
23+
> info ""
24+
> When you connect a new Destination to an existing Audience, Engage will backfill historical data for that Audience to the new Destination.
1625
1726
Follow these steps to connect an audience to a destination:
1827

@@ -21,7 +30,11 @@ Follow these steps to connect an audience to a destination:
2130
3. Select the destination you want to connect to, then click **Add destination**.
2231
4. Segment then begins its initial sync to the destination.
2332

24-
You can view a list of an audience's connected destinations in the destination list table of the audience overview tab.
33+
## View connected destinations
34+
35+
You can view a list of an audience's connected destinations in the destination list table of the audience overview tab.
36+
37+
![The Engage Destinations table showing two connected destinations](/docs/engage/images/destinations_table.png)
2538

2639
### Working with mappings
2740

45 KB
Loading

0 commit comments

Comments
 (0)