Campaign time zone and lead-level time zones

Draft — written from product facts + domain knowledge; UI labels to be verified before publishing.

A campaign's time zone comes from its sending schedule: every send window, day selection and holiday rule is evaluated in that zone. That is fine when all leads are in one region. When a single campaign targets several regions, you can give each lead its own time zone so the send window is applied in the lead's local time instead. This article explains both levels and how they interact.

Campaign time zone

Set on the sending schedule (Campaign Settings → Sending Schedules → schedule → time zone) and applied to the campaign in its Settings.
Governs when the campaign is allowed to send, when the daily new-contacts limit resets, and how the start date is interpreted.
If a lead has no time zone of their own, this is the zone used for them.

Lead-level time zones

A lead time zone overrides the campaign zone for that lead only. The send window stays the same (for example 08:00–17:00) but is applied in the lead's local time.

Steps: set time zones from your CSV

Add a column such as timezone to your CSV. Use IANA names (America/Chicago, Europe/Paris, Asia/Tokyo), one per lead.
Upload the file via Contacts → Upload Contacts or inside the campaign via Upload new CSV.
On the column-mapping screen, map the column to the Time zone field.
Complete the import.

Steps: set a time zone on one lead

Open the campaign → Contacts and click the lead.
Edit the Time zone field in the lead details and save.

Which approach to use


Situation	Approach
All leads in one region	Campaign schedule only
Two or three regions, distinct copy per region	Separate campaigns, one schedule each
Many regions, same copy	One campaign with lead-level time zones

Tips

If you do not have a time zone column, derive one from country or city before uploading; a spreadsheet lookup table handles 95% of leads.
Lead time zones do not change the days of the week or the holiday calendar; those still come from the campaign schedule. If you send to Australia and the US from one campaign, holidays for only one country are skipped.
Mailbox capacity is shared across all zones. A campaign with leads in Sydney and New York effectively sends around the clock, so the per-mailbox daily limit is what keeps volume in check.

Troubleshooting

Lead received an email at 3 am local time: the lead has no time zone set and the campaign zone is far from theirs. Add a lead time zone or split the campaign.
Time zone column did not map: values are not valid IANA names (for example EST or GMT+1). Replace them with America/New_York, Europe/Berlin, and so on.

Create a sending schedule (time zone, holidays, days, send windows)
Manage multiple sending schedules and apply one to a campaign
Handle duplicates and map CSV columns to contact fields
Daily sending limits: mailbox limit vs campaign limit

Was this helpful?

More in Campaigns: Schedule & Options

Create a sending schedule (time zone, holidays, days, send windows)→Manage multiple sending schedules and apply one to a campaign→Set the daily new-contacts limit for a campaign→Choose a sending strategy: follow-ups first, balanced, or new leads first→Schedule a campaign start date→Auto-match ESP: send from a mailbox that matches the recipient's provider→Bounce protection: auto-pause a campaign at a bounce-rate threshold→Daily sending limits: mailbox limit vs campaign limit→Inbox rotation: how OutreachFox spreads sends across mailboxes→Open tracking and link tracking (and when to turn them off)→CC and BCC on campaign emails→Why did my campaign pause or stop sending? (all reasons in one place)→