Google Ads

Connect direct and MCC-managed Google Ads customer accounts for read-only campaign, keyword, search-term, cost, and conversion analysis.

Connect Google Ads to analyze live advertising performance with GAQL queries. Formula Bot supports directly accessible customers and customers managed through a Google Ads manager account (MCC).

Prerequisites

  • A Google account with access to at least one Google Ads customer
  • An active Google Ads customer account or manager account
  • Formula Bot's server-side Google Ads developer token must be configured and approved for the accounts being queried

The connector cannot create campaigns, change budgets, edit ads, or perform any other mutation. It only uses the Google Ads Search endpoint.

Setup

  1. Open Connectors and choose Google Ads.
  2. Click Connect with Google and authorize Google Ads API access. Google provides one Google Ads OAuth scope rather than a narrower reporting-only scope; Formula Bot restricts its implementation to read-only account discovery and Search requests.
  3. Formula Bot discovers direct customers and traverses accessible MCC hierarchies.
  4. Select one or more serving customer accounts and click Save.
  5. Attach one Google Ads account to a chat or dashboard.

Manager accounts are shown to explain hierarchy but cannot be selected as serving accounts.

Permission and data use

Formula Bot requests these Google permissions:

  • https://www.googleapis.com/auth/adwords to discover accessible Google Ads customers and run the reports you request. Google does not provide a separate read-only reporting scope.
  • https://www.googleapis.com/auth/userinfo.email to label the connected Google account in connector settings.

The connector stores encrypted OAuth tokens, selected customer and manager metadata, saved GAQL queries, query audit records, and generated report artifacts. This information is used to answer your questions and rerun saved dashboard queries. Relevant report data may be processed by Formula Bot's hosting, storage, sandbox, and AI service providers as described in the Privacy Policy; it is not sold or used for advertising.

Disconnecting Google Ads removes Formula Bot's stored OAuth connection and selected customer connectors, which stops new API access. Existing chats, query logs, and generated reports remain subject to your normal retention settings. You can also revoke the grant from your Google Account connections.

Available reporting

  • Campaign and campaign-status performance
  • Ad-group and ad performance
  • Keyword and match-type reporting
  • Search-term reporting, subject to Google's privacy thresholds
  • Impressions, clicks, CTR, average CPC, and cost micros
  • Conversions, all conversions, and conversion value
  • Date, device, network, and compatible conversion segments

Google Ads fields must be compatible with the resource in the GAQL FROM clause. Formula Bot uses the dedicated Google Ads authoring guide to compose and correct queries.

Dates, currency, and timezone

  • Rolling questions use supported GAQL ranges such as LAST_7_DAYS or LAST_30_DAYS and roll forward when a dashboard refreshes.
  • Literal ranges such as BETWEEN '2026-06-01' AND '2026-06-30' remain fixed on refresh.
  • Cost fields such as metrics.cost_micros are returned in micros; divide by 1,000,000 for currency units.
  • Formula Bot carries the selected customer's currency and timezone into analysis context.

Example questions

  • "Show campaign spend, clicks, conversions, and conversion value for the last 30 days"
  • "Which keywords spent more than $100 without a conversion?"
  • "Trend CPA and ROAS by week this quarter"
  • "Which search terms drove the most conversions?"
  • "Compare enabled campaigns by device"

Troubleshooting

Reconnect required

Open Connectors → Google Ads, reconnect the Google account, and select the customer again.

Account inaccessible

Confirm the signed-in Google user still has access to the customer. For MCC-managed customers, verify the manager relationship still exists.

Developer-token configuration

The Google Ads API requires dedicated OAuth credentials and a server-side developer token. A workspace administrator must configure GOOGLE_ADS_CLIENT_ID, GOOGLE_ADS_CLIENT_SECRET, and GOOGLE_ADS_DEVELOPER_TOKEN; never paste them into chat. Analytics and Search Console continue using the shared GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET credentials.

Invalid field combination

Google Ads enforces resource and segment compatibility. Retry with fewer fields, remove the incompatible segment, or split the question into separate reports.

Quota or throttling

Wait before retrying. Formula Bot paginates Search results and caps a single dataset at 250,000 rows.

Next steps