Skip to content

Commit f548386

Browse files
authored
Disconnecting vs removing a destination
1 parent ec5154c commit f548386

File tree

1 file changed

+8
-0
lines changed

1 file changed

+8
-0
lines changed

src/engage/audiences/index.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,14 @@ For step-by-step instructions on how to connect an audience to a destination, se
159159
> info "Historical data behavior for new destinations"
160160
> 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.
161161
162+
### Disconnect or remove a destination
163+
164+
Whnen managing your audience-destination connections you have two options:
165+
166+
1. **Connect to destination** - Toggles the connection on and off. When disconnected, the setup and configuration remain saved, but no data flows from the audience to the destination until you re-enable the connection. Use this option to pause sending data without losing your work.
167+
2. **Remove destination from audience** - Deletes the connection completely, so no events are sent to the destination. To use the destination again, you'll need to set it up as new from the beginning.
168+
169+
162170
## Understanding compute times
163171

164172
Because a number of factors (like system load, backfills, or user bases) determine the complexity of an audience, some compute times take longer than others.

0 commit comments

Comments
 (0)