After you create a campaign, you can optimize its delivery so that users receive it when they're most likely to engage with it.
This level of personalization is important for building trust and brand loyalty, can help with compliance (especially for SMS campaigns), and can help you manage deliverability and performance concerns that can arise when you send lots of messages at the same time.
This article describes delivery options you can enable for your campaigns.
In this article
Campaign delivery options
As you're setting up a campaign, use the Delivery area to optimize the way your campaign is delivered. Depending on the type of campaign you're sending, you can adjust Quiet Hours, Send Time Optimization, Frequency Cap, Send Rate Limit, and Display Priority.
Email, Push, SMS, In-App, Web Push
Avoid disturbing users at inconvenient times by using Quiet Hours to pause sends during specified hours.
Enabling Quiet Hours
To turn on Quiet Hours for a campaign, when you're setting up a campaign, switch on the Quiet hours toggle in the Delivery area. Then, specify the period of time during which the message shouldn't be sent, and whether it should be sent after quiet hours ends, or be cancelled.
For more information, see Quiet Hours.
Send Time Optimization
To have Iterable send a campaign to each recipient at a specific time when they're likely it engage with it (based on their historical data), enable Send Time Optimization.
If the Send Time Optimization option isn't available, your Iterable project doesn't have enough historical engagement data. This is common for staging and test projects. Try switching to a project with more engagement data or wait until you've sent more campaigns.
Enabling Send Time Optimization
To turn on Send Time Optimization for all of your campaign's recipients, switch on the Send Time Optimization toggle and enter a number of hours (between 6 and 24) by which the send must complete.
You can't disable Send Time Optimization after Iterable starts sending a campaign.
To learn more about Send Time Optimization, see:
Email, Push, SMS
Marketing messages may be subject to sending limits according to your project's Frequency Management settings.
To override the frequency cap, toggle this option. When enabled, this setting ignores Frequency Management rules, and sent messages do not count towards frequency cap limits.
Frequency Management doesn't apply to transactional message types.
Read more at Frequency Management.
Send rate limit
Email, Push, SMS, In-App, Web Push
This feature is currently available in beta for select Iterable members.
Set a send rate limit to:
- Prevent your website and servers from being overwhelmed with traffic when many of your users simultaneously interact with a message you've sent.
- Mitigate deliverability issues that can occur when you're sending high message volumes.
When you send multiple campaigns of the same message type (with the same default send limit rate), they don't compete for the send rate limit's capacity. Each campaign can independently send as fast as the send rate limit allows.
However, when you send multiple campaigns that call the same data feed, they do compete for the data feed's send rate limit capacity. The total traffic to the data feed, from all campaigns, will not exceed the data feed's send rate limit.
- When a campaign has a send rate limit, Iterable doesn't necessarily send messages at that rate. But it won't exceed the send rate limit.
- If you turn on both Send Time Optimization and a send rate limit, your send rate limit could cause some sends to continue beyond your Send Time Optimization window.
- In situations where more than one send rate limit is applicable, Iterable uses the most restrictive limit.
Enabling a send rate limit
There are three ways to set a send rate limit in Iterable. You can:
Set a default send rate limit for each of your project's message types. Any new campaigns you create under each message type will follow the default send rate limit you've set.
Set a send rate limit for a data feed. Any campaigns that call the data feed will follow the send rate limit you've set for the data feed.
Adjust the send rate limit for an individual campaign. To do this, switch on the Set a Send Rate Limit toggle and enter the maximum number of messages Iterable should send during a specified period of time.
Apps built with Iterable's mobile SDKs use in-app display priority to help determine the display order for in-app messages. By default, the SDKs display higher priority messages first (sorted secondarily by send time — first sent, first displayed).
For example, you might use priority level in segmentation, to select users with In-App Send events of a particular priority:
- Low -
- Medium -
- High -
- Critical -
Proofs receive a
Transactional messages are sometimes urgent or sent as a response to a user action for which confirmation or further details may be necessary. Because of this, you should generally give them a higher priority than marketing campaigns.
The priority of an in-app message campaign cannot be changed after it has been sent. However, the priority of a scheduled campaign can be chaned before its send time.
Enabling display priority
To turn on display priority for an in-app campaign's recipients, switch on the Display Priority toggle and choose the priority level to apply to this campaign.