← All posts

  • claude-code
  • google-ads
  • ad-ops

Driving Google Ads from Claude Code

How Claude Code operates Google Ads, taken in order: MCP, the Google Ads API, the developer token, GAQL. Plus the places people actually get stuck connecting, from where we sit building ad-ops tooling.

Driving Google Ads from Claude Code

Translated from the Japanese original on mureo.jp.

Running Google Ads inevitably means long stretches with the console open, chasing numbers. Claude Code lets you replace much of that with instructions in plain language. There are, however, a few hurdles before you get connected, and quite a few people stop there. This article works through how driving Google Ads from Claude Code fits together, and where people actually get stuck.

The overall picture is in Can you automate ad ops with Claude Code?. The other search platform, Yahoo! JAPAN Ads, is covered in Driving Yahoo! JAPAN Ads from Claude Code, and Meta Ads in Driving Meta Ads from Claude Code, and Amazon Ads in Driving Amazon Ads from Claude Code.

Connecting to Google Ads through MCP

Claude Code on its own does not hold Google Ads data. In between sits a connection mechanism called MCP (Model Context Protocol), which talks to the Google Ads API. Claude Code reasons about “give me last week’s CPA for this campaign,” MCP translates that into a query against Google Ads, and Claude Code reads the numbers that come back.

Queries on the Google Ads side use a dedicated syntax called GAQL (Google Ads Query Language). It resembles SQL, but its conventions are its own. You do not need to learn it; Claude Code assembles it for you.

Hurdles before you are connected

Getting a developer token issued If you run this in your own environment, using the Google Ads API requires a developer token. It is an application-and-approval procedure, and even though it is only the first time, it feels heavy if you have never done it. This may be where the largest number of people stall. There are also managed arrangements that take this issuance off your hands.

Linking accounts If you use an MCC (a manager account that groups multiple accounts), connecting its OAuth once lets you extend to the accounts underneath. You then add overrides afterward only where individual accounts need them.

Scope of permissions Being able to touch budgets and bids the moment you connect is not something we recommend. Start with viewing and proposals only, and put approval in front of changes. This ties into the question of how to delegate, below.

What you can do with Google Ads once connected

  • Pull data across the account: read campaigns, ad groups, keywords, and search terms together from a single instruction, and find CPA deterioration and wasteful overlap.
  • Automate the check: delegate the morning number check and surface only what needs attention.
  • Delegate trafficking and changes: creating responsive search ads, adjusting budgets, adding and excluding keywords can all be executed from your instructions.

The work itself does get faster.

Where people get stuck with Google Ads

GAQL errors stop you One mistake in the syntax and the query fails with an error. Claude Code fixes and re-runs most of them, but the more complex the aggregation, the more likely the numbers that come back differ from what you meant. Rather than taking returned numbers at face value, it is safer to check them once against your own instinct.

Changes that “pass as plausible” are the bigger problem Failing with an error is actually the easier case, because you notice. The troublesome case is a change that looks about right but is actually off the mark, going through as is. Requiring approval or setting a ceiling on anything that touches bids or budgets keeps the damage from spreading.

No record of why a change was made “Why did you move this budget last week?” When you are asked later, you cannot answer if there is no log of the changes the AI made. Because ad ops is judged on reasons as well as results, designing for changes to be recorded pays off later.

Summary

Connecting Google Ads to Claude Code is not difficult once you clear the hurdles. What matters more is deciding, after connecting, how much to delegate and what to record. That is explored in Is it safe to hand ad ops to Claude Code?. We build mureo, which productizes this “design for delegation,” so you can talk to us not only about how to connect but about how to structure operations.