📗 This content is the Smart Bidding Ninja Script user manual, the same one the script writes in the «Manual» tab of its spreadsheet. Here you can search it, listen to it, highlight it and save it to favourites.
Practical recipes for common situations. Copy the label setup onto your campaigns.
Case 1: A brand new campaign
Situation: You launch a new campaign and want SBNS to manage it but without abrupt adjustments during Google's learning phase.
Labels: .SBNS + .lanzamiento + .max 50 (safety cap)
Explanation: The .lanzamiento scenario makes very small adjustments. The .max 50 stops the budget from scaling out of control if the campaign happens to perform brilliantly in its first few days.
When to change it: After 14-21 days, once it has solid data, remove .lanzamiento and apply .neutro or .ninja1 depending on profitability.
Case 2: A star campaign I want to scale
Situation: A campaign with excellent ROAS that you want to push as hard as possible without losing profitability.
Labels: .SBNS + .ninja2
Explanation: The .ninja2 scenario is the most reactive: it adjusts aggressively upwards when the campaign performs well, but it also comes down fast if things get worse (protection).
When to change it: If you see the ROAS falling systematically for 2-3 weeks, drop to .ninja1 or .neutro.
Case 3: A branding campaign with a fixed budget
Situation: A branding campaign on €30/day that the client insists on respecting. You want the metrics but you do not want the script touching the budget.
Labels: .SBNS + .neutro + .presupuesto off
Explanation: .presupuesto off locks any budget adjustment. The script will keep monitoring and, if there is an adjustable target, it will move it, but it will not touch the €30/day.
When to change it: If you change the campaign's strategy and let SBNS manage the budget, remove .presupuesto off.
Case 4: An account with a strict monthly budget
Situation: The client has €10,000/month and does not want to exceed it.
Configuration: "Monthly budget" = Yes, amount = 10000 (in the Config tab)
Explanation: Every day the script works out what pro-rated percentage you have spent. If you are above it, it blocks budget increases on every campaign (but still allows decreases). If you are below it, it works as normal.
Add-on: Combine it with .p [num] labels per campaign if you also want controls at the individual level.
Case 5: A Shopping campaign
Situation: A Shopping campaign with a target ROAS. You want SBNS to manage the budget.
Labels: .SBNS + .neutro
Explanation: Google does not allow the target ROAS of Shopping to be changed via Scripts. The script detects this, leaves the target columns in Day-Stats empty, but does adjust the budget according to the scenario's rules.
Tip: In Day-Stats you will see the "[Shopping]" tag next to the strategy so you can spot these campaigns.
Case 6: Making sense of an unexpected rollback
Situation: You open the Auto-Rollback tab and see an entry with status REVERTIDO for a campaign. You remember that a few days ago you changed its budget manually (typically an aggressive increase of 20% or more).
What has happened: The script detected your manual change and started observing the campaign. On day 7 or day 14 it evaluated the drop in the metric and found it above the threshold. It reverted to the budget the campaign had before your change and locked the script's increases until the date shown in "Lock end date".
What to do: Read the note on the entry. If it says "⚠️ Evaluated on a weak [day]", the drop may be influenced by seasonality and perhaps the increase was right but the timing was bad. If that note is not there, read the drop as real: the campaign could not take that jump in budget.
When to step in: If you think the rollback was unfair, you can raise the budget manually again — the script will detect it as a new manual change and open a new observation window. If you would rather wait for the campaign to settle down, let the 7 days of the lock pass and the scenario that applies will do its job.