Clarify expected behavior when connecting a new destination to an existing audience #6483
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pwseg
changed the title
pwseg
previously approved these changes
Mar 27, 2025
pwseg
approved these changes
Mar 27, 2025
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Update Audience Sync to Destination's section to clarify expected behavior when connecting a new destination to an existing Audience.
If 'include historical data' is enabled, the entire audience will be sent when a new destination is connected, otherwise, only new data is sent.
Merge timing
Related issues (optional)