Skip to content

Commit 356f601

Browse files
pwsegforstisabella
andauthored
Update src/engage/audiences/send-audience-data.md
Co-authored-by: forstisabella <[email protected]>
1 parent 98f7f33 commit 356f601

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Once you've previewed your audience, you can choose to connect it to a destinati
1616

1717
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.
1818

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.
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 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.
2020

2121
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.
2222

0 commit comments

Comments
 (0)