Budget management helps you manage budgets in one place, track spending progress, and keep your monthly budget on pace. With Budget management, you can:

Budget groups come in two levels — profile level and campaign level, and only one level can be enabled per profile. See budget group levels below for a comparison.

Advanced Ads Settings → Budget Management.

We recommend reading the following concepts before getting started.

Budget management offers two budget group levels, each with a different control scope and a slightly different feature set:

The budget group list uses four metrics to describe how far along the spend is. Profile level and campaign level share the same definitions:

Note that a day on which the daily overspend stop was triggered is calculated normally — no special handling. That day's Delivery rate reads noticeably high, which is precisely the signal that spend reached the limit before the campaigns were paused.

Budget % for the objects inside a group is a live figure, recalculated from each object's current budget, so it always adds up to 100%. If you change a budget outside Budget management — on the All Sponsored Ads page, or on a campaign directly in Amazon's console — these shares move with it and redistribute.

A profile-level budget group is configured by selecting one of two operating modes:

Note: Profile-level budget groups do not support auto pacing. To let the system autonomously optimize pacing, create a campaign-level budget group instead.

The progress metrics for profile-level budget groups (Budget left, Budget left %, Days left %, Delivery rate) use the same definitions and formulas as campaign level. See "Progress Metrics on the List".

A campaign-level budget group is configured by combining three independent switches that control how much the system intervenes in budget and pacing:

The three switches can be turned on or off independently. Common combinations:

Once enabled, the system generates default shares from each object's current daily budget, and you can adjust them by hand. The daily budget calculated at the budget group level is then dispatched to each campaign and managed group according to those in-group shares. The system dispatches at the current shares in these moments: when you edit and submit settings on the budget group page (with only "Allocate budget by percentage" on, it dispatches the average daily budget derived from the in-group shares; with both "Daily scheduling" and "Allocate budget by percentage" on, it dispatches that day's budget × the current in-group share); and on the 1st of each month, when the system dispatches once at the shares currently set.

The shares are not locked in permanently. If you later change a campaign's daily budget outside Budget management — on the All Sponsored Ads page, or directly in Amazon's console — Budget management recalculates the shares from the latest budgets at the next edit, recalculation or dispatch, rather than reusing the values saved last time.

When auto pacing is on, the system operates as follows:

Adjustments happen at two layers:

Put simply, Auto pacing works out time first and space second: it splits what is left of the group's monthly budget into daily budgets from today through the end of the month (the time dimension), then redistributes that day's budget among the managed groups and campaigns inside the group (the space dimension).

One of Auto pacing's goals is to protect ROAS as far as possible. The Minimum ROAS Guardrail turns that into a line you set yourself: as ROAS approaches the line, the system eases off on spend and explains on the page that it is doing so.

Both values live on the AI-managed group. The Target ROAS is the goal you have already set there — no new target was introduced this release. The Minimum ROAS Guardrail (the Min ROAS Guardrail column on the list) is the new field, right beside it. The capability therefore has to be used together with AI management: if no managed group inside the budget group has AI enabled, there is nowhere to set the value.

It is worth being clear that the Minimum ROAS Guardrail is not "a lower target" — the target is still the Target ROAS, and the guardrail only decides when the system would rather leave budget unspent than let ROAS slip. The guardrail also needs the budget group's pacing goal in order to work, so it only takes effect on managed groups inside a budget group; once a managed group is moved out, the value no longer affects delivery.

You can set it in two places: inline on the list and in the managed group edit dialog. The validation rule is that the Minimum ROAS Guardrail must be at or below the Target ROAS. If you move one value past the other, the system corrects the value you just edited back to the boundary on blur and tells you it did.

We recommend setting this value explicitly. If you leave it blank, the system applies a default floor below the Target ROAS — in other words the guardrail behaviour is always on, the default is simply not shown on the page. To spend as much of the budget as possible, set the guardrail low; to put ROAS first, set it close to or equal to the Target ROAS.

