Skip to content

Commit f34808a

Browse files
authored
Update index.md
1 parent 5c61875 commit f34808a

File tree

1 file changed

+6
-1
lines changed
  • src/connections/destinations/catalog/actions-klaviyo

1 file changed

+6
-1
lines changed

src/connections/destinations/catalog/actions-klaviyo/index.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,11 @@ To add and remove profiles in Klaviyo with Engage Audience data:
8585

8686
## FAQ
8787

88-
### Dealing with 429 Responses from Klaviyo's API
88+
### Dealing with Error Responses from Klaviyo's API
89+
90+
#### 429 Too Many Requests
8991

9092
If you're encountering rate limiting issues, consider enabling batching for the Action receiving these errors. Ensure that within the mapping configuration, "Batch data to Klaviyo" is set to "Yes". This adjustment can help alleviate the rate limiting problem.
93+
94+
#### 409 Conflict
95+
In most cases, you can safely ignore this error code as it prevents duplicate profiles from being created in Klaviyo. When you use the [Upsert Profile](/docs/connections/destinations/catalog/actions-klaviyo/#upsert-profile) mapping to send Identify events, Segment will first attempt to [create a new profile in Klaviyo](https://developers.klaviyo.com/en/reference/create_profile). If the first request returns with a `409` error code, a second request will be sent to [update the existing profile with the given profile ID](https://developers.klaviyo.com/en/reference/update_profile).

0 commit comments

Comments
 (0)