Dayparting rests on a simple idea: run ads harder in the hours that convert and pull back in the hours that do not. The idea breaks quietly if the schedule and the data are on different clocks. A pause meant for 1 a.m. that actually fires at 4 a.m. cuts into the morning, and nobody notices because the rule appears to work.
This guide covers which clock your Amazon data runs on, how to think about shoppers spread across several time zones, what daylight saving does to schedules, and how to manage schedules across more than one marketplace.
Know which clock your data uses
Amazon Ads reports each marketplace in that marketplace's own time zone. The same clock decides when a new day starts for campaign budgets. If you sell on the US marketplace from Europe, or from the US East Coast, your reports and budget resets are not on your local time.
Check the time zone shown in the console or report settings for each marketplace before you build anything. Then make every schedule in that time zone. Converting by hand from your own time zone works until a holiday, a time change or a new team member gets it wrong.
One marketplace, several shopper time zones
A large marketplace covers shoppers in several time zones. The US spans four in the continental states alone. Sponsored ads do not let you target by the shopper's time zone within a marketplace, so any schedule you set applies to all shoppers at once.
That sounds like a problem, but the data already accounts for it. Your hourly report shows performance by hour on the marketplace clock, and each hour blends shoppers from every zone. If the 6 p.m. hour converts well, it is because the mix of shoppers active at that moment buys. The schedule should follow that blended curve.
What it does mean is that curves are flatter and wider than any single time zone would produce. The evening peak stretches across several hours as it rolls from east to west. Be careful pausing hours on the edge of the peak; they often hold the start or end of another zone's evening. Reading hourly performance data covers how to spot those shoulders.
Build the schedule on enough data
Pull at least four weeks of hourly data, so each weekday appears several times. Mark hours whose conversion rate is well below the daily average with enough clicks to trust. Those are the candidates for lower bids or a pause. Building a schedule from data walks through the full method.
Start with the clearest weak hours, usually the middle of the night on the marketplace clock, and leave the shoulders at normal or slightly lower bids. A partial bid reduction is safer than a pause in hours that convert near the average.
Daylight saving time
Daylight saving changes cause two kinds of trouble.
First, regions change on different dates, and some do not change at all. If you sell in the US and Europe, there are a few weeks each spring and autumn when the gap between the two is an hour different from normal.
Second, a tool may run on one clock while the marketplace runs on another. If the tool uses fixed UTC offsets and the marketplace observes daylight saving, the schedule drifts by an hour twice a year.
The fix is to schedule in the marketplace's named time zone, not a fixed offset, so time changes are handled automatically. After each change, look at the first week of hourly data and confirm pauses and peaks still line up. Shopper behavior can also shift slightly as daylight hours change, which is one reason to review schedules seasonally. Seasonal scheduling covers that review.
Multiple marketplaces
Each marketplace needs its own schedule on its own clock. A schedule built for the US will not fit the UK or Germany, both because the clock differs and because shopping habits differ by country. Lunch-hour browsing, commuting and evening peaks happen at different local times.
Build each schedule from that marketplace's hourly data. If one marketplace is too small to have reliable hourly data, keep it unscheduled or use mild bid changes until it does. Copying a large marketplace's schedule onto a small one, shifted for time zone, is a starting guess, not a plan. Dayparting across marketplaces covers this in more depth.
Agencies and remote teams
Agencies managing clients across regions, and teams spread across time zones, run into a human version of the same problem. A note that says "pause at midnight" means different things to different people. Write schedules in the marketplace's time zone, label it every time, and keep one shared reference for each client. A change log that timestamps every adjustment in the marketplace clock makes it easy to check what ran when.
A quick checklist
Confirm the time zone for each marketplace in the console. Build every schedule on that clock. Use four or more weeks of hourly data. Pause only clear weak hours and treat shoulder hours gently. Check alignment after each daylight saving change. Keep separate schedules per marketplace. Review every quarter.
Frequently asked questions
What time zone does Amazon Ads use?
Each marketplace reports in its own time zone, and that is also the clock campaign budgets reset on. Check the time zone shown in your console and reports for each marketplace you sell in, and build schedules on that clock rather than your local one.
How do I schedule Amazon ads for shoppers in different US time zones?
You cannot target ads by shopper time zone within a marketplace, so the schedule covers all shoppers at once. Build it from hourly performance in the marketplace's clock. That data already blends the zones together, which is what your schedule needs to match.
Does daylight saving time affect Amazon ad schedules?
It can. If the marketplace clock and your tool's clock change on different dates, or one changes and the other does not, a schedule can shift by an hour for part of the year. Use a tool that schedules in the marketplace's own time zone, and check your peak hours after each change.
Off Hours runs dayparting rules on a 15-minute cadence and logs every change, so you can see exactly when each schedule fired. Start a free 14-day trial.