Google Ads by Get MCP Ads
<div align="center">
# Google Ads MCP server
### Turn Google Ads questions into useful answers.
Explore performance, research keywords and prepare campaign changes from your MCP client.
[](https://github.com/get-mcp-ads/google-ads-mcp-server/releases/latest)
[](https://github.com/get-mcp-ads/google-ads-mcp-server/actions/workflows/ci.yml)
[](https://smithery.ai/servers/getmcpads/getmcpads-google-ads)
[](LICENSE)
[](package.json)
[Watch the film](https://www.getmcpads.com/home/film/get-mcp-ads-brand-film-1080p.mp4) · [What's new](#whats-new) · [Install](#install-this-release) · [Tool reference](#tools) · [Try hosted getmcpads](https://www.getmcpads.com/tools/google-ads?utm_source=github&utm_medium=readme&utm_campaign=google-ads)
[](https://www.getmcpads.com/home/film/get-mcp-ads-brand-film-1080p.mp4)
**[Play the 45-second film](https://www.getmcpads.com/home/film/get-mcp-ads-brand-film-1080p.mp4)**
</div>
The film shows hosted getmcpads with sample data. Its MCP Apps, from creative galleries and alerts to Google Sheets exports and bulk launches, belong to the hosted product. This repository provides the standalone native API tools.
**35 read tools** · **13 write tools**, disabled by default.
Run locally with your own platform credentials and a client that supports stdio MCP, such as Claude Desktop, Claude Code or Cursor. Your requests go directly to the platform. For managed connections, including supported ChatGPT setups, use the hosted option.
## What's new
<!-- release-history:start -->
**[v2.1.1: Zod 4 security update](https://github.com/get-mcp-ads/google-ads-mcp-server/releases/tag/v2.1.1) · October 26, 2026**
- Update `zod` to 4.6.7. Every Zod release before 4.6.6 is covered by the high-severity advisory GHSA-mrhx-c7xc-m3w5: validating an oversized constrained collection can exhaust memory, and no Zod 3 release carries the fix. `npm audit --omit=dev` reports no vulnerability again.
- Keep the Zod 3 validation behaviour. A parameter default is still validated and completed before use, so an omitted object must still supply its required fields.
- Keep each parameter's own description when the parameter is optional or has a default. Zod 4 stores a description on the wrapped schema only, so the shared fallback description could otherwise replace it.
- Tool names, parameters and descriptions published over MCP are unchanged. `server-card.json` is regenerated with Zod 4's JSON Schema output, which spells some constraints differently.
**Earlier releases**
| Version | Date | Highlights |
| --- | --- | --- |
| 2.1.0 | October 23, 2026 | Renames, Google Ads API v26 and Search Lift |
| 2.0.1 | September 23, 2026 | Public repository restored |
| 2.0.0 | September 20, 2026 | Gateway sync and security fixes |
| 1.1.0 | September 13, 2026 | Platform capability sync and quality contracts |
| 1.0.2 | August 30, 2026 | Announce the package version over MCP. |
| 1.0.1 | August 30, 2026 | Add `server.json` and `mcpName` for the official MCP Registry, under `com.getmcpads/google-ads`. |
| 1.0.0 | August 29, 2026 | First open-source release |
[Full changelog](CHANGELOG.md) · [All releases](https://github.com/get-mcp-ads/google-ads-mcp-server/releases)
<!-- release-history:end -->
Source synchronization: [SOURCE_SYNC.md](SOURCE_SYNC.md).
### Upgrade notes
Requires **Node.js 22.23.4, 24.22.1 or 26.12.1**, or a newer release of one of these lines. Older releases lack the October 2026 security fixes, and the server prints a warning on stderr when it starts on one. CI covers Node 22, 24 and 26.
This release makes no breaking change to the configuration. Two changes are announced for 3.0.0:
- `GOOGLE_ADS_ACCOUNT_IDS` is optional in 2.x. When set, every tool is limited to the listed customers. When unset, the server starts as before and prints one line on stderr recommending it. It becomes required in 3.0.0.
- `GOOGLE_ADS_ENABLE_WRITES` still accepts `1`, `yes` and `on`, and prints one deprecation line on stderr. Use `true`, the only value 3.0.0 will accept.
The server pins **Google Ads API v26**. Raw queries sent through `google_ads_run_gaql` and `google_ads_run_readonly_rpc` follow v26 as well. A query that reads `customer.conversion_tracking_setting.enhanced_conversions_for_leads_enabled` or a hotel field of `ad_group_bid_modifier` must use the v26 names listed in [Google's v26 release notes](https://developers.google.com/google-ads/api/docs/release-notes). Writes remain optional and require explicit confirmation.
## Install this release
This is a GitHub source release. npm and MCP Registry versions are published separately. The commands below select this exact version; unpinned `npx` examples later in this document select the version currently available on npm.
```bash
git clone --branch v2.1.1 --depth 1 https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm ci
npm run build
```
Configure your MCP client to run `node` with the absolute path to `dist/cli.js` and the platform credentials documented below.
> **Prefer a managed connection?** [Use Google Ads with hosted getmcpads](https://www.getmcpads.com/tools/google-ads?utm_source=github&utm_medium=readme&utm_campaign=google-ads). Connect your account, select the data your assistant may access and use the hosted MCP connection. See the site for current features and plans.
## What you get
| | |
|---|---|
| **35 read tools** | Campaigns, ad groups, budgets, bidding strategies, search terms, landing pages, Performance Max assets and placements, Shopping, recommendations, change history |
| **13 write tools** | Off by default. Status, budgets, bids, schedules, renames, campaign creation. Each one **previews before it applies** |
| **Full Keyword Planner** | Keyword ideas, historical metrics, forecasts, ad group themes, geo target suggestions |
| **145 metrics, 88 dimensions** | With a compatibility matrix that catches invalid combinations before they hit the API |
| **Google Ads API v26** | The version this release pins, including the Search Lift metrics read from `lift_measurement_config` |
| **5 resources** | Live catalogues the model can read: metrics, dimensions, compatibility rules, 11 workflow recipes |
| **GAQL and beyond** | `google_ads_run_gaql` for raw queries, and `google_ads_run_readonly_rpc` for the services GAQL cannot reach |
### You do not need to know GAQL
The Google Ads API is queried with GAQL, its own query language, and most of its surface is
only reachable that way. This server carries the metric and dimension catalogues, so the model
asks for `cost` and `conversions` by name and the server writes the query.
`google_ads_validate_query` lets it check a combination before spending a call on it, and
`google_ads_run_gaql` is still there when you want to write GAQL yourself.
### Keyword Planner is not in GAQL
Keyword ideas, historical volumes and forecasts live in a separate RPC service that GAQL
cannot reach at all. Same for Reach Planner, audience insights and benchmarks. This server
covers them through `google_ads_run_readonly_rpc` and dedicated tools.
---
## Getting credentials
This is the heaviest setup of any advertising platform. Four values are needed, and one of
them requires a review by Google. Budget an hour the first time.
### 1. Developer token
From a **manager (MCC) account**, open **Tools → API Center** and apply for a token.
It starts at *Test Account* level, which only reaches test accounts. Apply for
**Basic Access** to reach live accounts. Google reviews the application, which can take a
few days.
📖 [Developer token documentation](https://developers.google.com/google-ads/api/docs/get-started/dev-token)
### 2. OAuth client
In a [Google Cloud project](https://console.cloud.google.com/), enable the **Google Ads API**,
then create an OAuth client under **APIs & Services → Credentials**. Choose **Desktop app**
for local use. Note the **client ID** and **client secret**.
### 3. Refresh token
Run the OAuth consent flow once, signed in as the Google account that can see your ad
accounts, and keep the **refresh token** it returns. Google's own helper script does this in
one command.
📖 [OAuth desktop flow](https://developers.google.com/google-ads/api/docs/oauth/cloud-project)
**The refresh token does not expire.** It is the sensitive value here: anyone holding it can
mint access tokens indefinitely. Treat it like a password, and use an OAuth client dedicated
to this server so you can revoke it on its own.
### 4. Login customer ID, if you use a manager account
If the accounts you query sit under an MCC, set `GOOGLE_ADS_LOGIN_CUSTOMER_ID` to the manager
account ID. Dashes are accepted and stripped. Skip it for a standalone account.
You can also leave it unset. Google refuses any request against a managed account unless the
call names its manager, with a `USER_PERMISSION_DENIED` that mentions neither the account nor
the manager, so it reads as missing access rather than as a missing header. When the variable
is unset and the account you query is not directly accessible, the server asks the managers it
can reach which accounts they hold, and announces the one that holds yours. The answer is
resolved once and kept for the life of the process.
Setting the variable is still faster: it skips that discovery entirely, and it is the right
choice when every account you query sits under the same MCC.
Run **`google_ads_health_check`** as your first call. It verifies all four credentials, lists
the accounts you can actually reach, and reports what is missing, without printing any secret.
---
## Setup
### Claude Desktop
`~/Library/Application Support/Claude/claude_desktop_config.json` (macOS)
or `%APPDATA%\Claude\claude_desktop_config.json` (Windows):
```json
{
"mcpServers": {
"google-ads": {
"command": "npx",
"args": ["-y", "@getmcpads/google-ads-mcp-server"],
"env": {
"GOOGLE_ADS_DEVELOPER_TOKEN": "your-developer-token",
"GOOGLE_ADS_CLIENT_ID": "your-client-id",
"GOOGLE_ADS_CLIENT_SECRET": "your-client-secret",
"GOOGLE_ADS_REFRESH_TOKEN": "your-refresh-token",
"GOOGLE_ADS_ACCOUNT_IDS": "123-456-7890"
}
}
}
}
```
Restart Claude Desktop. Ask it: *"list my Google Ads accounts"*.
### Claude Code
```bash
claude mcp add google-ads --env GOOGLE_ADS_DEVELOPER_TOKEN=... --env GOOGLE_ADS_CLIENT_ID=... --env GOOGLE_ADS_CLIENT_SECRET=... --env GOOGLE_ADS_REFRESH_TOKEN=... -- npx -y @getmcpads/google-ads-mcp-server
```
### Cursor
`.cursor/mcp.json` in your project, same shape as the Claude Desktop config above.
### From source
```bash
git clone https://github.com/get-mcp-ads/google-ads-mcp-server.git
cd google-ads-mcp-server
npm install && npm run build
cp .env.example .env # then fill in your credentials
npm start
```
### Configuration
| Variable | Default | Meaning |
|---|---|---|
| `GOOGLE_ADS_DEVELOPER_TOKEN` | none | **Required.** From the API Center, Basic Access or above |
| `GOOGLE_ADS_CLIENT_ID` | none | **Required.** OAuth client ID |
| `GOOGLE_ADS_CLIENT_SECRET` | none | **Required.** OAuth client secret |
| `GOOGLE_ADS_REFRESH_TOKEN` | none | **Required.** From the consent flow |
| `GOOGLE_ADS_LOGIN_CUSTOMER_ID` | none | Optional. Manager (MCC) account ID. Resolved automatically when unset |
| `GOOGLE_ADS_ACCOUNT_IDS` | *unset* | Recommended. Comma-separated customer IDs every tool is limited to. Unset, every account the credentials reach is available. Required in 3.0.0 |
| `GOOGLE_ADS_ENABLE_WRITES` | *unset* | Set to `true` to register the 13 write tools. `1`, `yes` and `on` still work and print a deprecation line |
| `LOG_LEVEL` | `info` | `debug`, `info`, `warn`, `error` |
Check your setup at any time:
```bash
npm run doctor
```
---
## Writes, and why they preview first
Write tools are **disabled by default**. Enable them with `GOOGLE_ADS_ENABLE_WRITES=true`.
Google's own [Google Ads MCP server](https://developers.google.com/google-ads/api/docs/developer-toolkit/mcp-server) is read-only, so this is the part to read carefully.
When enabled, every write tool returns a preview and changes nothing:
```jsonc
// google_ads_update_campaign_budget { customerId: "123-456-7890", budgetId: "555", dailyAmount: 50 }
{
"applied": false,
"action": "google_ads_update_campaign_budget",
"change": { "customer": "1234567890", "budget": "555",
"newDailyBudget": 50, "inMicros": 50000000 },
"message": "Preview only, nothing was changed. Repeat the same call with confirm: true to apply this change to the live account."
}
```
Only a second call carrying `confirm: true` touches the live account.
This is deliberate. An assistant composes these calls, and it can pick the wrong customer, the
wrong campaign, or the wrong order of magnitude on a budget. A mandatory preview makes the
mistake visible before it costs money, and gives a human the stopping point the protocol does
not guarantee on its own.
Two further guardrails:
- **`google_ads_create_campaign` always creates the campaign `PAUSED`.** There is no option to
create it active. Someone has to look at it before it spends.
- **Amounts are converted to micros for you.** Google holds money in millionths, so 12.50 in
the account currency is `12500000`. The preview shows both, so a factor-of-a-thousand
mistake is visible before it applies.
| Tool | What it changes |
|---|---|
| `google_ads_update_campaign_status` / `google_ads_update_adgroup_status` | Pause, re-enable or remove |
| `google_ads_update_campaign_budget` | Daily budget |
| `google_ads_update_adgroup_bid` | Default CPC bid |
| `google_ads_update_campaign_schedule` | Start and end dates |
| `google_ads_rename_campaign` / `google_ads_rename_adgroup` / `google_ads_rename_asset_group` / `google_ads_rename_account` | Name only. Ads cannot be renamed: Google keeps an ad's name immutable |
| `google_ads_create_campaign` | Creates a budget, then a campaign, always `PAUSED` |
---
## Tools
Every tool is listed below. See [server-card.json](server-card.json) for complete parameter and output schemas.
<details>
<summary><b>35 read tools</b></summary>
| Tool | Purpose |
| --- | --- |
| `google_ads_list_accounts` | List Google Ads customer accounts accessible with the current credentials. |
| `google_ads_get_account_details` | Get detailed information for a specific Google Ads customer account. |
| `google_ads_run_gaql` | Execute a raw GAQL (Google Ads Query Language) query. |
| `google_ads_get_insights` | Query Google Ads performance insights with intelligent query planning. |
| `google_ads_get_campaigns` | List campaigns for a Google Ads account with status, budget, channel type, and bidding strategy. |
| `google_ads_get_adgroups` | List ad groups for a Google Ads account, optionally filtered by campaign. |
| `google_ads_get_keyword_performance` | Get keyword-level performance data from keyword_view resource. |
| `google_ads_validate_query` | Validate metric/dimension/resource compatibility BEFORE executing a query. |
| `google_ads_health_check` | Read-only connectivity check. |
| `google_ads_get_account_hierarchy` | List accessible customers and, where possible, manager/client relationships from GAQL customer_client. |
| `google_ads_get_conversion_actions` | List conversion actions with status, type, category, primary/include-in-conversions flags, owner customer, and last activity dates when supported. |
| `google_ads_get_change_events` | Fetch recent change_event rows. |
| `google_ads_get_recommendations` | List Google Ads recommendations with type, resource, campaign/ad group links, dismissed state, and impact when supported. |
| `google_ads_get_budgets` | List campaign budgets with amount, status, delivery method, and recommended budget fields when supported. |
| `google_ads_get_bidding_strategies` | List portfolio bidding strategies. |
| `google_ads_get_search_terms` | Fetch search term performance from search_term_view or campaign_search_term_insight depending on reportType. |
| `google_ads_get_landing_pages` | Fetch landing_page_view performance with final URL, campaign/ad group context, traffic, conversion, and landing-page quality metrics when supported. |
| `google_ads_get_pmax_assets` | List Performance Max asset group assets from asset_group_asset with asset group/campaign context and optional date-range performance metrics. |
| `google_ads_get_simulations` | Read-only planning/forecast query for campaign, ad group, or portfolio bidding simulations. |
| `google_ads_get_paid_organic_search_terms` | Read-only paid/organic search terms report. |
| `google_ads_get_shopping_products` | Read-only Merchant Center product catalog/eligibility report via shopping_product. |
| `google_ads_get_shopping_performance` | Read-only Shopping performance report keyed by Merchant Center product dimensions. |
| `google_ads_get_pmax_placements` | Read-only Performance Max placement diagnostics from performance_max_placement_view. |
| `google_ads_get_pmax_asset_diagnostics` | Read-only Performance Max asset group diagnostics. |
| `google_ads_list_image_assets` | List the account's image asset library (FROM asset) with stable, publicly served full-size URLs on tpc.googlesyndication.com, dimensions, file size, and mime type. |
| `google_ads_list_video_assets` | List the account's YouTube video assets (FROM asset) with derived watch, embed, and public thumbnail URLs. |
| `google_ads_get_demand_gen_assets` | List Demand Gen ads (video responsive, multi-asset, carousel) with their referenced creatives resolved: stable image URLs and YouTube video IDs with embed and thumbnail URLs. |
| `google_ads_generate_keyword_historical_metrics` | Get Keyword Planner search-volume history for supplied keywords. |
| `google_ads_generate_keyword_ideas` | Discover Keyword Planner ideas from up to 20 seed keywords, a URL, keywords plus URL, or a whole site. |
| `google_ads_generate_keyword_forecast_metrics` | Forecast clicks, CPC, cost, conversions, and CPA for a temporary keyword campaign. |
| `google_ads_search_fields` | Search Google's live GoogleAdsField catalog. |
| `google_ads_suggest_geo_targets` | Resolve up to 25 location names or geo target IDs to Google Ads geoTargetConstants. |
| `google_ads_generate_ad_group_themes` | Organize supplied keywords into existing Google Ads ad groups. |
| `google_ads_run_readonly_rpc` | Advanced read-only escape hatch for allowlisted Google Ads services outside GAQL: Audience Insights, Reach Planner, benchmarks, creator/trending insights, targeting suggestions, Smart Campaign suggestions, identity verification, invoices, and payments accounts. |
| `google_ads_get_video_upload` | Read the processing state and YouTube video ID of one Google Ads upload in the selected customer. |
</details>
<details>
<summary><b>13 write tools</b></summary>
Disabled by default. Calls preview unless explicitly confirmed. Check the configuration and exact schema before use.
| Tool | Purpose |
| --- | --- |
| `google_ads_upload_video` | Upload MP4/WebM/QuickTime bytes (max 16 MiB) to the Google-managed YouTube channel for the selected ad account. |
| `google_ads_remove_video_upload` | Remove a video upload owned by the selected ad account. |
| `google_ads_apply_plan` | Preview, validate and atomically apply a Google Ads v26 build/change plan: campaigns, budgets, ad groups, RSA/Display/Demand Gen ads, image/text/YouTube assets, PMax asset groups and links, keywords, geographic/language targeting listing groups and conversion action configuration (no conversion event uploads). |
| `google_ads_update_campaign_status` | Pause, re-enable or remove a Google Ads campaign. |
| `google_ads_create_campaign` | Create a Google Ads campaign. |
| `google_ads_update_campaign_budget` | Change the daily budget of a Google Ads campaign. |
| `google_ads_rename_campaign` | Rename a Google Ads campaign. |
| `google_ads_rename_adgroup` | Rename a Google Ads ad group. |
| `google_ads_rename_asset_group` | Rename a Google Ads Performance Max asset group. |
| `google_ads_rename_account` | Rename a Google Ads account (its descriptive name). |
| `google_ads_update_campaign_schedule` | Change the start or end date of a Google Ads campaign. |
| `google_ads_update_adgroup_status` | Pause, re-enable or remove a Google Ads ad group. |
| `google_ads_update_adgroup_bid` | Change the default CPC bid of a Google Ads ad group. |
</details>
<details>
<summary><b>5 resources</b></summary>
| URI | Contents |
|---|---|
| `google-ads://manifest` | What this server exposes, and which tool to run first |
| `google-ads://metrics` | All 145 metrics with categories and formats |
| `google-ads://dimensions` | All 88 dimensions and where they are valid |
| `google-ads://compatibility` | The compatibility matrix |
| `google-ads://recipes` | 11 step-by-step workflows |
</details>
---
## Security
This server holds a refresh token that never expires, a client secret and a developer token.
Concretely:
- **None of the four credentials is ever logged**, at any log level, or written to disk.
- **The access token is cached in memory** until a minute before expiry, rather than
re-requested on every call. Reads and writes share it.
- **A revoked refresh token is reported once.** When Google answers `invalid_grant`, every
later call returns the same message with the steps to authorize again, and the server stops
asking Google for a token until it restarts.
- **Accounts can be limited.** With `GOOGLE_ADS_ACCOUNT_IDS` set, a call naming another customer
is refused before any request, and account discovery lists only the allowed customers.
- **Two hosts are contacted, and only two**: `googleads.googleapis.com` and
`oauth2.googleapis.com`. *A test fails the build if a third host appears in the source.*
- **No fetch follows a redirect.** Every outbound call sets `redirect: "error"`, so a redirect
cannot forward a bearer token or client secret to another host. *A test fails the build if
any fetch omits this.*
- **No telemetry.** The server makes no network call other than to Google.
Full policy and reporting instructions: [SECURITY.md](SECURITY.md).
---
## Looking for a managed, multi-platform version?
[Try hosted Google Ads](https://www.getmcpads.com/tools/google-ads?utm_source=github&utm_medium=readme&utm_campaign=google_ads_hosted) if you want to use this source without operating a local server.
getmcpads also connects advertising, Search Console and GA4 through one MCP URL.
Source availability and plan limits are listed on the site; connecting an account is still required.
1. Follow the [Google Ads connection guide](https://www.getmcpads.com/guides/sources/google-ads).
2. Select the account or property your assistant may read.
3. Connect [Claude](https://www.getmcpads.com/guides/setup/claude),
[ChatGPT](https://www.getmcpads.com/guides/setup/chatgpt) or
[Codex](https://www.getmcpads.com/guides/setup/codex).
4. Try a read-only review: “Compare campaign spend and conversions across equal periods. State missing data and do not change anything.”
See the [current hosted tool catalogue](https://www.getmcpads.com/tools/google-ads)
and [pricing](https://www.getmcpads.com/pricing) before choosing a paid plan.
This Apache 2.0 adapter remains independently useful with your own credentials.
---
## Contributing
Issues and pull requests are welcome. See [CONTRIBUTING.md](CONTRIBUTING.md).
Please read [SECURITY.md](SECURITY.md) before reporting anything security-related.
## Licence
[Apache License 2.0](LICENSE). See also [NOTICE](NOTICE).
Google, Google Ads and the Google Ads API are trademarks of Google LLC.
**This project is not affiliated with, endorsed by, or sponsored by Google LLC.**
It is an independent client of a public API.
## MCP contracts and desktop bundle
Every tool declares read/write annotations, parameter descriptions and a structured output schema. Successful calls expose the payload as `structuredContent.result`; errors retain `isError: true`. The generated [server card](server-card.json) contains definitions only.
Run `npm run bundle -- /path/to/output` to build a `.mcpb` desktop bundle from the current catalog. Credentials are entered locally during installation. Write tools remain disabled unless explicitly enabled.
## More from getmcpads
[Meta Ads](https://github.com/get-mcp-ads/meta-ads-mcp-server) · [Google Analytics 4](https://github.com/get-mcp-ads/google-analytics-mcp-server) · [Google Search Console](https://github.com/get-mcp-ads/google-search-console-mcp-server) · [TikTok Ads](https://github.com/get-mcp-ads/tiktok-ads-mcp-server) · [Pinterest Ads](https://github.com/get-mcp-ads/pinterest-ads-mcp-server) · [X Ads](https://github.com/get-mcp-ads/x-ads-mcp-server)
Maintained by **Emmanuel** at [getmcpads](https://www.getmcpads.com). Questions: [hello@getmcpads.com](mailto:hello@getmcpads.com).
TDQS
Scored across 35 tools
Most tools target clearly distinct Google Ads resources or report types, and the descriptions differentiate adjacent areas such as PMax assets, Demand Gen assets, and asset diagnostics. The main ambiguity is among the generic query/discovery tools (get_insights, run_gaql, run_readonly_rpc, validate_query, search_fields), though the descriptions make their intended roles reasonably clear.
All tools use the google_ads_ prefix and snake_case, with mostly predictable action_object naming such as get_campaigns, list_accounts, generate_keyword_ideas, and validate_query. Minor deviations appear in the mix of get_ vs list_ and the noun-style google_ads_health_check, but the pattern remains readable and consistent overall.
Thirty-five tools is heavy for agent selection, and several specialized reports could be consolidated behind run_gaql or get_insights. However, Google Ads has a very broad reporting surface, so many of the tools do earn their place as convenience wrappers rather than being purely redundant.
The surface is broad for read-only Google Ads analytics: accounts, campaigns, ad groups, keywords, search terms, shopping, PMax/Demand Gen assets, budgets, bidding, recommendations, change events, forecasting, and keyword planning are all covered. The main gaps are the absence of any write/mutation lifecycle tools and some less-explicit report surfaces such as ad-level or audience/geo performance, though run_gaql and run_readonly_rpc provide escape hatches for many reporting gaps.