Google Ads
Spend, conversions, ROAS, queries, products, budgets and targets. This is the only service where change operations are available under the account mode and rules.
See where campaigns spend without results and what to fix first. netroas reviews Google Ads and your available Google data, prepares changes and applies them with your confirmation. Work in the AI assistant you already use.
Spend, conversions, ROAS, queries, products, budgets and targets. This is the only service where change operations are available under the account mode and rules.
Paid-traffic purchases versus Ads conversions, channel mix and landing pages converting clearly below average.
Queries, clicks, impressions and positions — inputs for new campaigns and a check of brand demand.
Rejected products with reasons, catalogue status and — with Market Insights enabled — price benchmarks and best sellers.
After successful Google sign-in, you can use the services your account can access. Beyond Google Ads, netroas only reads data. A missing source does not block an audit; your assistant identifies the missing context.
In the pilot, Claude Cowork, ChatGPT and Codex use the same connector. Choose your app and review its connection instructions.
Paste the netroas address, connect your Google account, and select the connector in the conversation.
Customize → Connectors → Add custom connectorCreate a private app from the MCP address and connect the account. Public-directory installation becomes possible only after OpenAI approval.
Settings → Security and login → Developer modePaste the address, restart, and choose Authenticate. Prefer a terminal? Copy one command.
Settings → MCP servers → Add servercodex mcp add netroas --url https://mcp.netroas.dmt.zone/mcpA clear note on ChatGPT: direct connection to your own MCP server currently uses Developer Mode. A public directory version requires separate OpenAI approval.
You do not assemble a report from four dashboards. Ask in plain language; netroas combines the sources and shows scope, numbers and whether an operation is reversible before any write.
1. Fix 23 rejected feed products. 2. Review 7 weak landing pages. 3. Exclude 61 non-selling terms in Ads — after your approval.
Compares paid-traffic purchases in GA4 with Ads conversions. A larger discrepancy is a signal to investigate, not a verdict.
Reads Search Console queries, clicks and impressions, then uses them when planning new campaigns and brand campaigns.
Uses GA4 to identify paid landing pages converting clearly below the account average.
Shows rejected products and reasons. Uses price benchmarks and best sellers when Market Insights is enabled.
Audits and proposes negatives, budgets and targets, and prepares Search, Shopping and Performance Max campaigns.
In control mode, the workflow runs from proposal and preview to execution. The server enforces step limits and a journal; nothing outside Ads is changed.
netroas is an intermediary and execution layer between your assistant and Google — not a stateless proxy. The standard connection uses OAuth. To operate in the background, the server stores access tokens and the state described below.
With the standard connection, you sign in at Google and do not paste a Google key into the conversation. The assistant stores an MCP token; treat a legacy private connector URL like a password.
OAuth and MCP tokens, e-mail and consent, account identifier, settings, strategy, audit results, proposals and the change journal.
We do not mirror entire accounts. Data is fetched from Google services when an audit, check or decision requires it.
netroas tools perform no writes in GA4, Search Console or Merchant Center and do not change your feed or website. The Google consent scope may be broader than the operations used.
The server allows a closed operation list, step limits and a journal. In control mode, the assistant follows proposal → preview → “yes” → execution; autopilot follows the stored strategy.
Revoking Google consent blocks further Google access but does not automatically delete local records. After 30 days without activity, we remove the Google token, audits and active state; a technical account record and anonymised journal may remain.
The assistant follows proposal → preview → “yes” → execution. The server runs one operation at a time, journals it and offers undo for reversible changes.
Audit, improvement plan, and reports with no write operations. Switch with one prompt.
Optional, after at least 14 days in confirmation mode, with a goal and policy set. Enable it separately on the website; it operates within safety rules.
Free: an audit at no cost. Start: USD 12, Pro: USD 25 per month. Agency: USD 5 per account per month. Net prices + tax.
USD · net prices + tax
For one account, to get started.
For regular work on one account.
For up to three accounts.
For agencies, priced per account.
Done for you, with human review. We agree the scope of care individually.
Free includes an audit and up to 5 confirmed changes per month. Start has no monthly plan quota; safety and API limits still apply. Managed care is a separate, optional add-on. Advertising spend and your AI assistant are paid separately. Within the first 14 days of paid service: a full refund.
Pilot: we are opening sign-up. After successful sign-in, go from Google access to your first audit. Jump to any step.
Sign in with access to Google Ads and choose an advertiser account, not a manager account. GA4, Search Console and Merchant Center are optional; the same Google login needs access to them.
https://mcp.netroas.dmt.zone/mcp
Copy the address and add netroas using the instructions. For the public /mcp address, choose OAuth and sign in with Google. A private /t/…/mcp address contains your access key: keep it private; it needs no additional login.
Customize → Connectors → Add custom connector
Paste the netroas address, connect your Google account, and select the connector in the conversation.
Provider instructionsSettings → Security and login → Developer mode
Create a private app from the MCP address and connect the account. Public-directory installation becomes possible only after OpenAI approval.
Plugins → +
Settings → MCP servers → Add server
Paste the address, restart, and choose Authenticate. Prefer a terminal? Copy one command.
codex mcp add netroas --url https://mcp.netroas.dmt.zone/mcp
Streamable HTTP
codex mcp login netroas
claude mcp add --transport http netroas https://mcp.netroas.dmt.zone/mcp
/mcp
Select netroas in a new conversation and paste this prompt. A response naming the correct account confirms that your assistant can access your data.
Use netroas. Check the connection, Google Ads account name and access to GA4, Search Console and Merchant Center. Explain missing permissions. Do not change campaigns.
Missing a service? Check Google permissions, return to the installation page and refresh Google access. If your assistant cannot see netroas, check the address, authentication and connector selection in the conversation.
Use netroas. Audit the last 30 days, allow for conversion lag and check tracking. Show the three most important issues, evidence and an improvement plan. Do not make changes.
Use netroas. Review spend, conversions, recent changes and alerts. Suggest the next action with evidence. Before any change, show a preview and wait for my confirmation.
Start with reading. Set a goal and budget limit before the first change. Autopilot is optional, available after 14 days of confirmation mode and enabled separately on the website.
Pilot: we are opening sign-up. After successful Google sign-in, choose your Ads account and check the available services. Connecting alone does not begin a paid subscription.
In control mode, the assistant follows proposal → preview → your “yes” → execution. Independently, the server limits the operation list, step size and frequency and journals the result. Autopilot unlocks after 14 days, is enabled separately on the site and follows the strategy.
No. Google Ads is enough to start. netroas uses GA4, Search Console and Merchant Center when the same account can access them, and states clearly what it cannot check when a source is missing.
No. These services provide diagnostic context and netroas only reads from them. Approved operations can run only in Google Ads; you fix the feed and website on your side.
You, to your provider — Claude, OpenAI. netroas supplies the numbers and the execution; the assistant writes the sentences on your account.
Optional, after at least 14 days in confirmation mode, with a goal and policy set. Enable it separately on the website; it operates within safety rules.
Yes, any month. Within the first 14 days of paid service: a full refund. Campaigns and their history stay on your Google account.
No. The server stores OAuth and MCP tokens, e-mail and consent, account identifier, settings, strategy, audit results, proposals and the journal. It does not mirror entire Google accounts. After 30 days without activity it removes the Google token, audits and active state; a technical account record and anonymised journal may remain.
netroas can work alongside your agency in observe mode. Agency is priced per account.
No. netroas doesn't bid manually — it sets goals and limits, Google bids. The agent watches what Google doesn't: waste, margin, learning resets and budget.