Add info on how Segment handles Klaviyo rate limiting #6463
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
If the issue persists even after enabling batching, it will be auto-tuned. We don't have a fixed rate limit for the Klaviyo destination; our system uses an adaptive algorithm to determine the proper rate at which to send events. If there is an increase in Klaviyo destination rate limit, our system will adapt to a rate that is slightly faster than what the downstream service can handle. The occurrence of 429 and other retryable errors actually signals our egress to slow down. The more retryable errors we encounter, the slower we send events; if we achieve more successes, the rate will increase.
pwseg
changed the title
pwseg
approved these changes
Feb 27, 2025
|
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.
If the issue persists even after enabling batching, it will be auto-tuned. We don't have a fixed rate limit for the Klaviyo destination; our system uses an adaptive algorithm to determine the proper rate at which to send events. If there is an increase in Klaviyo destination rate limit, our system will adapt to a rate that is slightly faster than what the downstream service can handle. The occurrence of 429 and other retryable errors actually signals our egress to slow down. The more retryable errors we encounter, the slower we send events; if we achieve more successes, the rate will increase.
Proposed changes
Merge timing
Related issues (optional)