Duration of Campaign Send Job

Hey @Optihub 

Welcome to the community!

Thanks for reaching out for help with our developer documentation.

• As for how long the campaign send should process will depend on the list or segment size you are sending to. Per the document you shared the rate limits are as follows with Klaviyo API: 10/sec (bursts) or 150/min (stream). 

• As for how you're approaching the send impacting performance, it is important to consider the goal of the campaign (i.e. is this time sensitive? Or are you trying to send campaigns based on realtime data you are collecting and need it more spaced in time to collect then deliver data.)

As I just shared when considering burst versus stream API calls for campaign sends goals, the impact on the campaign's efficiency, performance, and user experience can be significant. Here’s how each approach might affect campaign sends:

Burst API Calls in Campaign Sends (depending on your campaign goal, this is probably the route you want to go with 1 off campaign sends)

Advantages:

1. Efficiency: Sending a large number of campaign messages in a short period can be efficient for specific scenarios where all messages need to be delivered at once.

   1. example: you are offering a promotion to the first 100 customers who purchase XXX item. You want to everyone on the list to receive it as fast as possible so the all have the same odds of being one of the first 100 customers.

2. Simplicity: Implementation is often simpler since you can send a batch of messages in one go. 

3. Predictability: Easier to predict when messages will be sent and received since the send process is concentrated into a single burst.

Disadvantages:

1. Rate Limits: API rate limits can be a significant constraint, as sending too many requests in a short period might lead to throttling or blocking.

2. Deliverability Issues: Sending a large number of messages at once might increase the likelihood of being flagged as spam by email or message servers.

Stream API Calls in Campaign Sends (this is what you will want to setup if you are looking for longterm or continuous campaigns)

Advantages:

1. Real-Time Delivery: Messages are sent as soon as the data becomes available, ensuring timely delivery.

2. Rate Management: Continuous, paced delivery can help manage and stay within API rate limits.

3. Load Distribution: Distributes the server load over time, reducing the risk of overload and downtime.

4. Improved Deliverability: Lower risk of being flagged as spam since messages are sent in a more natural, less bursty manner.

Disadvantages:

1. Complexity: Implementing a streaming solution can be more complex and may require persistent connections and more sophisticated error handling.

2. Latency: There can be slight delays between data availability and message sending, depending on the stream's implementation.

Hope this helps! Let us know if you have any other questions!