Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update index.md - clarify expected behavior when connecting a new destination to an existing audience #6483

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/engage/audiences/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -110,7 +110,7 @@ For account-level audiences, you can send either a [Group](/docs/connections/spe
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.
> 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.

## Understanding compute times

Expand Down