The system works in three stages:

"Easing off on spend" here means reallocating budget inside that budget group — shifting the weighting between managed groups and manually run campaigns, adjusted continuously on performance, rather than dropping any one object to a fixed amount. ROAS takes priority over spending the budget.

A label next to Delivery rate shows which stage is active:

The label appears whenever the system is easing off for ROAS, not only once ROAS falls below the Minimum ROAS Guardrail. The reason is that delivery starts falling behind while ROAS is still inside the band, and without the label you would see the pace slow with no explanation for it.

On permissions, the Minimum ROAS Guardrail shares the same permission as Auto pacing; without it, the field is not shown.

When Auto pacing is on, all AI-enabled managed groups in the budget group automatically enter budget utilization mode, and it stays on for as long as auto pacing is on. This mode is designed to make sure the budget allocated by auto pacing actually gets spent:

Budget management and AI budget dayparting work at two different levels, so they do not conflict on pacing: Budget management decides how much a campaign should spend each day, while AI budget dayparting decides when during the day that budget is available — it redistributes the day's budget across hours based on recent hourly spending capability and ad performance, without changing the day's total.

There are two situations where budget management dynamically adjusts daily budgets based on the month's actual spend:

When the budget group contains a managed group with AI on, and its action psace has bid optimization or targeting optimization enabled, auto pacing shows an AI other controls column to indicate which AI actions may run alongside the budget adjustments:

Display rules:

Redistribution inside the group conserves the day's total — it changes only how the amount is split between objects, never the group's total for that day.

Optional switches, independent from the three switches above:

When auto start takes effect, you receive an in-app notification.

A second layer of protection on top of the monthly one, on a daily cycle: when the day's spend approaches or reaches the budget dispatched for that day, the system sets every active campaign in the budget group to paused, marked as "paused by budget group" in the same way.

It works for bare campaigns and AI-managed groups alike, with no difference in treatment, and the trigger is fixed — there is no threshold setting to configure.

"Daily scheduling" has to be on first. Without a budget for the day there is nothing to compare against, so the daily overspend stop cannot be enabled on its own; when you enable it, the dialog offers to switch on "Daily scheduling" at the same time.

Reactivation runs in the same cycle as the pause check, once every hour on the half hour:

Every trigger is recorded in the budget group's operation log, the list styles the overspend-paused state distinctly, and an in-app notification is sent.

About how much protection this gives you: spend data comes from reporting and runs about an hour behind, so the daily overspend stop is a supplementary safeguard against overspend. It does not promise minute-level response and cannot rule overspend out entirely. Amazon itself allows a campaign to spend up to 100% over its daily budget on a given day (that is, up to twice the amount), and that factor cannot be read through the API.

If there is remaining budget in the current month and a budget value is already set for the next month, the remaining budget from the current month is automatically added to next month's budget. To enable the rollover, set next month's budget in advance (see Create a Budget Group — Step 2).

Note when the rollover actually runs: because of spend-data attribution, the rollover is executed on the 4th day of the following month, not on the 1st. For the first few days of the new month you therefore still have the budget you set for that month, with the rolled-over amount folded in on the 4th.

Step 1: Select objects in the group

Step 2: Fill in basic info

Step 3: Configure operating mode

See Core Concepts for how each mode and switch works:

Step 4: More settings (optional)

After filling everything in, click Save. The budget group takes effect immediately and the system delivers today's budget under the current switch combination.

The following objects do not appear in the selection list: archived campaigns, campaigns or managed groups already in another budget group, and Sponsored Brands campaigns using the lifetime budget type.

The monthly calendar is shown when a profile-level budget group is in dynamic allocation mode, or when a campaign-level budget group has daily scheduling on. The calendar style depends on whether auto pacing is on:

Without auto pacing (profile-level budget groups always look like this; campaign-level budget groups look like this when auto pacing is off):

With Auto pacing on (campaign-level budget groups only):

Operations on the calendar:

