Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add info on how Segment handles Klaviyo rate limiting #6463

Merged
merged 3 commits into from
Feb 27, 2025
Merged

Add info on how Segment handles Klaviyo rate limiting #6463

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
16eb993
Rate limit Klaviyo
Panandhan22 Apr 30, 2024
dda6936
Merge branch 'develop' into Panandhan22-patch-5
pwseg Feb 27, 2025
391434c
sentence case
pwseg Feb 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 11 additions & 3 deletions src/connections/destinations/catalog/actions-klaviyo/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,11 +82,19 @@ To add and remove profiles in Klaviyo with Engage Audience data:

## FAQ

#### Dealing with Error Responses from Klaviyo's API
#### Dealing with error responses from Klaviyo's API

##### 429 Too Many Requests
##### `429` Too Many Requests

If you're encountering rate limiting issues, consider enabling batching for the Action receiving these errors. To enable batching, navigate to the mapping configuration and set "Batch data to Klaviyo" to "Yes". This adjustment might help alleviate the rate limiting problem.
If you're seeing `429` rate limit errors, try enabling batching for the impacted Action. In the mapping configuration, set "Batch data to Klaviyo" to `Yes` to help reduce rate limits.

If `429` errors persist, Segment automatically adjusts the event delivery rate. There’s no fixed rate limit for the Klaviyo destination; Segment adapts based on Klaviyo’s capacity:

- If Klaviyo allows more traffic, Segment increases the send rate.
- If Klaviyo returns `429` or other retryable errors, Segment slows down.
- As more events are successfully delivered, the system gradually speeds up.

Retryable errors tell Segment to slow down, while successful deliveries let Segment send events faster.

##### 409 Conflict
In most cases, you can safely ignore a `409` error code.
Expand Down
Loading