Log in / Create free account🌐 ES☀️

Intermediate training · Module 10 — Scripts I — what they are, what they solve and how to install the Suite

Reading the scripts' spreadsheets: dashboards, traffic lights, checkboxes, history and the manual

⏱️ 8 min read · 🥷 Scripts · updated on 2026-09-02

🎧 Listen to the lesson · ≈ 4 min🔒 Subscribers only

In short: every spreadsheet in the suite has the same anatomy — Settings, Dashboard with traffic light, analysis, actions with a checkbox, history by ID, diagnostics and manual — so learning to read one means learning them all. You read from red to green, and the checkbox is the only door to anything irreversible: nothing runs unless you tick it.

The interface of every Suite script is a Google spreadsheet. They all follow the same anatomy, so learning to read one is learning to read all of them. This lesson is that lesson: which tab to look at first, what each colour means and how to approve an action.

Which tabs does a suite spreadsheet have?

Tab What it holds When you look at it
Config Goals, thresholds, scenarios, emails, TEST mode, the Active checkbox When you install; when you change your criteria
Dashboard A summary with a traffic light: the status of each account/campaign/product against the goal Every Monday, in 2 minutes
Analysis tabs The detail per item: search terms, keywords, products, placements, ad assets When the Dashboard flags something
Action tabs Proposals with an approval checkbox (pause, exclude, negate, publish) Every week: approve or dismiss
History Everything applied, with the date, the reason and the item's ID To audit or to roll back
Diagnostics / Log The trace of the last run, with errors highlighted If something does not add up
Manual How the script works, tab by tab, regenerated with each version The first time; after an update

What do the traffic-light colours mean?

The colours are consistent across the whole Suite:

Reading rule: you read the Dashboard from red to green. The reds take you to their detail tab; the greens you leave alone.

How do you approve an action with the checkboxes?

An action tab has rows with a proposal (what, why, on what data) and a checkbox. Ticking it = approving; on the next run the script applies the action, logs it in the history with its date and verifies it (checks in Google Ads that it went through). What you need to know:

What are TEST mode and the Active checkbox for?

Which patterns repeat across every spreadsheet?

What should you review each week in five minutes?

  1. The script's email (if it sends one): anything red?
  2. Dashboard: from red to green.
  3. Action tabs: approve/edit/dismiss.
  4. Diagnostics only if the Dashboard timestamp is not from today.
  5. Close it. The script does the rest.

💡 Ninja trick: the spreadsheets are also the interface with the Agent: each script publishes a small range of indicators in its spreadsheet (the NS_KPIS) that the Agent reads to watch the fleet and summarise it by email. That is why it is best not to rename tabs or move blocks around: the spreadsheet is yours, but the scripts and the agent read it by position and by ID.

What you should remember

📎 Sources and further reading

⚠️ Free training with no support. Ninja Scripts support channels (email and Telegram) are only for the use of the scripts, not for Google Ads questions or questions about this training.

Pick up here

← BeforeAnatomy of the loader, the licence and the security: why the code never circulatesScripts I — what they are, what they solve and how to install the SuiteAfter →Automating with judgement: rules, scripts and AI — what to delegate, what to supervise and what never to automateScripts I — what they are, what they solve and how to install the SuiteRelacionadaAI Max Analyzer in practice: install it, read the verdict and actAI Max — the black box of automatic Search expansionRelacionadaAnatomy of a GAQL query: clauses, operators, dates, micros and the rules that get you rejectedGAQL and the API — reading what the interface does not showRelacionadaAnomalies, currencies and safety: keeping the judge from doing harmSmart Bidding II — portfolios, cross-mode, the judge and anomaliesRelacionadaAPI versus scripts: where each automation should liveGAQL and the API — reading what the interface does not show

Ver el temario completo

🎓
You're reading the Ninja Academy in the open

Create your free account (no card) to save your progress, take the graded quizzes, earn the Basic level certificate and unlock part of the Intermediate and Advanced training.

Create my free account →
🥷

Subscriber feature

This option is part of the Ninja Scripts Suite subscription.

See the subscription →