Budget rule

A Budget rule does one of two things, chosen under Action:

• Raise a budget cap — when spend keeps reaching a cap, raise it, never above the rule’s ceiling.
• Add the next flight to the Order — when the running flight is about to end, add the next one.

Create one under Automation Rules › Budget › New Rule. Both act only on orders and line items that are Enabled: something paused spends nothing, so there is nothing to raise or extend.

Both spend more money than doing nothing. Read Preview before switching one on.

Raise a budget cap

Which cap

Cap	Applies to
Order daily cap · Order monthly cap	The order’s daily or monthly cap
Line item daily spend cap · Line item monthly spend cap	A Standard line item’s spending limit. Performance+ line items have none

The rule only raises a cap that already exists. An order or line item without that cap is skipped: “the rule never adds a cap.”

When

“Spend is total cost minus the Amazon DSP fee, by finished day in the advertiser’s time zone. Days are compared with the current cap.”

Cap	The rule acts when	To start with
Daily	Spend reaches X% of the cap on at least N of the last M finished days (M up to 14)	85%, on 2 of the last 3 days
Monthly	Month-to-date spend reaches X% of the cap’s pace — “monthly cap × days passed ÷ days in the month”	85%

X is 1% to 100%. “100% means spend is on track to use the whole cap.” A monthly cap is not checked on the first day of the month.

Because past days are compared with the current cap, a day that reached the old cap counts for less after a raise. One busy stretch does not raise the cap again and again.

You can add up to 10 conditions under And these are true (optional) — for example, raise only while ROAS ≥ 2. They use their own Look back, Skip latest days and Minimum impressions, which apply only when there are conditions.

Then

Setting	Limits
Raise by	Percent, 1% to 200%, or Amount, $0.01 or more
Never above ($)	Required. The cap never goes higher. There is no starting value — you enter it
At most (raises per 7 days)	1 to 7; 2 to start with
Cooldown (days)	0 to 90; 3 to start with

A cap already at or above the ceiling is left alone: “Cap is already at the rule’s ceiling”.

“A higher cap lets Amazon spend more each day. Flight budgets are not changed, so the Order still stops at its flight budget. Automation only raises caps; lower them by hand in DSP Manager.”

A raised cap can be rolled back.

Add the next flight to the Order

When

“The running flight ends in at most” N days — 1 to 30, 5 to start with — “Only when the Order has no flight after the running one. Orders whose flights have all ended are left alone.” An order whose flights have all ended may have stopped on purpose, so it is never extended.

Optional conditions work as for a cap.

Then

Setting	Choices
New flight runs	To the end of that month, As long as the running flight, or A number of days (1 to 366). It starts the day after the running flight ends
Budget	Same daily rate as the running flight, Running flight’s daily rate ± % (−90% to +200%), or A fixed amount
Lowest budget ($) · Highest budget ($)	Required. “The new flight’s budget always stays within these two.”
Stop by	Optional date. No flight the rule adds ends after it
At most (flights per Order)	Optional, 1 to 24. “Counts every flight DSP Automation added to the Order” — from any rule
Cooldown (days)	At least 1, so the same flight is never added twice. 1 to start with

Set Stop by, At most, or both — the rule won’t save without one, “so the rule does not add flights forever”. A new rule starts at 3 flights per Order.

Daily rate means the running flight’s budget per day × the new flight’s days. A few days to the end of a month get a few days’ budget, not the whole flight’s.

What to know before switching it on

• Flights it adds cannot be removed — not by Vendlen, not by rollback. Change or shorten them in Amazon DSP.
• On a seat managed by Vendlen, each new flight needs enough balance, as when you add a flight by hand. Without it the flight is skipped: “Not enough money in the wallet for this flight”, with the largest budget you could set.
• Before adding a flight, a run reads the order from Amazon DSP. If the running flight changed or is no longer the last one, nothing is added.