Once every day in the month has been set by hand, editing one of those days again makes the system check whether the daily budgets add up to more than the monthly budget, and block the change if they do.

When you open the edit page of a campaign-level budget group, if daily scheduling is on, today and future dates show the budgets you previously set, not the post-reallocation result — so the numbers you see in the edit page match what you originally set.

To recalculate based on the latest spending data, click the Recalculate daily allocation button on the edit page. The system runs a full reallocation and updates today and future dates.

Trend chart: the chart at the top of the list offers five metrics — Spend, Planned budget, Delivery rate, Sales and ROAS — with monthly, weekly and daily granularity, a start and end month, and export to Excel.

Daily breakdown dialog: the entry point sits in the action area of each row on the list, beside the edit entry. The former budget group detail page has been retired and everything it did now lives here:

On the budget group list, the following actions are available on any row:

Numeric values can be edited directly on the list — the group budget, the shares and amounts of the objects inside it, Target ROAS and the Minimum ROAS Guardrail. All three entry points (group budget, a child row's share, a child row's amount) open the same whole-group edit mode, because these values are coupled: change one and the rows you did not touch rebalance automatically, so the total always stays at 100%. If a value falls outside the permitted range, it is corrected to the nearest valid value on blur with a message, and this does not block saving. The whole group is submitted in one save, and a budget dispatch runs immediately afterwards.

Switches require the edit page or a bulk operation — only Auto pacing can be toggled on the list itself; the other switches (Daily scheduling, Allocate budget by percentage, Notification, Overspend stop & auto-enable, Daily overspend stop) show their state on the list but cannot be changed there.

The budget group name and the objects inside the group are still changed on the edit page. Changes take effect under the new rules immediately.

Please note: if this budget group did not previously have "Allocate budget by percentage" switched on, editing the in-group shares on the list and saving switches it on — from then on the system dispatches each object's budget at the shares you set. If you only want to look at the data and do not want the system taking over the budget, do not edit the shares here. The change is recorded in the operation log.

Select multiple Budget Groups on the list to perform the following bulk operations:

Note: Bulk operations require that all selected budget groups belong to the same profile; cross-profile selections are blocked.

Budget Alert sends in-app notifications when the Budget Group's spending pace deviates from expectation, so you can react in time:

To enable, check Budget Alert on the Budget Group create or edit page. Xnurta sends a notification when the current month's actual spend progress deviates from the ideal progress by more than 50% (actual progress = month-to-date spend ÷ monthly budget; ideal progress is based on the daily budgets planned to date).

Note: Budget Alert only sends notifications; it does not change campaign budgets or statuses. To automatically respond to overspending, enable Overspend Stop; to actively manage pacing, enable Auto pacing.

Different control goals call for different switch combinations:

Auto pacing's budget adjustments and the managed group's AI action space are complementary — budget decides "how much to spend" while the action space decides "how to spend it more precisely".

We recommend treating auto pacing and the managed group's AI action space as a paired setup: turning on auto pacing alone limits AI to budget allocation only; turning on action space without auto pacing leaves pacing to you.

If you have also set a Minimum ROAS Guardrail, this pairing gains one more dial — it decides when the system would rather leave budget unspent than let ROAS slip.

Q: Can profile-level budget groups use auto pacing too?

A: Not currently. Auto pacing is available only for campaign-level budget groups. Profile-level budget groups use the two operating modes (Monitoring only / Dynamic allocation). To let AI autonomously optimize budget pacing, use a campaign-level Budget Group with Auto pacing on.

Q: When auto pacing is on, will the system change my budget automatically? At which levels?

A: Yes. With auto pacing on, the system recalculates today's actually delivered budget once per day, and may fine-tune in-group budget shares based on performance. All changes are recorded in the budget management operation Log.

Q: Will auto pacing conflict with daily scheduling?

A: They don't conflict, but they behave differently:

Q: I opened the budget group edit page and the budgets look the same as what I set yesterday — why hasn't the allocation been refreshed?

