Preview, Runs and rollback

Two pages under Monitoring show DSP Automation’s work: Preview, before anything is sent, and Runs & Change Logs, after.

Preview

“What the rules would change right now, using synced data. Nothing is sent until you press Apply.”

Preview checks every order that has an Objective, with the same evaluation a run uses, and lists one row per match:

Column	What it holds
Order / line item	Where the change lands, with its order
Rule	The rule that matched
Change	The field, its value now, and the value the rule wants — Max bid: $6.00 → $5.40
Numbers	The figures the rule judged on: impressions, the condition metrics, cap used, days left in the flight
Status	Will change, a reason it won’t, or Stopped by “…” when a higher-priority rule holds the same field

The line above the table says how many orders were checked, “using data synced up to” which date, and how many changes would be made. Run Again recalculates.

Include rules that are off adds switched-off rules, so you can read a rule before turning it on. Their rows always show Rule is off.

Why a row won’t change

Status	Means
Rule is off	The rule is switched off
Excluded	The order or line item is excluded for this rule type
Line item is still learning (under 7 days)	Bidding and Frequency rules wait 7 days
In cooldown	DSP Automation changed the same thing too recently
Max bid is Automatic	A percentage change has no CPM to change
Already at the target	The value is already where the rule would put it
Cap is already at the rule’s ceiling	A Budget rule can’t raise it further
Raised the most times allowed in 7 days	The Budget rule’s raise limit is used up
The rule already added the most flights allowed	The Budget rule’s flight limit is reached
The new flight would end after the stop date	The Budget rule’s Stop by date

The highest-priority rule that matches keeps the field even when it is blocked — in cooldown, say — so a lower-priority rule cannot push the same value the other way in the meantime.

Applying one change yourself

Apply… on a Will change row opens DSP Manager’s own send window for that one change: it reads the order or line item from Amazon DSP, shows what will change, and sends when you confirm. It is the same as making the change by hand in DSP Manager, so it needs DSP Manager · Edit and an advertiser that allows sending — see Before you can send — and it is recorded in Change history under your name.

This is how a change goes out when automatic sending is off, and the only way a Set max bid to Automatic rule is ever applied.

Runs

Runs & Change Logs lists the last 30 runs, newest first. A seller with no switched-on rule in an assigned Objective has nothing to run, so no run is recorded:

Column	What it holds
Started	Date and time, Pacific
Trigger	Scheduled, or Manual for a run Vendlen started
Result	n sent · n failed · n skipped; for a dry run, n would change · dry run and why; Skipped and why; Failed

Open a run to see every change it considered, with its rule, the change from → to, and its outcome:

Outcome	Means
Sent	Amazon DSP accepted it
Would change	A dry run: it would have been sent
Failed	Amazon rejected it, or its answer was unclear. Amazon’s message is shown
Skipped	Not sent, with the reason — for example “Changed on Amazon since the check” or “In cooldown”
Blocked · Stopped	Matched, but blocked or stopped by a higher-priority rule, as in Preview

When Amazon’s answer is unclear, the run reads the order or line item back. If the change is there, it is logged as Sent, with “Amazon’s answer was unclear, but reading it back showed the change”. If not, nothing else is changed on that order or line item in the same run, and the change still counts toward its cooldown — Amazon may have applied it.

A run that stops partway is logged as failed; one interrupted for more than two hours is closed with “The run was interrupted. Changes it may have sent are counted for cooldown.”

Rolling a change back

Roll Back… appears on a Sent change. It sends the old value back through DSP Manager’s send window, the same way as Apply — so it needs DSP Automation · Edit, DSP Manager · Edit and an advertiser that allows sending. Nothing is rolled back automatically.

When the old value shows in Vendlen, the change is marked Rolled back. If it doesn’t yet: “Vendlen does not show the old value yet, so it was not marked as rolled back. Check Change History, then try again.”

• Flights can’t be rolled back. A flight DSP Automation added can only be changed in Amazon DSP.
• A rolled-back change still counts for cooldown, so the rule does not redo it on its next run. To stop it for longer, switch the rule off or exclude the order or line item.