netroas documentation
Wersja robocza — wymaga przeglądu prawnego / Draft — pending legal review
Effective: [DATA]
netroas runs Google Ads campaigns from an AI assistant: it reads data, runs audits, proposes changes and applies them after you confirm.
Intended purpose
For merchants and agencies who want to review and improve Google Ads in a conversation with an assistant. Tools return data from the account; the assistant explains it in plain language. Outside Google Ads (GA4, Search Console, Merchant Center) netroas only reads.
How to connect
Add a connector with the public /mcp address (OAuth) in your assistant, then sign in with a Google account that has Google Ads access. Guides for Claude, ChatGPT, Cursor, VS Code, Claude Code and Codex:
Google sign-in must work — without it netroas has no access to data. During the pilot it may be temporarily unavailable; the added connector stays and works once you sign in.
Tools
List from the server registry (current every time this page is shown):
| Tool | Title | Kind |
|---|---|---|
ping | Check connection | read |
audit | Audit account | read |
plan | Build improvement plan | read |
report | Google Ads report | read |
status | Account status | read |
get_policy | Read policy and goal | read |
set_goal | Set campaign goal | write (changes Google Ads account state or netroas settings) |
set_policy | Set strategy limits | write (changes Google Ads account state or netroas settings) |
strategy_template | Strategy template | read |
mode | Read or set work mode | write (changes Google Ads account state or netroas settings) |
propose_change | Propose change | proposal (writes only to netroas; Google receives a validateOnly check only) |
apply | Apply confirmed change | write (changes Google Ads account state or netroas settings) |
reconcile_change | Reconcile interrupted change | write (changes Google Ads account state or netroas settings) |
undo | Undo change | write (changes Google Ads account state or netroas settings) |
changes | Change log | read |
playbook | Account playbook | read |
weekly_review | Weekly review | read |
feed_check | Check Merchant feed | read |
propose_campaign | Propose new campaign | proposal (writes only to netroas; Google receives a validateOnly check only) |
validate_copy | Validate ad copy | proposal (writes only to netroas; Google receives a validateOnly check only) |
create_campaign | Create confirmed campaign | write (changes Google Ads account state or netroas settings) |
performance_review | Compare performance | read |
full_report | Full PDF report | read |
merchant_check | Merchant Center check | read |
site_check | GA4 site check | read |
data_sources | Data sources | read |
search_demand | Search demand (Search Console) | read |
Confirming and undoing changes
- propose_change or propose_campaign prepares a preview and changes nothing; the server checks policy and limits, and Google validates the change as a dry run (validateOnly).
- The assistant shows the preview; after your “yes” for that proposal it calls apply (or create_campaign). A proposal is valid for 24 hours.
- undo reverts an applied change if it is reversible and nobody changed the account in the meantime; changes shows the log; reconcile_change checks with Google the result of a change interrupted mid-way and completes the log (it never retries the write).
- Free plan: up to 5 confirmed changes per month; an undo does not return quota.
Modes and limits
- Modes: observe, confirm (default), autopilot. You enable autopilot only on the netroas website, after at least 14 days of confirmation mode, with a goal set.
- Server limits: budget ±20 % per change, tROAS/tCPA target ±10 %, 7 days between structural campaign changes, at most 35 % budget change in 30 days, the daily ceiling from your policy.
- A server refusal is a decision, not an error — the assistant should pass it on as is.
Troubleshooting
- Connector not visible: check that it is enabled in the assistant settings and in the conversation; in Claude Team/Enterprise the organisation owner adds connectors.
- Google sign-in error: try again later (during the pilot sign-in may be unavailable); make sure the Google account has access to Google Ads.
- No GA4, Search Console or Merchant Center data: tick all scopes on the Google consent screen, and the Google account must have access to that service; then connect again.
- Revoke and reconnect: revoke access at https://myaccount.google.com/permissions, remove the connector in the assistant and add it again following the install guide.
Privacy and support
Support: [E-MAIL WSPARCIA].