> For the complete documentation index, see [llms.txt](https://docs.sellermagnet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sellermagnet.com/ppc-management-beta/ppc-manager-overview/ppc-planning.md).

# PPC Planning

Forecast strategy changes against your real 30-day performance with the Scenario Simulator, then schedule campaign moves for a future date and time with the Campaign Mover.

{% hint style="info" %}
**Difficulty:** 🟡 Intermediate · **Reading time:** \~16 min
{% endhint %}

{% hint style="success" icon="rocket" %}
**Open this page in your dashboard:** [**Go to PPC Planning →**](https://dashboard.sellermagnet.com/ppc/planning)
{% endhint %}

{% hint style="warning" icon="triangle-exclamation" %}
**BETA:** The PPC Manager is currently in beta. Some features may behave unexpectedly or change based on user feedback. Please report any issues at <info@sellermagnet.com>.
{% endhint %}

## 📋 Overview

![SellerMagnet PPC Planning - Scenario Simulator screenshot](https://4139654583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fih2knSvVpBcq5rIeXVjM%2Fuploads%2Fgit-blob-fa04ed51b5755a5f158dd23f251c07eb20a0c616%2Fppc-planning.png?alt=media)

![SellerMagnet PPC Planning - a +20% budget scenario simulated, showing the projection vs baseline](https://4139654583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fih2knSvVpBcq5rIeXVjM%2Fuploads%2Fgit-blob-71a165681b037e15747951effc36e6f768d443d5%2Fppc-planning-2.png?alt=media)

**PPC Planning** is the forward-looking half of the PPC Manager. Instead of changing bids and budgets live and hoping for the best, you model the change first, then schedule the winners for a set date and time. You will find it in the sidebar under the **AI & Planning** group, right below the AI Optimizer. The page header reads "Forecast and schedule before you commit".

PPC Planning is part of the PPC Manager and needs a connected Amazon Advertising account. Without one, the page shows a **Connect Your Amazon Advertising Account** banner with a **Go to Settings** button, and the buttons that need a connection (**Run simulation**, **Save scenario**, **Schedule change**) are dimmed and cannot be clicked.

In practice it looks like this: it is early November and you want to push harder for Black Friday. You open **Scenario Simulator**, drag the budget lever to +30%, and see a projected 30-day spend, sales, ACoS (Advertising Cost of Sale) and ROAS (Return on Ad Spend) side by side with your real last-30-days baseline. The numbers look good, so you switch to **Campaign Mover** and schedule your main campaign to raise its daily budget at 07:00 your local time on November 24. The change is recorded as pending, it shows up in the Up-next banner, and you can cancel it until its apply time.

The page has two tabs, each a self-contained tool:

| Tab                    | What it does                                          | When to use it                                  |
| ---------------------- | ----------------------------------------------------- | ----------------------------------------------- |
| **Scenario Simulator** | What-if forecasting against your real baseline        | Before you commit to a budget or bid strategy   |
| **Campaign Mover**     | Schedule a campaign change for a future date and time | When a change should apply at a specific moment |

Tabs work like any tab bar: click one, or focus a tab and use the arrow keys, **Home** and **End**. The page remembers your last tab for as long as the browser tab stays open, and you can link straight to a tab with `?tab=scenario` or `?tab=mover` on the page address.

At the top of the page, three header stats track your planning activity at a glance:

| Stat                  | Meaning                                                       |
| --------------------- | ------------------------------------------------------------- |
| **Saved scenarios**   | Number of scenarios you have saved for this project           |
| **Scheduled changes** | Campaign Mover changes still pending (not yet applied)        |
| **Applied (30d)**     | Scheduled changes with the status Applied in the last 30 days |

***

## Scenario Simulator

The Scenario Simulator projects the next 30 days of performance if you were to change your strategy, and compares it against your real last-30-days baseline. Nothing you do here touches Amazon: it is a pure forecast you can run as many times as you like.

### Strategy levers

The left card holds three sliders. Adjust at least one, then click **Run simulation**. Any non-zero value counts, including negative ones. If every slider is still at its starting position, the page shows the message "Adjust at least one slider to simulate."

| Lever             | Range         | Step | What it models                                       |
| ----------------- | ------------- | ---- | ---------------------------------------------------- |
| **Budget change** | -90% to +200% | 5    | Scale campaign budgets up or down by this percentage |
| **Bid change**    | -75% to +200% | 5    | Raise or lower keyword bids by this percentage       |
| **Target ACoS**   | off to 60%    | 1    | Simulate autopilot bidding down toward a target ACoS |

The Target ACoS slider is labelled "off", "30%" and "60%" along its axis. Here you pick a percentage on the slider, which is different from the Campaign Mover's Target ACoS field (see [Step 4](#building-a-scheduled-change) there), where you type a decimal.

{% hint style="warning" %}
**Target ACoS overrides bid change.** When you set the Target ACoS lever above 0, the simulator models autopilot adjusting your bids toward that target and ignores the manual Bid change slider. Use one approach or the other, not both. Leave Target ACoS at "off" if you want to steer bids by hand.
{% endhint %}

{% hint style="info" icon="lightbulb" %}
**A budget change only moves spend where the budget is the limit.** Raising or lowering a daily budget only changes the spend of campaigns that are actually held back by their daily cap today. A campaign that is not using its full budget keeps spending what it spends now, whatever its cap says. The simulator therefore applies the Budget change slider only to the share of your spend that comes from budget-limited campaigns. See the warnings below for how the page tells you when this applies.
{% endhint %}

### Quick scenarios

Above the levers, three preset chips fill the sliders for you so you can go straight to a run:

| Preset                | Sets                                |
| --------------------- | ----------------------------------- |
| **Model +20% budget** | Budget change +20%                  |
| **Target 25% ACoS**   | Target ACoS 25%                     |
| **Conserve cash**     | Budget change -30%, Bid change -15% |

There is also a one-click **Preview a +20% budget scenario** button in the empty result panel. It sets Budget change to +20% for your whole account (it is not tied to any single campaign) and runs the simulation for you.

### Reading the projection

After you run a simulation, the right card fills with a **Projection vs baseline** block, subtitled "Next 30 days · last 30 days baseline". Every metric shows your baseline value, an arrow, the projected value, and the change between them. The projection covers the next 30 days; the baseline is your real last 30 days.

| Metric          | What it tells you                                    |
| --------------- | ---------------------------------------------------- |
| **Spend**       | Projected ad spend vs your recent spend              |
| **Sales**       | Projected ad-attributed sales                        |
| **ACoS**        | Projected advertising cost of sale (lower is better) |
| **ROAS**        | Projected return on ad spend (higher is better)      |
| **Orders**      | Projected ad-attributed orders                       |
| **Clicks**      | Projected clicks                                     |
| **Impressions** | Projected impressions                                |
| **CPC**         | Projected average cost per click                     |

When you have at least 7 days of daily history, each metric also shows a **Likely range** (a low and a high value). Hover over it for the tooltip: "Likely range from your own day-to-day history, not a guarantee." The range is built from your own day-to-day ups and downs, so a wide range means your results swing a lot from day to day.

Under the metrics, a footnote reads "Projection for the next 30 days vs last 30 days baseline." with the confidence badge next to it. When the bid projection uses your own measured response to past bid changes, a second footnote adds "Bid impact calibrated from your own bid history."

### Confidence badge and warnings

Two signals help you judge how much to trust the numbers.

**Confidence badge.** The badge reads **Low confidence**, **Medium confidence** or **High confidence**. It does not measure how noisy your data is. It starts from the length of the baseline window, and the page always uses a 30-day baseline, which starts at High. The badge is then lowered by the size of the change you ask for:

* One level lower: a Budget change or Bid change slider above +100%, or projected clicks that differ from your baseline by more than 75% (up or down). The warning "Confidence reduced - large change requested" appears.
* Two levels lower: projected clicks that differ from your baseline by more than 150%. The warning "Confidence reduced - extreme change requested" appears.
* Low confidence on its own appears when your baseline has no spend or no clicks at all (see "insufficient baseline" below).

In other words, a moderate change on an account with 30 days of traffic reads High, and Medium or Low mostly tells you "this is a big move, treat the number loosely". Use the Likely range to judge how steady your results are.

**Warnings.** Short flags above the metrics tell you when something limits or changes the projection:

| Warning as shown                                                                                    | What it means                                                                                                                                                                                                                                                                                                                   |
| --------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Mixed currencies in baseline - totals are a cross-currency blend**                                | Your baseline includes more than one currency, so totals add different currencies together.                                                                                                                                                                                                                                     |
| **Confidence reduced - large change requested** / **Confidence reduced - extreme change requested** | The change you asked for is large; the confidence badge was lowered (see above).                                                                                                                                                                                                                                                |
| **budget partially utilised**                                                                       | Only some of your spend comes from campaigns held back by their daily budget, so the Budget change moves spend by less than the slider suggests.                                                                                                                                                                                |
| **budget not utilised**                                                                             | None of your spend is held back by a daily budget, so a budget change is not projected to change spend. The page adds the note "Higher budgets alone are not projected to increase delivery. Review campaign status, bids, targeting and product eligibility before increasing spend limits." with a **Review campaigns** link. |
| **already at or below target**                                                                      | Your Target ACoS is at or above your baseline ACoS, so there is nothing to bid down and no bid effect is modelled.                                                                                                                                                                                                              |
| **no baseline acos for target**                                                                     | Your baseline has no ACoS to compare the target with, so the Target ACoS lever is ignored.                                                                                                                                                                                                                                      |
| **insufficient baseline**                                                                           | Your last 30 days have no spend or no clicks, so there is little to project from.                                                                                                                                                                                                                                               |
| **extreme budget cut**                                                                              | Budget change is below -75%.                                                                                                                                                                                                                                                                                                    |

Only the mixed-currency and confidence warnings have a full sentence. The others are shown as plain lowercase words, for example "budget not utilised". They are normal warning flags, not errors.

{% hint style="info" icon="lightbulb" %}
**Every projection is an estimate.** The simulator extrapolates from your recent performance. It assumes the market behaves roughly as it did over your baseline period. Seasonality, competitor moves, and listing changes can all shift the real outcome, so use the projection to compare options, not as a recommendation to spend more or as a guaranteed result.
{% endhint %}

### Saving scenarios

The **Save scenario** button appears only after a simulation has run successfully. If you move a slider afterwards, the result is cleared and the button hides again, so what you save is always what you just ran. If the settings ever differ from the last run when you try to save, the page tells you "Run a simulation with these settings before saving."

Click **Save scenario**, and a dialog titled "Save this scenario" asks you to "Name this scenario:". The name is pre-filled with "Scenario" and today's date; change it to something you will recognise. Saved scenarios are private to your project.

The **Saved scenarios** card at the bottom of the tab lists them, with a count next to the title. Each row shows the name and a one-line summary such as "budget +20% · bid +10% · target ACoS 25%". Two buttons sit on each row:

* **Play button:** puts the saved levers back on the sliders and runs the simulation again against your current data.
* **Trash button:** deletes the scenario after you confirm "Delete this saved scenario?". This cannot be undone.

When you have none, the list reads "No saved scenarios yet."

### Worked example: scaling for the holidays

> **Situation:** Your baseline for the last 30 days is EUR 2,400 spend, EUR 9,600 sales, 25.0% ACoS and 4.0x ROAS. You want to grow volume for Q4 and your main campaigns run out of daily budget well before the end of the day.
>
> **What you do:**
>
> 1. Open Scenario Simulator and set **Budget change** to +30%.
> 2. Leave **Target ACoS** at "off" and click **Run simulation.**
>
> **Illustrative projection:** Spend rises to about EUR 3,120 (+30%), sales to about EUR 11,790 (about +23%), ACoS drifts up to about 26.5%, and ROAS eases to about 3.8x. The badge reads **High confidence**, because the baseline is 30 days long and +30% is not a large change.
>
> **If you push the slider further:** Drag **Budget change** to +120% and the badge drops to **Medium confidence**, with the warning "Confidence reduced - large change requested".
>
> **If your campaigns are not budget-limited:** Spend would rise by less than 30%, and the page would show "budget partially utilised" or "budget not utilised" instead.
>
> **Decision:** The extra EUR 720 of spend is projected to return about EUR 2,190 in additional sales, roughly 3.0x. That is below your 4.0x average, so you decide whether that marginal return clears your own break-even. If it does, you save the scenario as "Q4 scale +30%" and move to Campaign Mover to schedule the budget change.

*(Figures above are illustrative and depend entirely on your own account data.)*

***

## Campaign Mover

The Campaign Mover records a single campaign-level change to be applied at a future date and time you choose. This is how you plan holiday budget bumps, post-promo pauses, and gradual scale-ups without having to be at your desk when they need to happen. You can cancel a change as long as it is still Pending.

{% hint style="info" %}
**What this page does.** Scheduling a change saves it as **Pending** with its apply time stored in UTC, and the **Planned changes** list tracks its status (Pending, Applied, Cancelled or Failed). The page itself sends nothing to Amazon: a background worker picks up due changes about every 5 minutes and applies them. A change left more than **6 hours** past its apply time - during an outage, for example - is marked **Failed** with a "missed window" reason instead of being applied late. Due changes also wait as Pending while the emergency stop is on or a subscription has lapsed, and in sandbox mode they are simulated rather than sent. After an important apply time has passed, check that the status has moved to Applied, and confirm the result on the campaign itself in your Amazon Ads console before you rely on it.
{% endhint %}

### Quick presets

At the top of the tab, three chips jump straight into the builder. Each one selects the property for you and moves the cursor to the campaign picker:

| Preset                  | Selects                              |
| ----------------------- | ------------------------------------ |
| **Schedule a pause**    | Property **State**, new value Paused |
| **Bump daily budget**   | Property **Daily budget**            |
| **Tighten target ACoS** | Property **Target ACoS**             |

### Building a scheduled change

The builder is a five-step stepper. Each step lights up as you complete it, and a live preview writes out what you are about to schedule in plain English.

{% stepper %}
{% step %}

### Step 1: Pick a marketplace

Choose the marketplace the campaign lives in, or leave it on **All Marketplaces** to list campaigns from every marketplace. Marketplaces are shown with their country flag.
{% endstep %}

{% step %}

### Step 2: Pick a campaign

Select the specific campaign you want to move. The list is filtered by the marketplace you chose in Step 1 and shows each campaign with its country flag. Campaign Mover works at the campaign level, not the keyword level.
{% endstep %}

{% step %}

### Step 3: What to change

Choose the property to change:

| Property                     | Change                                 |
| ---------------------------- | -------------------------------------- |
| **State (ENABLED / PAUSED)** | Set the campaign to Enabled or Paused  |
| **Daily budget**             | Set a new daily budget amount          |
| **Target ACoS**              | Set a new target ACoS for the campaign |

Five more properties are listed with the suffix "- coming soon" and cannot be selected yet: Bidding strategy, Targeting type, Placement: Top-of-search %, Placement: Product-pages % and Campaign name.
{% endstep %}

{% step %}

### Step 4: Set new value

The **New value** control changes with the property:

| Property         | New value control                                                                                                                                                       |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **State**        | A drop-down with **Enabled** and **Paused**. It starts on Enabled, so check it before you schedule.                                                                     |
| **Daily budget** | A number field (minimum 1). The server rejects amounts above 1,000,000.                                                                                                 |
| **Target ACoS**  | A **decimal** number field with the hint "decimal · e.g. 0.25 = 25%". The server accepts 0.01 to 5, so although the field itself will let you type 0, zero is rejected. |

{% hint style="danger" %}
**Target ACoS here is a decimal, not a percentage.** Type 0.25 for 25%. If you type 25, the change is rejected with "target\_acos must be between 0.01 and 5 (decimal, e.g. 0.25 = 25%)". This differs from the Scenario Simulator, where the Target ACoS slider is in percent.
{% endhint %}
{% endstep %}

{% step %}

### Step 5: Pick apply time

Choose the date and time the change should apply, in **your own local time**. The field is pre-filled with tomorrow at 08:00 local time, so change it to the moment you actually want.

Next to the **Apply when** label you will see:

* A **Local time** pill. Hover over it for the tooltip: "Enter your local time. SellerMagnet converts it to UTC; check the UTC time in the preview before scheduling."
* A timezone badge such as "auto: Europe/Berlin", with the tooltip "Browser timezone sent with this planned change." It shows the timezone your browser reports, which is the one your local time is read in.

SellerMagnet converts your local time to UTC before saving, and stores and processes the change in UTC. The live preview prints the converted time as "{date} at {time} UTC", for example "Nov 24 at 06:00 UTC". Always check that line before you click **Schedule change**.

The apply time has to be in the future. The server rejects a time that is more than 5 minutes in the past with "apply\_at must be in the future (or within last 5 min for clock skew)."
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Enter your local time, do not convert it yourself.** The page does the conversion to UTC. If you convert first and type the UTC time, the time is shifted twice and the change is set for the wrong hour. For example, you are in Berlin in winter (UTC+1) and want 07:00 local time: type 07:00, and the preview reads "... at 06:00 UTC". A local time that does not exist on a daylight-saving change day (the skipped hour) cannot be scheduled and gives the message "Pick when this should apply."
{% endhint %}

### Preview and reason

Below the steps, a **live preview** turns your selections into a sentence. For a daily budget it reads, for example: "Will set the daily budget of Brand-Exact to €80.00 on Nov 24 at 06:00 UTC." The budget is shown in your account's default currency. For a state change it reads "Will pause ..." or "Will enable ...", and for a target ACoS "Will set the target ACoS of ... to 25% on ..." (the preview shows 0.25 as 25%).

The preview label is **Live preview** while the form is incomplete and changes to **Ready to schedule** once a campaign, a property, a new value and an apply time are all filled in. The marketplace step is optional.

There is also an optional **Why this change?** field, up to 500 characters. It is not required, but recording a reason ("Black Friday promo", "Q1 scale push", "Out-of-stock pause") makes the planned-changes list far easier to read later. Fill it in, then click **Schedule change.** The toast "Planned change scheduled." confirms it, the reason field is cleared, and the list switches to the **Pending** filter.

### The Up-next banner and Planned changes list

At the top of the tab, an **Up-next banner** highlights the pending change with the earliest apply time. Its bold title shows the property and the new value, for example "Daily budget → 80", with a clock chip for the apply time and a campaign chip beside it. The campaign chip shows the campaign as "Campaign" followed by its ID. When nothing is queued the banner reads "No upcoming scheduled changes" and points you to the builder. If the page could not load your changes, it says "Scheduled changes could not be loaded - This is a loading problem, not an empty queue" and asks you to reload; that does not mean your queue is empty.

The **Planned changes** list at the bottom shows your scheduled changes, sorted by apply time with the earliest first, with a count badge next to the title. The row label **Show** introduces the filters:

| Filter        | Shows                                            |
| ------------- | ------------------------------------------------ |
| **Pending**   | Scheduled changes that have not been applied yet |
| **Applied**   | Changes that have already been applied           |
| **Cancelled** | Changes you cancelled before they were applied   |
| **Failed**    | Changes that could not be applied                |
| **All**       | Everything, regardless of status                 |

Each row shows:

* The property ("Campaign state", "Daily budget" or "Target ACoS") and the new value.
* The campaign with its country flag. The list does not always carry the campaign name, so a row may show "Campaign" followed by an ID, such as "Campaign 123456789", instead of a name.
* The apply time, and your reason in italics if you gave one.
* For failed rows, a failure reason in red.
* A status badge: **Pending**, **Applied**, **Cancelled** or **Failed**.

When a filter has no rows, the list reads "No planned changes in this state".

Each row has action buttons:

| Button               | Where             | What it does                                                                                                                                                                                                              |
| -------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Cancel change**    | Pending rows only | Asks "Cancel this planned change?". The change will not be applied, and the row stays in your history as Cancelled. Once a change is no longer pending, the server refuses with "Only a pending change can be cancelled." |
| **Reset to pending** | Failed rows only  | Puts a failed change back to Pending.                                                                                                                                                                                     |
| **Delete**           | Every row         | Asks "Delete this planned change record?" and removes the row from your Planned changes list. The dialog calls this permanent and it cannot be undone from the page.                                                      |

{% hint style="warning" %}
**To stop a pending change, use Cancel change, not Delete.** Delete is for tidying your history. Cancel is the action that marks a pending change as Cancelled.
{% endhint %}

### Worked example: scheduling a Black Friday budget bump

> **Goal:** Raise the daily budget on your "Brand-Exact" campaign to 80 at the start of Black Friday.
>
> **Steps:**
>
> 1. Open the **Campaign Mover** tab.
> 2. Step 1: pick the marketplace (or leave All Marketplaces).
> 3. Step 2: select **Brand-Exact.**
> 4. Step 3: choose **Daily budget.**
> 5. Step 4: enter **80.**
> 6. Step 5: your promo starts 07:00 Berlin time on November 24. You type your own local time, **Nov 24, 07:00.**
> 7. Reason: "Black Friday promo."
>
> **Preview reads:** "Will set the daily budget of Brand-Exact to €80.00 on Nov 24 at 06:00 UTC." The UTC time is 06:00 because Berlin is UTC+1 in winter. That is the line to check.
>
> **Result:** You click **Schedule change.** The change appears under **Pending** and in the Up-next banner. You can cancel it any time while it is Pending. Once the apply time has passed, look at the status in the Planned changes list: **Applied** means it has been processed, and **Failed** shows a reason.

***

<details>

<summary><strong>⚠️ Common Mistakes to Avoid</strong></summary>

{% hint style="danger" %}

* **Mistake 1: Converting the apply time to UTC yourself.** The Campaign Mover apply field takes your local time and converts it to UTC for you. If you type UTC, the time is converted twice and the change is set for the wrong hour. **Fix:** Enter your own local time, then read the "... at hh:mm UTC" line in the live preview and check that it is the moment you want before you schedule.
* **Mistake 2: Setting both Bid change and Target ACoS in the simulator.** When Target ACoS is above 0 it overrides the Bid change lever, so the manual bid slider is ignored. **Fix:** Choose one approach: either steer bids manually with Bid change, or model autopilot with Target ACoS, but not both at once.
* **Mistake 3: Reading the confidence badge as data quality.** High confidence does not mean your results are steady, and Medium or Low does not mean your data is thin. The badge mostly reflects how large a change you asked for. **Fix:** Use the badge as a size-of-change warning and the **Likely range** to see how much your own results swing. Model a smaller change if the badge drops.
* **Mistake 4: Typing a percentage for Target ACoS in Campaign Mover.** The field takes a decimal, so 25 is rejected. **Fix:** Type 0.25 for 25%.
  {% endhint %}

{% hint style="warning" %}

* **Mistake 5: Treating the simulator as a guarantee.** The projection extrapolates from recent performance and cannot see seasonality, competitor moves, or listing changes. **Fix:** Use it to compare options against each other, then verify the real outcome after the change goes live.
* **Mistake 6: Scheduling a pause and forgetting to schedule the re-enable.** A post-promo pause with no matching enable leaves a campaign dark indefinitely. **Fix:** When you schedule a pause, immediately schedule the Enabled change for when the campaign should come back, and confirm both appear under Pending.
* **Mistake 7: Expecting a budget increase to raise spend on every campaign.** A budget change only affects campaigns that are held back by their daily cap. **Fix:** If you see "budget partially utilised" or "budget not utilised", look at campaign status, bids and targeting before raising budgets further.
* **Mistake 8: Using Delete to stop a pending change.** Delete removes the row from your list; it is not the same as cancelling. **Fix:** Use **Cancel change** on pending rows.
  {% endhint %}

</details>

## ✅ Best Practices

1. **Simulate first, schedule second.** Use the Scenario Simulator to find a strategy you believe in, then use Campaign Mover to put the winning change on a timer. That is the intended two-step workflow.
2. **Save the scenarios you might act on.** A named saved scenario lets you compare a few strategies side by side before you commit, and revisit your reasoning later. The play button re-runs it against your current data.
3. **Enter your local time and read the UTC line in the preview.** Do not convert to UTC yourself. Check the "... at hh:mm UTC" line once, deliberately, before you click Schedule change, and make sure the "auto: ..." timezone badge shows the timezone you expect.
4. **Always write a reason.** The optional reason field costs a few seconds and makes your Planned changes list readable weeks later when you have several moves queued.
5. **Pair every pause with an enable.** For promos and out-of-stock windows, schedule both the Paused change and the Enabled change up front so nothing gets stranded.
6. **Read the confidence badge as a size-of-change signal.** Moderate changes read High. If the badge drops to Medium or Low, you are asking for a big move, so treat the numbers more loosely, and look at the Likely range.
7. **Check the Up-next banner regularly.** It is your fastest confirmation that the right change is queued, and it shows the earliest pending change first.
8. **Check the status after an important apply time.** Open the Planned changes list and confirm the row moved to Applied, then confirm the result on the campaign itself.

## 🔧 Troubleshooting

| Problem                                                           | Cause                                                                                                                                                                            | Solution                                                                                                                                          |
| ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Simulator will not run, "Adjust at least one slider to simulate." | No lever has been moved off its starting position                                                                                                                                | Move at least one slider to any non-zero value (negative values work too)                                                                         |
| Save scenario button is missing                                   | No successful run yet, or you moved a slider after the last run                                                                                                                  | Run the simulation again, then click Save scenario                                                                                                |
| "Run a simulation with these settings before saving."             | The sliders differ from the last run                                                                                                                                             | Run the simulation again with the current settings, then save                                                                                     |
| "No baseline data available for this project / profile / window." | The simulator found no performance data to use as a baseline                                                                                                                     | Check that your Amazon Ads account is connected and has finished its first data load, then try again                                              |
| Bid change slider seems ignored                                   | Target ACoS is set above 0 and overrides it                                                                                                                                      | Set Target ACoS back to "off" to steer bids manually                                                                                              |
| Projection shows low confidence                                   | Your last 30 days have no spend or no clicks ("insufficient baseline")                                                                                                           | Wait until the account has ad traffic, or model against a period with data                                                                        |
| Confidence drops to Medium or Low                                 | The change you asked for is large                                                                                                                                                | Model a smaller change, or accept that the number is a looser estimate                                                                            |
| Budget change projects little or no extra spend                   | Your campaigns are not held back by their daily budgets ("budget partially utilised" / "budget not utilised")                                                                    | Review campaign status, bids, targeting and product eligibility rather than raising budgets                                                       |
| Warning text looks odd, such as "budget not utilised"             | Most warnings are shown as plain lowercase words                                                                                                                                 | This is expected; see the warnings table above                                                                                                    |
| Target ACoS rejected: "target\_acos must be between 0.01 and 5"   | You typed a percentage instead of a decimal                                                                                                                                      | Type 0.25 for 25%                                                                                                                                 |
| "apply\_at must be in the future"                                 | The apply time is more than 5 minutes in the past                                                                                                                                | Pick a future date and time                                                                                                                       |
| "Pick when this should apply."                                    | The apply time is empty, or it falls in the hour skipped by a daylight-saving change                                                                                             | Choose a valid local time                                                                                                                         |
| Scheduled change applied at the wrong hour                        | The UTC time in the preview was not the moment you meant, for example because you converted to UTC yourself, or the timezone badge showed a different timezone than you expected | Cancel the change and re-create it: enter your local time, check the UTC line in the preview, and check the "auto: ..." badge                     |
| Scheduled change is still Pending after its apply time            | The worker runs about every 5 minutes, so a short delay is normal. It also holds due changes while the emergency stop is on or a subscription has lapsed                         | Check the emergency stop and your subscription first. If it is still Pending well past the apply time, contact support at <info@sellermagnet.com> |
| Row shows "Campaign 123456789" instead of a name                  | The planned-changes list does not always carry campaign names                                                                                                                    | The ID is the Amazon campaign ID; match it to your campaign in the PPC Manager                                                                    |
| "Scheduled changes could not be loaded" in the Up-next banner     | The list failed to load                                                                                                                                                          | Reload the page. This is a loading problem, not an empty queue                                                                                    |
| Cannot pick a property in Campaign Mover                          | The option is marked "- coming soon"                                                                                                                                             | Only State, Daily budget, and Target ACoS are available today                                                                                     |
| Page shows a connect banner                                       | Amazon Advertising account is not connected                                                                                                                                      | Click Go to Settings and connect your Amazon Ads account, then reload                                                                             |
| No campaigns appear in the picker                                 | The marketplace filter is set to a marketplace without campaigns, or ads data is still loading                                                                                   | Choose All Marketplaces, wait for the initial data load to finish, or reload if you see "Could not load campaigns - try refreshing the page."     |

***

## ❓ FAQ

<details>

<summary><strong>Does running a simulation change anything in my Amazon account?</strong></summary>

No. The Scenario Simulator is a pure forecast. It reads your recent performance and projects forward, but it never sends anything to Amazon. You can run it as often as you like with no risk.

</details>

<details>

<summary><strong>Why does the Target ACoS lever override my Bid change?</strong></summary>

Target ACoS and a manual bid change are two different ways to steer the same thing. When you set a target ACoS, the simulator models autopilot bidding toward that target, which supersedes any fixed percentage bid change. Pick whichever approach matches how you actually plan to manage bids, and leave the other at its default.

</details>

<details>

<summary><strong>What does the confidence badge mean?</strong></summary>

It tells you how far the change you modelled sits from your normal operating level, on top of the baseline length. The page uses a 30-day baseline, which starts at High. A budget or bid slider above +100%, or projected clicks that move by more than 75% from your baseline, lower it by one level. Projected clicks that move by more than 150% lower it by two levels. It is not a measure of how clean your data is; for that, look at the Likely range on each metric.

</details>

<details>

<summary><strong>What is the Likely range under a metric?</strong></summary>

A low and a high value for that metric, taken from your own day-to-day history. It appears when you have at least 7 days of daily history. It is not a guarantee: the real outcome can land outside it.

</details>

<details>

<summary><strong>Why do I see "budget partially utilised" or "budget not utilised"?</strong></summary>

A budget change only moves spend for campaigns that are actually held back by their daily budget. If only some of your spend comes from such campaigns, you get "budget partially utilised" and the projected change is smaller than the slider. If none of it does, you get "budget not utilised", the page adds a note that higher budgets alone are not projected to increase delivery, and offers a **Review campaigns** link.

</details>

<details>

<summary><strong>Are apply times in my timezone or UTC?</strong></summary>

You enter your own local time. SellerMagnet converts it to UTC when you schedule, and stores and processes the change in UTC. The live preview shows the converted time as "... at hh:mm UTC", so check that line before you click Schedule change. The "auto: ..." badge shows the browser timezone that is sent with the change.

</details>

<details>

<summary><strong>Can I cancel a scheduled change after I create it?</strong></summary>

Yes, as long as it is Pending. Click **Cancel change** on the row and confirm; the row stays in your history as Cancelled. Once a change is Applied (or otherwise no longer pending) it cannot be cancelled, though you can always schedule a new change to reverse it.

</details>

<details>

<summary><strong>How do I know a scheduled change has been applied?</strong></summary>

Look at the status badge in the Planned changes list. **Pending** means it is still waiting for the worker, **Applied** means it was sent, and **Failed** shows a failure reason in red. For anything important, also confirm the result on the campaign itself in Amazon Ads. A failed change can be put back to Pending with **Reset to pending**.

</details>

<details>

<summary><strong>What is the difference between Cancel change and Delete?</strong></summary>

**Cancel change** is for pending rows and marks the change as Cancelled; the row stays in your history. **Delete** is available on every row and removes it from your Planned changes list. Use Cancel to stop a pending change.

</details>

<details>

<summary><strong>Why does a row show "Campaign 123456789" instead of the campaign name?</strong></summary>

The planned-changes list does not always include campaign names, so it falls back to "Campaign" followed by the campaign ID. The Up-next banner always shows the campaign this way.

</details>

<details>

<summary><strong>What level does Campaign Mover operate at?</strong></summary>

The campaign level. You pick one campaign and change its state, daily budget, or target ACoS. Keyword-level bid changes belong in Bid Rules and the AI Optimizer, not Campaign Mover.

</details>

<details>

<summary><strong>Why are some properties greyed out?</strong></summary>

Bidding strategy, Targeting type, both Placement percentages, and Campaign name are marked "- coming soon" and cannot be scheduled yet. Only State, Daily budget, and Target ACoS are available today.

</details>

<details>

<summary><strong>Are my saved scenarios visible to other users?</strong></summary>

No. Saved scenarios are private to your project. They are there for you to compare strategies and revisit your reasoning later.

</details>

***

## ➡️ What's Next?

{% content-ref url="/pages/kw3mb3OSwMEFnPlRPVag" %}
[PPC AI Optimizer](https://docs.sellermagnet.com/ppc-management-beta/ppc-manager-overview/ppc-ai-optimizer.md)
{% endcontent-ref %}

{% content-ref url="/pages/AgCa0wMskRJ5quPLWZtg" %}
[PPC Bid Rules](https://docs.sellermagnet.com/ppc-management-beta/ppc-manager-overview/ppc-bid-rules.md)
{% endcontent-ref %}
