Skip to content

Clarify expected behavior when connecting a new destination to an existing audience #6483

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.

Sign up for GitHub

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

Merged
merged 3 commits into from
Mar 27, 2025
Merged

Clarify expected behavior when connecting a new destination to an existing audience #6483

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c65ea15
Update index.md
samkcrespo May 1, 2024
68866ee
minor rewording
pwseg Mar 27, 2025
c0a3e70
Merge branch 'develop' into samkcrespo-patch-13
pwseg Mar 27, 2025
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
4 changes: 2 additions & 2 deletions src/engage/audiences/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,8 +109,8 @@ 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.
> info "Historical data behavior for new destinations"
> 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:[email protected]) to request a resync.

## Understanding compute times

Expand Down