Dayparting is one of the simplest efficiency gains in an Amazon account. It is also easy to get wrong in ways that quietly cost sales. A bad schedule does not throw an error. It just removes orders from hours you did not look at closely, and the loss shows up weeks later as a dip nobody can explain.
This guide covers the mistakes that cause most of that damage: building schedules from thin data, reading the wrong time zone, pausing when a bid cut would do, and treating a schedule as finished. Each section ends with the fix.
Building the schedule from too little data
Hourly data is noisy. A campaign with a few dozen clicks per hour will show some hours with zero orders purely by chance. If the schedule is built from a week or two of data, those random dead hours look like real patterns, and the schedule pauses them.
The fix is more data and a minimum click threshold. Use at least four weeks, so each weekday appears several times. Ignore any hour that does not have enough clicks to judge. For small campaigns, group hours into blocks (for example, 1 a.m. to 5 a.m.) and judge the block instead of each hour. Reading hourly performance data walks through how to tell a real pattern from noise.
Reading hours in the wrong time zone
Amazon reports hourly data in the marketplace's time zone, not yours. A seller in Europe looking at a US account, or an agency spread across several time zones, can easily read "2 a.m." as their own 2 a.m. The schedule then pauses the wrong block entirely, sometimes the start of the evening peak.
Write the time zone at the top of every hourly sheet and every schedule. Check one known event, such as a spike after a promotion went live, to confirm the hours line up. Ad scheduling and time zones covers the details, including daylight saving changes.
Pausing hours that only need lower bids
Some hours are dead: clicks cost the same and almost nothing converts. Those should be paused. Many more hours are simply below average. They convert, just less well. Pausing them removes real orders and can also reduce the sales history that supports organic rank.
Reserve pausing for hours that are clearly weak with enough clicks to prove it. For hours that are merely soft, lower bids or budgets instead. Pausing versus lowering bids lays out where the line usually falls.
Using one schedule for every campaign
An account-level hourly curve is a blend. Branded campaigns often convert steadily across the day because the shopper already knows what they want. Generic discovery campaigns tend to have sharper peaks. Competitor and product targeting campaigns can behave differently again. A single schedule applied everywhere fits the average and none of the parts.
Start with the account view to find the obvious dead hours. Then check the largest campaigns individually. If a campaign's curve differs clearly from the account curve, give it its own schedule. Most accounts end up with two or three schedules, not one and not dozens.
A simple test helps here. Pick your three largest campaigns and lay their hourly conversion rates side by side. If the curves look alike, one schedule is fine for now. If one peaks two or three hours later than the others, or never really drops overnight, that campaign needs its own schedule. The check takes a few minutes and prevents most of the damage a blanket schedule does.
Ignoring the day of the week
A Tuesday at 10 p.m. and a Saturday at 10 p.m. are not the same hour. Weekend shopping often starts earlier in the day and runs at a different pace. A schedule built from all days blended together can pause Saturday mornings that convert well, or run Monday nights that do not.
Break the hourly view out by weekday versus weekend at minimum. If the two curves differ, use separate schedules. Day-of-week performance shows how to check this quickly.
Forgetting to turn campaigns back on
Manual dayparting depends on someone pausing campaigns at night and reactivating them in the morning. Pausing is easy to remember. Reactivating is easy to miss, especially on weekends and holidays. One missed morning can cost more than a month of savings from the night pauses, because the morning ramp leads into the strongest hours.
If schedules run by hand, put the reactivation step on a checklist and check campaign status at the start of every day. Better still, automate it so the schedule runs the same way every day without anyone remembering it.
Treating the schedule as finished
A schedule built in spring reflects spring shopping. Gifting seasons, back-to-school and sales events all shift when people buy. Hours that were dead in March can be productive in November. A schedule left untouched for a year is almost certainly wrong for part of it.
Review the schedule at least once a quarter, and before any major event. During big sales events, consider loosening the schedule or suspending it, since shoppers behave differently and the event hours may run late. Building a schedule from data covers the rebuild process, which takes far less time the second time around.
None of these mistakes means dayparting is a bad idea. They mean a schedule needs the same care as bids and budgets: built from enough data, read in the right time zone, checked against total sales, and reviewed as the year moves on.
Frequently asked questions
What is the most common dayparting mistake on Amazon?
Building the schedule from too little data. A week or two of hourly numbers is mostly noise, so the schedule ends up pausing hours that happened to have a bad few days. Use at least four weeks, and more for low-volume campaigns.
Should I pause every campaign on the same schedule?
No. Branded, generic and competitor campaigns often peak at different hours, and so do different products. Start with one account-level view, then adjust schedules for campaigns whose hourly curve differs clearly from the rest.
How often should a dayparting schedule be reviewed?
At least once a quarter, and before any major season or sales event. Hourly patterns shift with the season, and a schedule built in a quiet month can pause hours that matter later in the year.
Off Hours runs dayparting rules on a 15-minute cadence and logs every change, so campaigns pause and come back on schedule without anyone remembering to do it. Start a free 14-day trial.