← All articles
Guides · 8 min read

How to Connect Claude to Google Ads

M

Metrifact Team

September 9, 2026

A practical walkthrough for connecting Claude to Google Ads through Metrifact: the OAuth setup, what permissions it actually grants, real prompts for finding wasted spend, and how the confirm-before-applying flow works once you ask Claude to fix something.

Metrifact connects Claude to your Google Ads account so you can ask questions in plain English and get answers pulled from live account data. Setup takes about two minutes: no API key, no code, just an OAuth login. Claude finds the problem: a search term burning budget, a keyword with a terrible cost-per-conversion. Metrifact applies the fix once you’ve confirmed it in the conversation. Nothing changes on its own.

Connect Claude to Metrifact

No API key needed. OAuth handles login and account access entirely inside Claude.

Remote server URL

https://app.metrifact.com/mcp

What you’ll need

  • A Google Ads account you have edit access to. A direct account or one reached through a manager login both work
  • Claude.ai or Claude Desktop
  • About two minutes. No API key, no code to write

Note

Connecting grants Claude the same access level your Google login already has on that account. Reading data works immediately: campaigns, keywords, search terms, spend, all of it. Write actions, like pausing a keyword or changing a budget, still need your explicit confirmation in the conversation before anything is applied. Connecting the account is not the same as handing over blanket write access.

Connect Claude to Google Ads

Every connection uses Google’s own OAuth flow. You log in directly with Google, not with Metrifact. Metrifact never stores your Google password. What comes back is a scoped access token, not your credentials.

  1. Open Settings, then Connectors

    Inside Claude, go to Settings and select Connectors.

  2. Choose Add custom connector

    This opens the form where you’ll paste Metrifact’s connector URL.

  3. Paste the URL below, then select Add

    Use https://app.metrifact.com/mcp as the connector URL.

  4. Log in and approve access

    Claude opens an authorization window. Log in with the Google account tied to your ads account, then approve access to continue.

Once you’re back in Claude, ask it to list your connected accounts before doing anything else. That confirms the right account made it through the connection.

If your login is a manager (MCC) account rather than a single client account, you’ll likely see more than one account to choose from during setup. That’s expected, not an error. It’s covered in more detail in the troubleshooting section below.

Analyze your account

Once you’re connected, ask Claude to look at something specific. Vague requests get vague answers. Specific requests get specific findings.

Returns the search terms that spent over $500 with zero conversions

Show me every search term that’s spent more than $500 in the last 30 days with zero conversions.

Ranks every keyword by cost-per-conversion, worst first

Which keywords have the highest cost-per-conversion this month?

Shows exactly which campaigns moved most, week over week

Compare this week to last week and tell me which campaigns changed the most.

Each of these pulls real numbers from the account you connected. Claude isn’t summarizing a report you’d have to go find yourself. It’s running the query and handing you the rows that matter, not a paragraph about how things are “trending.”

Worth knowing: if your account is lead-gen rather than ecommerce, Google Ads doesn’t expose a standard ROAS field. Ask for it anyway and Claude will say the field isn’t there, rather than estimating a number that doesn’t exist.

If the conversion count here doesn’t match what Shopify or GA4 shows for the same period, that’s expected, not a bug: see Stop trusting platform-reported ROAS. Use MER. for why, and what to check instead.

How changes are approved

Nothing above changes anything. Finding a problem and fixing it are two separate steps, on purpose.

Note

When you ask Claude to make a change, Metrifact prepares the exact edit and shows it to you before touching your account. You confirm it in the conversation, and then it’s applied. Nothing runs silently. A budget increase of more than 3x the campaign’s current value needs a separate, explicit acknowledgment on top of the normal confirmation, so a misread instruction can’t quietly triple your spend. That confirmation is also short-lived. If you walk away mid-conversation, you’ll need to ask again once you’re back.

In practice: you ask Claude to pause a keyword, and it names the exact keyword, the ad group it lives in, and what changes if you say yes. You confirm it or you don’t. Nothing sits half-applied. If you say nothing, the request simply expires.

Act on what you find

Same three findings from above. This time, fix them.

Excludes them without touching anything else in the account

Add those as phrase-match negatives.

Pauses just the keywords dragging down that average

Pause the three worst of those keywords.

