Skip to content

Commit 68866ee

Browse files
authored
minor rewording
1 parent c65ea15 commit 68866ee

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/engage/audiences/index.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,8 @@ For account-level audiences, you can send either a [Group](/docs/connections/spe
109109

110110
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.
111111

112-
> info ""
113-
> When you connect a new Destination with an existing Audience, Engage will backfill historical data for that Audience to the new Destination if the 'Include Historical Data' option is enabled in the Audience Settings. For Audiences that do not have this setting enabled, only new data will be sent. If you'd like to sync all Audience data to the newly connected Destination, please reach out to [Support](friends@segment.com) to request a Resync.
112+
> info "Historical data behavior for new destinations"
113+
> When you connect a new destination to an existing audience, Engage backfills historical data if the **Include Historical Data** option is enabled in the audience settings. If this setting is disabled, only new data gets sent. To sync all historical data manually, [contact Support](mailto:friends@segment.com) to request a resync.
114114
115115
## Understanding compute times
116116

0 commit comments

Comments
 (0)