Amazon Ads Automation: How All Four Rule Types Work Together.

Amazon campaigns have one default setting: always on. Spend the same budget across Monday morning and Friday night. Run the same schedule in January as in July. Apply the same logic whether ACoS is 18% or 42%.

Most accounts live in this default longer than they should. Not because the seller is not paying attention, but because fixing it manually, one campaign at a time, does not scale. You adjust a budget for an event and forget to undo it. You audit ACoS at the end of the month and find a campaign that has been bleeding for six weeks. You realize on a Tuesday that campaigns ran all weekend on a flat budget while your best traffic day came and went under-funded.

The four rule types in Off Hours are designed to solve exactly this. Each one addresses a different dimension of the same underlying problem: wasted Amazon ad spend. And they are designed to layer, not to conflict.

Rule 1: Dayparting

Dayparting rules control when your campaigns run. The rule watches the clock, and at the hour you set, it pauses or resumes your campaigns. No budget calculation, no performance evaluation. Time in, on or off out. The schedule enforces every 15 minutes.

What it solves: campaigns running 24/7 by default. For most product categories, the hours between 1am and 6am produce a fraction of the conversions that 7pm to 10pm do, but cost-per-click is often similar. You are paying for impressions in hours where almost nobody is buying.

A dayparting rule pauses campaigns at midnight, or 1am, or whenever your dead window starts. It resumes them in the morning. Automatically, every night, every weekend, regardless of whether anyone is watching the account.

When to use it: any account that has not audited its hourly conversion data. For most consumer categories, an overnight pause delivers an immediate ACoS improvement because you are simply cutting spend during hours that rarely produce sales. The full dayparting guide covers how to pull that data and set the window.

Rule 2: Budget Rules

Budget rules control how much your campaigns can spend during a defined window, and they restore the original budget when the window closes. That second part is what separates them from Amazon's native tools: Amazon lets you raise a budget manually. It does not automatically lower it back.

What it solves: one flat daily budget across seven very different days. Friday at 7pm and Monday at 9am do not perform the same way, but they often get the same allocation. A budget rule raises the ceiling on Friday at 6pm and restores it Monday morning. No manual edits, no forgotten increases left running.

The baseline snapshot pattern is what makes this work. When a budget rule fires for the first time, Off Hours captures the current budget as the baseline. When the window ends, it restores to that exact value. You are lending campaigns extra room to spend for a defined period, not permanently raising the floor.

Parkway Home used this pattern for their spring peak. Their top Sponsored Products campaigns regularly hit daily cap by mid-afternoon on weekends. A budget rule raised each campaign's ceiling by 35% from Saturday morning through Sunday evening. Sales volume increased because the campaigns could run through their best hours instead of going dark at 3pm.

When to use it: for predictable, recurring spend windows where demand exceeds your standard allocation. Weekends, peak days of week, pre-event periods. See budget rules for the full setup guide, how budget rules work for a deep dive on the baseline-and-restore cycle, and budget rules vs dayparting for a comparison of when each is the right tool.

Rule 3: Event Rules

Event rules handle tent-pole moments: Prime Day, Black Friday, Cyber Monday, product launches. You define a date range, set a ramp shape (build gradually, hold at peak, wind down after), and the rule handles budget automatically from start to finish.

What it solves: what we call the two-event problem. The first event is the sale itself. The second event is the teardown afterward. When BFCM ends at midnight, budgets need to come back down immediately. If nobody is watching the account at midnight, they do not.

Event rules treat the restore as part of the rule, not an afterthought. When the event window closes, the rule restores budgets to their pre-event baseline. Off Hours also runs a reconciler that verifies the restore happened and flags any campaigns that did not revert correctly.

The day-before notice is another guardrail: the evening before the event window opens, you get an alert confirming the rule is ready to fire. This is a deliberate check against rules that were built months ago and then forgotten.

When to use it: any predictable event where you want budget to increase, hold, and then restore cleanly. Read the full setup guide at event rules, or see how event rules work for a detailed walkthrough of the baseline snapshot, the restore sequence, and overlapping event handling.

Rule 4: Performance Rules

Performance rules are fundamentally different from the first three. Instead of scheduling based on time, they evaluate yesterday's settled data every morning at 6am, profile-local time.

What it solves: ACoS creep discovered at month-end. A campaign drifts from 22% to 38% ACoS over six weeks. Nobody catches it because no one is running a daily audit. By the time it shows up in a monthly review, real money has gone to a campaign that was already underperforming.

Performance rules check each campaign against its own baseline every morning. The response is graduated: an alert first, then a budget adjustment, then a pause if conditions warrant. Each step up the ladder requires more confidence before firing.

Why once daily and not every 15 minutes? Amazon's reporting has a 3-12 hour lag. Real-time performance data on Amazon is not real-time. Evaluating campaigns every 15 minutes on incomplete data would trigger false positives constantly. The once-daily schedule on settled prior-day data is the correct cadence for performance-based decisions.

When to use it: any account where ACoS or spend has drifted without detection. Start with alert-only rules. Give them two to four weeks of data before adding any budget adjustment or pause actions. Read more at performance rules, or see the full breakdown at how performance rules work.

Spend Alerts: the floor under all four

Spend Alerts are not a rule you configure. They are always on, included free on every account, and require zero setup.

Every account gets watched against a 14-day rolling baseline. If spend spikes, drops, or drifts past a threshold, you get an alert that names the culprit campaigns. You are not hunting through the account to find the problem. The problem finds you.

The distinction from performance rules: Spend Alerts watch the account-level picture across all campaigns. Performance rules enforce the thresholds you define explicitly per campaign. They are complementary. Spend Alerts catch the unexpected. Performance rules enforce the boundaries you set.

Think of Spend Alerts as the floor under everything else. Even before you have set up any rules, the floor is already there. See how Spend Alerts work for the full breakdown of what they watch, how the 14-day baseline is built, and how they complement rather than replace performance rules.

How all four layer on the same account

An account running all four rule types has layered coverage across every dimension of spend.

Here is how that looks for Northlane Goods, which runs Sponsored Products and Sponsored Brands across 14 campaigns in a competitive home goods category:

The rules do not step on each other because they operate on different inputs. Dayparting fires on time of day. Budget rules fire on date windows and recurring schedules. Event rules fire on defined calendar events. Performance rules fire on settled prior-day metrics. Spend Alerts watch the aggregate picture continuously. None of them are competing for the same decision.

To see what layering looks like in practice, walk through one of Northlane Goods's Sponsored Products campaigns during BFCM week. The campaign runs with a $120 standard daily budget. All four rules are active.

Friday, 5pm: The weekend budget rule fires. The campaign budget lifts from $120 to $150, the 25% boost configured weeks earlier. No one logged into the account.

Friday, midnight: The dayparting rule fires. All campaigns pause for the overnight window. The BFCM event rule has already elevated the event-period budget to $220, but pausing takes precedence. The campaigns go dark until the dayparting window reopens.

Saturday, 6am: Dayparting resumes all campaigns. The event rule budget of $220 is still the active ceiling. The campaigns come back online with significantly more room to spend than a normal Saturday. Performance rules have already run their 6am evaluation on the prior day's settled data. Two campaigns that crossed the ACoS alert threshold on Friday are flagged in the dashboard before the account team starts their morning.

Sunday evening: The weekend budget rule window closes. Off Hours restores the top-performer budgets from $150 back to $120. The BFCM event budget of $220 stays active through the end of the event window on Monday night.

Monday, just after midnight: The event rule's restore sequence fires. Budgets return to the pre-event baseline captured before the rule first ran. The reconciler confirms each restore and flags any campaign that did not revert correctly.

Each of those actions happened automatically, at the scheduled time, without anyone logging into the account or making a manual edit. The rules did not conflict because they were never trying to make the same decision at the same time.

What each rule type does NOT do

Understanding what each rule controls is as important as knowing what it does. The boundaries are intentional, and they matter for how you think about stacking all four.

Dayparting does not touch bids, budgets, or campaign settings of any kind. It only pauses or resumes campaigns. A campaign that gets paused during an overnight dayparting window still has the same daily budget, the same keyword bids, and the same targeting it had before. Dayparting changes one thing: whether the campaign is active. Nothing else.

Budget rules do not touch campaign pause/resume status or bids. They modify only the daily budget amount on the campaigns in scope. A campaign under a budget rule can still be paused by a dayparting rule without conflict. When the budget window closes, the rule restores the original amount to its captured baseline regardless of whether the campaign is currently running or paused.

Event rules do not create new campaigns, restructure the account, or change keyword bids. They work only on budgets and the schedule window you defined. Targeting, match types, ad copy, and everything else in the account stay exactly as you configured them. The rule activates when the event window opens and restores when it closes. That is the full extent of what it touches.

Performance rules do not act in real-time and do not compound across cycles. A rule that reduces a campaign budget on Monday morning re-evaluates against fresh prior-day data on Tuesday. It does not look at the Monday reduction and cut from there again. Each daily cycle runs against settled Amazon data, not against the previous cycle's output. This is deliberate: it prevents a reactive rule from compounding its own adjustments into corrections far more aggressive than you intended.

Where to start

The recommended order is not arbitrary. It follows the risk profile of each rule type.

Start with dayparting. An overnight pause is the lowest-risk, highest-return rule for most accounts. Set it up, watch it for a week, and confirm the ACoS improvement before adding anything else.

Add budget rules second. Once the schedule is stable, identify your first recurring spend window. A weekend boost or a pre-event increase is a good starting point. Watch how the restore behaves.

Build event rules third. Create the first event rule ahead of the next tent-pole date. Prime Day and BFCM are the obvious ones. A product launch works too.

Set up performance rules last. Start alert-only. Give the rules two to four weeks of data before adding any budget adjustment or pause action. The data will tell you whether the threshold you set is calibrated correctly before you let the rule do anything consequential.

Spend Alerts are already running. Nothing to configure.

For a broader look at how to think about what to automate, read Amazon PPC automation: what to automate and what to keep manual. For a side-by-side comparison of when budget rules versus dayparting rules are the right choice, read budget rules vs dayparting rules. If you want to build any of these rules without manual configuration, the AI rule builder lets you describe the rule in plain English and reviews what it built before anything runs.

Off Hours gives you all four rule types plus always-on Spend Alerts, at $149 per account per month. Start a free 14-day trial, no credit card required.