@kapa.ai is ther any way to have the Klaviyo source not hit rate limits?

There are several ways to help the Klaviyo source connector avoid hitting rate limits: 1. Limit Conversion Metric IDs for Analytics Streams The Campaign Values Reports and Flow Series Reports streams are particularly rate-limit-sensitive, with strict limits of 1 request/second burst, 2 requests/minute steady, and 225 requests/day. By default, the connector fetches reports for all metrics in your account. You can reduce API calls significantly by specifying only the conversion metrics you need using the Conversion Metric ID(s) (

metric_ids

) configuration field (e.g.,

RESQ6t,ABC123

). [Klaviyo supported streams] 2. Disable Fetching Predictive Analytics The Profiles stream can experience transient API errors under heavy load. You can enable the "Disable Fetching Predictive Analytics" setting to improve sync success rates. Note that this will remove the

predictive_analytics

field from Profiles stream records. [Klaviyo performance] 3. Adjust the Number of Worker Threads The

num_workers

configuration option controls how many parallel worker threads are used. Reducing this value (default is 10) can lower the rate of API requests, helping stay within Klaviyo's rate limits. [Klaviyo Terraform schema] 4. General Behavior Under normal usage, the Klaviyo connector is designed to handle rate limits automatically via retries. If you encounter rate limit issues that are not automatically retried successfully, it's recommended to open an issue. [Klaviyo performance] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.