Everything you need to know about Limits

Wioleta Jednaka avatar
Written by Wioleta Jednaka
Updated over a week ago

Why set limits for sent messages?

When sending messages to customers, you've probably wondered whether you're sending too many, risking them being marked as SPAM. You can control this by setting limits in the edrone system. Once the set limits are exceeded, each subsequent message that should be sent gets blocked.

We have two places where we decide on the frequency of message sending. The first is the Customize each scenario section, where we can precisely specify when the customer will receive a message after a specific action on the website. The second is the Limits section, found in Settings in the main Mission Control panel.

How to set limits in the edrone system and on selected scenarios?

The operation of the Customize section is very similar in each scenario. Here's an example from the Recover Customers scenario. In this scenario, we can choose after how many days and hours two messages will be sent. Then, we have the option to limit the sending frequency in the "Send no more often than:" and "do not send after ordering" fields. As you can see, we have great control over the time and quantity of messages sent in each scenario.

To set the Message Sending Limit in MISSION CONTROL, go to the SETTINGS section, then click on LIMITS. Here, you can set limits for automation scenarios from the ENGAGE section.

We have:

  • Daily limit

  • Weekly limit

  • Monthly limit

Furthermore, at this point, you can also decide to limit the sending of transactional messages (automation scenarios) only to SUBSCRIBERS.


The above limits apply to transactional scenarios such as Recover Customers, Abandoned Carts, Viewed Products, After Purchase, Recommendations, Cross-Selling, Loyalty Program, Notify Availability.

Messages from the Dynamic Newsletter, Newsletter Subscription, Chat Subscription, Referral Program, and reward messages from the Loyalty Program are not counted towards the limits!

What does too restrictive limit setting lead to?

Setting limits makes sense if you have many automation scenarios running and want to control the number of messages received by the customer. Sometimes, if you only have a few scenarios running, there is no real need to set limits, as this can result in lower sales by not delivering specific messages. If you've decided to run a particular scenario, let it run. Too restrictive limits can also have the opposite effect, so it's worth analyzing the running scenarios and the customer's purchase path to decide based on that whether limits should be introduced.

Can our system automatically ban mailing to the same recipient group if the next dispatch takes place in a very short time, e.g., 1 minute?

This is controlled by the system mechanism. It limits the dispatch to a single customer to: a maximum of 4 messages in 24 hours, a maximum of 1 message from a specific scenario in 10 seconds (e.g., we will send a message for ABANDONED_CARTS and PRODUCT_VIEW in 10 seconds, but attempting to send 2 messages for ABANDONED_CARTS will result in blocking the second message).

In the case of sending Newsletter Categories, a situation may arise where we want to send messages to different categories at the same time.

Unfortunately, our system will only send the first planned newsletter,

and each subsequent one will be blocked because 2 newsletters cannot be sent at the same time. Just send such messages with a 1-minute interval, and there will be no problems with sending.

Both mechanisms do not apply to test messages, from the NEWSLETTER_SUBSCRIPTION scenario, and reward messages from the LOYALTY_PROGRAM scenario.

Moreover, there is still a provider-side block for email delivery. Not all providers add such a mechanism, but Emaillabs gives us the guarantee of blocking messages with the same ID within 24 hours. This means that we will not send 2 messages with the same parameters: CUSTOMER_ID, TRACKER_ID, ENGAGEMENT_ID, ENGAGEMENT_MESSAGE_ID, ENGAGEMENT_TYPE_ID, TIMESTAMP, EMAIL_CATEGORY_ID.

In practice, this mechanism is mainly used when resending a message that, for some reason, was not sent in its entirety. Thanks to this, we are sure that the customer will not receive a duplicate message.

Need Additional Help?

If you have questions about limits, contact us at

Did this answer your question?