Iterable allows you to send campaigns at a specific local time depending on the user. For example, a campaign can be delivered at exactly 9am Pacific, Eastern or Samoan time.
You can enable this feature if you provide either a
ip field for users. These fields are case and space-sensitive.
timeZone, the time zone will need to be formatted as described by Wikipedia's List of tz database time zones. Here's an example of how it would look in CSV:
ip, you will need to include the user's ip address. Here's the CSV example:
If you provide the
ip field in an import and have the Enable User IP to Location Lookup setting enabled, Iterable will automatically do a geoLookup and fill in the
timeZone fields on the user profile if this information is returned by the geo lookup.
You can send blast campaigns and workflow campaigns at a specific local time. In blast campaigns, you can choose this option in the final launch step of the campaign creation process.
Starting and fallback time zones for blast campaigns
When scheduling a blast campaign, you have the option to choose both a starting and fallback time zone (see below).
The starting time zone is used to determine when the campaign will start sending. No messages will be sent before the selected time in this time zone. Anyone with a
timeZone value that is east of the starting time zone (up until the international date line) will receive the email at this starting time.
The fallback time zone will dictate when users who do not have the
timeZone field set will be sent the campaign.
Say you set your email to send today at 3:00pm, with a starting time zone of
America/Chicago and a fallback time zone of `America/Honolulu``:
|Bob||San Francisco, CA||America/Los_Angeles||3pm PST/5pm CST|
|Sally||New York, NY||America/New_York||4pm EST/3pm CST||Sally is east of the starting time zone, so she is sent the email immediately at 3pm CT.|
|Wendy||San Francisco,CA||6pm PST/3pm HST||Wendy doesn't have a
Delaying a workflow until a specific time
In workflows, you can send at a specific local time by adding a delay prior to a message send node that will delay until a specific time: