Most advice about Amazon PPC automation stops at the philosophy: automate the repetitive work, keep the strategy human. That is the right frame, and we have written about where the line between automation and judgment actually falls. But it leaves an obvious question unanswered. Which rules do you actually build, and in what order?

This is the catalog. Eight automation rules that cover the work nearly every account needs handled, with the specific conditions, thresholds, and order that matter. Build them in roughly this sequence. The first three will do most of the heavy lifting.

Northlane Goods runs 11 Sponsored Products campaigns across three product lines. Before setting up automation, their account manager spent roughly two hours every Monday manually adjusting bids and budgets based on the weekend numbers, and still regularly missed campaigns burning spend on overnight hours that had never once converted. After building this rule set, the Monday session dropped to a 20-minute review. The rules handle the mechanical execution. The time goes to strategy.

First, the three action types

Every automation rule does one of three things, and the risk scales with each. Alert rules notify you and change nothing. Completely safe, and a good way to test a condition before you trust it. Adjust budget rules move spend up or down and restore the original value when the window ends. Medium risk. Pause rules stop a campaign from running. This is the destructive one, and it deserves the most caution.

A good automation setup uses all three, but it earns its way up the risk ladder. Run an unfamiliar condition as an alert for one to two weeks. Watch what it catches. Then promote it to an adjust or pause rule once you are confident in the signal.

Action type
Risk level
Alert — notify only, no change
Lowest risk. Always safe to start here.
Adjust budget — raise or lower spend, restore at end of window
Medium risk. Reversible. Watch the baseline snapshot.
Pause — stops campaign from running
Highest risk. Start as alert first, promote only after trust is built.

The eight rules, at a glance

Rule Action type
1. Overnight dayparting pausePause
2. Peak-hour budget boostAdjust budget
3. Daily budget capAdjust budget
4. Top-performer budget releaseAdjust budget
5. Event ramp for tent-pole salesAdjust budget
6. ACoS ceilingPause or alert
7. Zero-sale spend guardrailPause or alert
8. Under-utilization alertAlert

Build top to bottom. Rules 1 through 3 deliver most of the savings. Rules 6 and 7 are your safety net. Rule 8 keeps you informed.

1. Overnight dayparting pause

Rule condition IF: time is between [your overnight floor] and [your morning threshold]
THEN: pause all active campaigns

The highest-return rule for most accounts. Pause campaigns during the overnight hours that historically convert poorly, then resume them in the morning. If your products almost never sell between midnight and 6am, every click you pay for in that window is close to pure waste.

What threshold to use: Start with midnight to 6am. Then pull 30 days of hourly data and adjust. Some categories convert late. Some have international buyers active overnight. Your data tells you your actual dead hours, not someone else's. The full setup is in the dayparting guide, and the wasted-spend audit shows how to find your specific dead hours.

Watch out for: Setting too wide a pause window too fast. Start conservative — midnight to 6am — then expand if the data supports it.

2. Peak-hour budget boost

Rule condition IF: time is within your peak conversion window
THEN: increase campaign budget by [X]% for that window

The mirror of rule one. If you know the hours when your products convert best, lift the budget during those hours so you are not capped exactly when demand is highest. A campaign that hits its daily cap at 2pm leaves your best evening hours completely unfunded.

This rule raises the ceiling for the peak window and restores the baseline afterward, so you are spending more only during the hours that earn it. Your peak hours are in your hourly campaign data. Look for the windows where your conversion rate is 1.5x or higher than your account average.

3. Daily budget cap

Rule condition IF: campaign spend reaches [planned daily limit]
THEN: pause until the next day

A simple pacing guardrail. A sudden traffic spike or a bidding war should not blow through your budget before you notice. Paired with rule two, you get a floor and a ceiling: more budget during the conversion window, hard stop when the daily plan is spent.

4. Top-performer budget release

Rule condition IF: campaign ACoS is below [target] AND budget utilization is above 90%
THEN: increase budget by [X]%

The opposite problem of rule three. Some campaigns deserve more money than your default cap allows. This rule watches for campaigns that are fully using their budget while staying under target ACoS — the clearest signal of a campaign being starved — and releases more spend automatically. Budget rules cover this pattern in depth, including how the baseline snapshot restores the original value when the condition clears.

5. Event ramp for tent-pole sales

Rule condition IF: date is within [event window]
THEN: increase budget by [X]% for the event duration

Prime Day, Black Friday, a product launch, a back-to-school peak. These events justify a temporary, shaped budget increase. Set this rule once, in advance, and the budget scales for the event without you managing it at 2am when it goes live. The right shape is a ramp: increase before the event, peak during it, taper after. Our Prime Day dayparting guide shows this shape in practice.

