Iterable allows you 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 "timeZone" or "ip" field for users. These fields are case and space sensitive.
For "timeZone", the time zone will need to be formatted as described here. Here's an example of how it would look in a CSV.
For "ip", you will need to include the user's ip address. Here's the CSV example:
Warning: 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 "city", "country", "region", "state" and "timeZone" fields on the user profile if this information is returned by the geoLookup.
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.
Blast Campaign - Starting and Fallback Timezones
When scheduling a blast campaign, you have the option to choose both a starting and fallback timezone (see below).
The "starting" timezone is used to determine when the campaign will start sending. No messages will be sent before the selected time in this timezone. Anyone with a timeZone value that is east of the starting timezone (up until the international date line) will receive the email at this starting time.
The "fallback" timezone 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 3pm with a starting timezone of America/Chicago and a fallback timezone of America/Honolulu...
|User||Location||timeZone field||Send Time||Note|
|Sally is east of the starting timezone, so she is sent the email immediately at 3pm CT.|
|Wendy doesn't have a timeZone on her user profile, so she is sent the email with the fallback timezone.|
Workflows - Delay Further Until 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: