Update index.md repeater to include details on replay #4801
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
Add Replay details when using a Repeater
forstisabella
approved these changes
Jan 26, 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.
Add Replay details when using a Repeater
Proposed changes
Added the section Replays with a Repeater
Replays can affect your MTU count when using a Repeater destination. Notify your team before initiating a Replay if you’re using a Repeater destination. There are edge cases where the repeater would count towards MTUs, specifically when replaying historical data from the source connected to feed data into that Repeater destination. This is because userIds/anonymousIds would not have been seen by the source the Repeater sends data to. The API plans count by events sent through the pipeline; the repeater resends an event through the entire pipeline [Source → Repeater → Source → Destinations] so one event is sent through twice, and would increase the throughput count.
This is necessary to add at this point in the docs so that customers are aware of the nuances associated with repeaters and replays.
Merge timing
Related issues (optional)
Zendesk tickets :