Applies the cut, nothing else in that campaign changes

Cut that campaign’s daily budget from $200 to $120.

Notice the prompts don’t repeat account, campaign, or keyword details. Claude already has them from the conversation above.

Pausing a keyword or a campaign isn’t permanent. Ask Claude to re-enable it later and it will. Removing something outright is a separate, explicitly labeled action, and that one can’t be undone the same way.

Every one of these calls still goes through the same preview-then-confirm step described above. Analyzing and acting aren’t two different modes with different rules. They’re the same conversation, and the write half of it is just slower on purpose.

One honest limit worth stating plainly: Metrifact doesn’t run on a schedule of its own. It only acts inside a conversation you’re actively having with Claude. There’s no background job doing it between conversations.

Troubleshooting

I logged in with a manager (MCC) account. Which account do I connect? +

Google’s own login shows Metrifact every account your login can access, which for a manager account usually means more than one. When that happens, you’ll see a selection screen with a checkbox next to each account. Pick the specific client account (or accounts) you actually want to work with, not the manager account itself unless that’s genuinely what you meant to connect. If you’re not sure which one is which, cancel and check the account names in Google Ads first rather than guessing.

I connected the wrong account +

Disconnect it from your account settings and reconnect, choosing only the account you meant this time. Removing a connection deletes its stored credential immediately, so there’s nothing left over from the first attempt sitting around unused.

The OAuth window closed without finishing login +

This is usually a pop-up blocker. Allow pop-ups for claude.ai and try connecting again. If it still doesn’t open, check that you’re not already signed into a different Google account in the same browser session than the one you meant to use.

My confirmation expired before I approved it +

Confirmations are short-lived on purpose, so a change can’t sit half-approved indefinitely waiting for someone to come back to it. Just ask Claude to prepare the change again and confirm it right away. Nothing from the expired attempt carries over or applies on its own.

Claude asked me to acknowledge a large budget increase I wasn't expecting +

That’s the magnitude check, not a bug. Any budget increase of more than 3x the current value needs a separate acknowledgment before it goes through. If the number looks wrong, say so instead of confirming. That’s exactly what the check exists to catch: usually a misread instruction rather than an intended change.

Claude says it can't do something I know Metrifact supports +

Claude reads the list of available tools once, when it connects, not on every message. If we ship a new capability after your session connected, that session keeps using the list it started with. The fix is live on our end. Disconnect Metrifact in your account settings and reconnect to pick it up. One reconnect doesn’t always take effect right away, so if the capability still isn’t there, disconnect and reconnect again rather than assuming something’s wrong.

If you also run Meta Ads, the setup is nearly identical: see How to Connect Claude to Meta Ads.

FAQ

Do I need to install anything to connect Claude to Google Ads? +

No. Metrifact is hosted, so you paste a URL into Claude and sign in. There’s no server to run and nothing to keep updated on your end.

Is my Google Ads data used to train any AI model? +

No. Your account data is retrieved live for each request, not copied into a separate database of its own, and never sold, shared with third parties, or used to train any AI or ML model.

Can Claude change my campaigns without asking me first? +

No. Every write action goes through a preview step first, and nothing is applied until you explicitly confirm it in the conversation. That confirmation also expires automatically after a short window if you don’t use it, so it can’t sit around waiting.

Can I connect a manager (MCC) account, or do I need to log in separately for every client? +

You can connect through a manager login. Metrifact lists every account that login can access and lets you pick which ones to actually connect, rather than assuming you want all of them at once.

Will connecting Metrifact get my Google Ads account flagged or restricted? +

Metrifact only uses Google’s own official OAuth API, the same access model any approved third-party tool uses, paced under internal limits set below what Google allows specifically to avoid tripping automated abuse detection. It never asks for your password and can’t bypass Google’s own account policies.

Can I connect accounts for multiple clients if I run an agency? +

Yes. Connect using your own login and each client account you have access to shows up in your workspace. If a client would rather not hand you their login, they can connect their own account instead and share access with you that way. Removing a connection later deletes its stored credential immediately, not on some delayed schedule.

Try it on your own accounts

Connect Google Ads, Meta, GA4, Search Console and Shopify to Claude in two minutes. 7-day trial, no card.

Start free trial
M

Metrifact Team

September 9, 2026