Documentation
Learn how to configure capture schedules, timezones, trigger windows, and cloud storage — from first setup to production workflows.
Browse sections
Need help?
Contact SupportTimezones
Your schedules run in your selected local time — not in hidden server UTC. This keeps automation correct through daylight saving changes and ensures “9:00 AM” always means 9:00 AM in the region you care about.
When you schedule “9 AM”, it should run at 9 AM where your audience is — not after you mentally convert time offsets. That’s why we use full timezone IDs like America/New_York and Asia/Tokyo.
Popular timezones
You don’t need to memorize timezone IDs — just start typing your city/region and select the best match.
America/New_York
EST / EDT
America/Los_Angeles
PST / PDT
Europe/London
GMT / BST
Europe/Paris
CET / CEST
Asia/Tokyo
JST
Australia/Sydney
AEST / AEDT
How timezone selection works
- 1You pick a timezone on the schedule (or in account settings, depending on your workflow).
- 2We store the timezone ID with the schedule (e.g., America/New_York).
- 3At runtime, we convert it to UTC only for execution — your schedule still “thinks” in local time.
- 4Daylight saving adjustments are handled automatically by the timezone database.
Best practices
Use city-based IDs
Choose America/Los_Angeles instead of UTC-8. City IDs handle DST correctly.
Match the audience region
Monitor pricing, banners, and promos in the timezone where customers see them.
Separate schedules by region
If the same URL changes by region, create separate schedules per timezone.
Pair timezone with location
Timezone controls “when”, data center/location controls “from where”. Use both for best accuracy.
FAQ
What happens during daylight saving changes?
Your “9 AM” schedule stays at 9 AM local time. When clocks move forward/back, we adjust the underlying UTC execution time so the local schedule remains stable.
Can I change the timezone later?
Yes. When you update a schedule’s timezone, future runs respect the new timezone. Past captures remain as they were.
Should I use UTC for everything?
Use UTC only if your organization explicitly standardizes on it. For customer-facing monitoring, city-based timezones are usually clearer and easier to reason about.