Iterable can send blast campaigns and triggered campaigns:
- Blast campaigns are sent to a list of users (or multiple lists), and can be sent immediately or scheduled for the future.
- Triggered campaigns are sent when you make an API call (maybe in response to a user action in your app or on your website), or when a user reaches a particular place in journey.
This article explains how to send or schedule a blast campaign. You'll do this on the campaign review page, after verifying that your campaign is set up correctly.
A campaign's send time can also be affected by the delivery options you choose. For more information, read Optimizing Campaign Delivery.
In this article
Sending a blast campaign immediately
To send a campaign immediately after reviewing it, click Send Now.
A confirmation window appears, with a recipient estimate. With your confirmation, Iterable sends the campaign.
Scheduling a blast campaign
To schedule a campaign to send later, click Schedule. Then, configure options related to the scheduling of a campaign in the Schedule Campaign window.
Start date and time
The date and time (up to 21 days from today) when Iterable should send the
campaign. When entering a time manually, you can use a 12-hour format (
or a 24-hour format (
Send with respect to
Not available when Send Time Optimization is enabled
The time zone Iterable should use to decide when to send the campaign.
Project Time Zone — Your project's time zone, as defined in Settings > Project Settings.
Recipient's Time Zone — Send to each user based on their own time zone. To use this setting, you'll also need to specify a starting time zone and a fallback time zone:
Starting Time Zone - Iterable won't send messages before this time. Users with a
timeZoneto the east of the starting time zone (up to the International Date Line) will be sent the campaign after the scheduled time in their local time zone.
Fallback Time Zone - Iterable uses this time zone when sending a campaign to all users who do not have a
timeZoneon their user profile.
Sending in different time zones
To determine a user's time zone, Iterable looks at the
timeZone field on
their user profile. For example:
If you choose to send the campaign in the recipient's time zone, you can set a starting time zone and fallback time zone.
Starting time zone - The earliest time zone Iterable uses to send the campaign at the scheduled time. Users who are in time zones east of the starting time zone (up to the International Date Line) receive the message at the scheduled time in the starting time zone. No users will receive the campaign before the scheduled time according to your starting time zone.
Fallback time zone - The time zone Iterable uses if a user’s time zone isn’t listed on their user profile (in the
timeZone field name is case-sensitive and space-sensitive.
To have Iterable automatically populate a user's
ipuser profile field to each user profiles. This allows Iterable to populate their
To keep time zone information current, turn on these geolocation project settings:
Enable User IP to Location Lookup - With this setting on, when you populate a user's
ipaddress, Iterable also fills in their
Automatically Update IP in User Profile from Inbound Events - Causes Iterable to automatically capture a user's IP address each time they click a link in an email.
Time zone example
Consider a campaign scheduled to send today at 3:00 p.m., with a starting time zone of America/Chicago (Central Time) and a fallback time zone of America/Honolulu (Hawaii Time).
Users with a
America/Los_Angeles will be sent the campaign at
3:00 p.m. Pacific Time (5:00 p.m. Central Time). This is the campaign's
scheduled send time, in the user's local time zone.
Users with a
America/New_York will be sent the campaign at 4:00
p.m. Eastern Time (3:00 p.m. Central Time). This is the campaign's scheduled
send time in the campaign's starting time zone, since
America/New_York is east
Users without a
timeZone will be sent the campaign at 3:00 p.m. Hawaii Time.
This is the scheduled send time in the fallback time zone's local time.
If a campaign uses Send Time Optimization in a campaign, you can't choose to send the message using the recipient's time zone.
Blast campaigns can be scheduled to recur. This can be useful for sending static content (like a welcome message to users who have signed up in the last 7 days), or to send dynamic content to a users who expect to see it repeatedly (like a list of each week's live fitness classes sent to all subscribers).
When you set up a recurring campaign, all of the subsequent sends keep the same settings as the original. You can adjust these settings before each new send — just edit the child campaign before its scheduled send time.
Select the repeat options:
Daily, Weekly, Every Two Weeks, Every 30 Days - The campaign sends according to the selected schedule, starting on the first day scheduled. For Daily, you can also specify days you want to skip sending.
First of the Month, 15th of the Month, Last of the Month - The campaign sends on the selected day of the month.
Custom - The campaign sends according to the selected schedule, respecting days to skip sends.
- For all options, the campaign stops sending on the specified end date (if provided).
- Once you schedule a repeating campaign, you can't change it to Don't Repeat.
For recurring campaigns, you can specify an amount of time that Iterable should create the campaign ahead of send time, with a maximum of 24 hours. This can give you time to edit the campaign before it is sent.
Aborting a blast campaign
To prevent remaining sends of a blast campaign already in progress, click Abort Campaign.
Users to whom the campaign is not sent receive a Send Skip event on their user profile.
Before sending a blast campaign, verify that it looks right. For more info, see Reviewing a Campaign Before Sending.