Add details on Replay when connecting Engage Sources #4108
Merged
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
Adding the replay details in this section provides additional context around what occurs when a Source is added. The common misconception is that all of that source's data will be available in the Engage Space, but having this section added would subvert that misconception and enable customers to reach out preemptively with replay requests for historical data beyond 30 days.
|
@lizkane222 does this works till need to be done? This PR is quite old and still in draft state. We plan to close this PR on Friday January 26, 2024. If the work still needs to be done, please let us know. |
updates to grammar
cmastr
approved these changes
Feb 21, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
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.
Adding the replay details in this section provides additional context around what occurs when a Source is added. The common misconception is that all of that source's data will be available in the Engage Space, but having this section added would subvert that misconception and enable customers to reach out preemptively with replay requests for historical data beyond 30 days.
Proposed changes
Adding the replay details in this section provides additional context around what occurs when a Source is added to an Engage Space. The common misconception is that all of that source's data will be available in the Engage Space, but having this section added would subvert that misconception and enable customers to reach out preemptively with replay requests for historical data beyond 30 days.
Though some of this data can be found on the link provided, Connect production sources, some key details in the setup might be overlooked in this possibly too simple of a setup.
Merge timing