Updates to docs based on lookback config updates #7840
Conversation
This file contains hidden or 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
stayseesong
requested changes
Aug 20, 2025
src/engage/audiences/index.md
Outdated
| @@ -257,7 +257,7 @@ To edit a realtime trait or audience: | |||
| Engage then processes your realtime audience or trait edits. While the edit task runs, the audience remains locked and you can't make further changes. Once Engage incorporates your changes, you'll be able to access your updated audience or trait. | |||
|
|
|||
| > warning "" | |||
| > If your audience includes historical data (Historical Backfill is enabled), editing an audience creates a new backfill task. The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations). | |||
| > If your audience includes historical event data (the **Include Historical Event Data** option is enabled), editing an audience creates a new backfill task (you may also change this setting after creation). The backfill task, and therefore the edit task, take longer to process if the audience is connected to a destination with rate limits. Rate-limited destinations dictate how fast Engage can backfill. View a list of [rate-limited destinations](/docs/engage/using-engage-data/#rate-limits-on-engage-event-destinations). | |||
There was a problem hiding this comment.
@wilwong-twilio the "(you may also change this setting after creation)" doesn't make sense to add into this warning. I'm going to suggest taking it out
Co-authored-by: stayseesong <[email protected]>
Co-authored-by: stayseesong <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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
Updated docs based on new changes to lookback config - https://docs.google.com/document/d/17GMf6Paiz1vB2yMegwZFb945SbBtrb6qC4wPLfIqxnI/edit?tab=t.0
Merge timing