Core Features
140+ Supported Timezones
Your schedules run in your local time — never in some hidden server UTC. We use timezones so jobs stay correct through daylight saving changes and relocations.
When you schedule “9 AM”, it should run at 9 AM where your audience is — not at a random converted UTC time. That’s why every schedule uses a full timezone like America/New_York or Asia/Tokyo.
Popular timezones
You don't have to memorize timezone IDs — just start typing your city or region name and we'll suggest the right one.
The full list appears during My Account - Time Zone - just start typing your city, like "New_York", "Berlin", or "Sydney".
How timezone selection works
- You choose a specific timezone from My Account.
- At runtime, we convert that to UTC only for internal execution.
- Daylight saving changes are handled automatically by the timezone database.
Best practices
- Always use a city-based timezone (
America/Los_Angeles), not fixed offsets likeUTC+2. - Schedule captures in your audience's timezone (e.g. EU for cookie banners, US for pricing).
- Use separate schedules if you monitor the same page for different regions.
FAQ
What happens during daylight saving changes?
Your "9 AM" schedule stays at 9 AM local time. When the clocks move forward or back, we adjust the underlying UTC time so that the local time remains the same.
Can I change the timezone later?
Yes. When you update a schedule's timezone, future runs will respect the new setting.