A: This is intentional in the new version — it prevents the numbers in the edit page from changing every time you open it, which would make it hard to tell "what did I originally set?". To refresh the allocation based on the latest spending, click the Recalculate daily allocation button on the edit page, and the system updates today and future dates.(for auto pacing off budget groups)

Q: Will auto pacing affect my managed group's bids or targeting?

A: Auto pacing itself only adjusts budget allocation. However, when Auto pacing is on, AI-enabled Managed Groups automatically enter Budget utilization mode, which can make AI optimization more aggressive and turns off AI Budget Dayparting and Budget Boost — see Budget utilization mode in Core Concepts.

Q: How do I know exactly what budgets the system changed, and which campaigns were affected?

A: Check the operation log on the budget group: the budget management page records group-level setting changes and overall delivery actions; the all sponsored ads log records each individual daily budget change a budget group made to a campaign (with the operator shown as "Budget Management"). Auto pacing on/off events and each delivery are logged.

Q: What if auto pacing's results don't meet expectations (e.g., budget under-spent or ROAS dropping)?

A: You can turn off auto pacing on the budget group list at any time, and return to manual or fixed pacing. To diagnose, combine the budget management operation log with ad management reports: if budgets are delivered but spend is still low, the issue is likely in ad competitiveness, bidding, or targeting — consider enabling the managed group's optimize base bids or keyword/ASIN harvesting action spaces. If spend rises but ROAS keeps dropping, consider lowering the monthly budget or rebalancing in-group budget shares.

Q: Why was my campaign suddenly paused?

A: Possible reasons: The budget group it belongs to triggered overspend stop, and active campaigns in the group were changed to paused with a "paused by Budget Group" mark — topping up the monthly budget with Auto Resume on restores them

Q: Will deleting a budget group also delete the campaigns inside?

A: No. Deleting a budget group only removes the budget group's control over its campaigns; campaigns keep their daily budget settings and statuses from before the deletion.

Q: Can a campaign belong to multiple budget groups at once?

A: No. A campaign can only belong to one campaign-level budget group. Also note that within the same profile, profile-level and campaign-level budget groups cannot be enabled at the same time.

Q: Why does the daily overspend stop require "Daily scheduling" to be on first?

A: The daily overspend stop compares the day's spend against the budget dispatched for that day. Without "Daily scheduling" there is no daily budget to serve as that baseline, so it cannot be enabled on its own. When you enable the daily overspend stop, the dialog offers to switch on "Daily scheduling" at the same time.

Q: With the daily overspend stop on, is overspend ruled out?

A: No — it is a supplementary safeguard against overspend. Spend data comes from reporting and runs about an hour behind, so minute-level response is not promised. Amazon itself also allows a campaign to spend up to 100% over its daily budget on a given day (that is, up to twice the amount), and that factor cannot be read through the API.

Q: What is the difference between the Minimum ROAS Guardrail and the Target ROAS?

A: The Target ROAS is the goal you want to reach; the Minimum ROAS Guardrail is the floor you do not want to fall through. Both are set on the AI-managed group — the Target ROAS being the value the managed group already had. The guardrail is not a lower target; it only decides when the system would rather leave budget unspent. While ROAS sits between the two, the system keeps spending but grows more conservative the closer it gets to the Minimum ROAS Guardrail; once ROAS falls below it, protecting ROAS comes first.

Q: What happens if I do not set a Minimum ROAS Guardrail?

A: The system still applies a default floor below the Target ROAS. The guardrail behaviour is always on; the default is simply not shown on the page. So if you have a firm requirement for a ROAS floor, we recommend setting the value explicitly rather than leaving it blank.

Q: If I edit the in-group shares on the list, does the system start taking over my budget?

A: Yes, and you are told before saving. If this budget group did not previously have "Allocate budget by percentage" switched on, editing the shares on the list and saving switches it on, and from then on the system dispatches each object's budget at those shares. If you only want to look at the data, do not edit the shares here. The change is recorded in the operation log.