6. ACoS ceiling

Rule condition IF: campaign ACoS on prior full day exceeded [target x 1.3] AND spend above [minimum threshold]
THEN: alert (first 4 weeks) — then promote to pause

Your first reactive performance rule. When a campaign's ACoS stays above your target, something is wrong. Trigger on a single bad hour and you will pause healthy campaigns over noise. Trigger on a full prior day above a calibrated ceiling and you catch real problems.

Why the 1.3x multiplier on the trigger: ACoS has natural daily variance. Setting the ceiling at exactly your target fires too often and creates alert fatigue. Start at 1.3x. If you are getting too many alerts on campaigns that recover on their own, widen to 1.5x. Start with alert-only for the first four weeks — confirm the rule is catching campaigns you would actually want to pause before you let it act autonomously.

Performance rules should evaluate once daily, not hourly. Amazon's advertising reports lag by several hours. An hourly performance rule reacts to incomplete data and will make bad decisions. If you are not sure what your ACoS target should be, start with what counts as a good ACoS and how to bring a high one down.

7. Zero-sale spend guardrail

Rule condition IF: campaign spend on prior day exceeded [threshold] AND sales = 0
THEN: pause (or alert)

The bluntest safety net and one of the most valuable. This catches the failures an ACoS rule misses — a campaign with no sales has no ACoS to measure at all. Set the threshold high enough to allow normal launch variance. A mature campaign that spent $60 yesterday and generated zero sales is broken. A new campaign with few impressions may legitimately spend a small amount and convert nothing on day one.

8. Under-utilization alert

Rule condition IF: campaign spend is below [X]% of daily budget for 2+ consecutive days
THEN: alert

The one pure-alert rule on this list. It flags campaigns spending far below their budget — usually because a bid is too low to win impressions or a keyword has gone quiet. There is no automatic fix, because the right response depends on context only you have. The rule's job is to surface the campaign before it sits invisibly under-delivering for weeks.

The mistakes that break automation setups

Common mistake
What actually happens
Rules that contradict each other (budget boost and ACoS pause on same campaign)
Unpredictable behavior. The campaign flickers between states and you cannot diagnose why.
Performance rules set to fire hourly
Decisions made on data 3 to 12 hours behind reality. Campaigns pause and restore all day based on stale numbers.
Skipping the alert phase
A pause rule fires on day one and takes down a healthy campaign. No trust has been built in the signal.
Zero-sale threshold too low on launch campaigns
New campaigns with no purchase history get paused before they have data to learn from.

The order matters more than the count

You do not need all eight on day one. Turn on the overnight pause, watch it for a few days, then layer in the budget rules, then add the performance guardrails last. Most accounts settle at five to eight rules and stay there.

The point is not to remove yourself from your account. It is to hand off the work that runs on a clock or a clear threshold, so your attention goes to the decisions that need a human: campaign structure, target setting, launch strategy, and reacting to the market. For agencies managing many accounts, this same rule set is what makes the mechanical layer scale without adding headcount.

Frequently asked questions

What are Amazon PPC automation rules? Conditions you set once that adjust your campaigns automatically — covering schedules (pause overnight, boost at peak hours), budgets (raise on top performers, restore at the end of a window), and performance triggers (pause or alert when ACoS or spend cross a threshold). The rule enforces a decision you already made, so the routine work happens on time every time without you watching the account.

Which Amazon PPC automation rule should I set up first? Start with an overnight dayparting pause. It is the lowest-risk, highest-return rule for most accounts — campaigns stop running during the hours that historically convert poorly, so you stop paying for clicks that rarely turn into sales. Once it is stable and you have watched it for a week, add an ACoS ceiling as an alert and a zero-sale spend guardrail.

Are automated pause rules safe for Amazon campaigns? Pause is the most destructive action type, so it needs guardrails. Start any new pause condition as an alert-only rule. Use a sustained condition (prior full day, not one hour). Evaluate performance rules once daily to account for Amazon's reporting lag. And set a meaningful minimum spend threshold so the rule does not fire on statistically insignificant data.

How many automation rules should one Amazon account have? Most accounts run well on five to eight rules. More is not better. Overlapping rules that contradict each other — one raising a budget while another pauses the campaign — cause more confusion than the spend they save. Keep the set small and make each rule's job obvious.

What is the difference between a scheduling rule and a performance rule? A scheduling rule fires on time — it does not care how the campaign is performing. A performance rule fires on a metric. The combination of both gives you coverage for two completely different failure modes: running at the wrong time, and running at the wrong cost.


Off Hours lets you build all eight of these rules in plain English — no scripts, no spreadsheets. Scheduling, budgets, and performance triggers in one place. Start a free 14-day trial.