Set Up Claude for Google Ads Analysis

Claude can turn a Google Ads account into a plain-English analysis layer. Instead of exporting data, cleaning spreadsheets, and building decks, you ask a question and get a structured answer fast.

This guide explains the connection choices, the quickest setup path, and the work you can hand off once Claude can read your account data.

Why this setup matters

Connecting Claude to Google Ads replaces a lot of repetitive reporting with near-instant analysis. Rather than spending hours each week pulling numbers into shape, you can request what you need and get a clean response in under 30 seconds.

What you gain:

• Live optimization: Access current account data for quicker decisions.
• Automated reporting: Create executive-ready summaries without manual assembly.
• Faster decisions at scale: Get analysis you can act on quickly.
• Less repetitive work: Cut weekly admin from 12–15 hours to 2–3 hours.

Google Ads is also more complex than it used to be. Since 2020, account complexity has increased by 340% due to campaign formats such as Performance Max and Discovery, plus audience signals, smart bidding, and multiple attribution models. Doing all of that manually does not scale well. Claude helps manage that complexity while you keep control of strategy.

This article covers API setup, Managed Control Plane (MCP) configuration, 12 automation workflows, and a fix for a common setup issue.

Three ways to connect Claude to Google Ads

Your best option depends on your technical ability, how often you need updated data, and whether you want live access or a static export.

Easiest route: managed connector

This is the simplest path. Create an account, sign in with Google, and use the provided MCP server endpoint. This option handles OAuth token refresh, API rate limiting, and data formatting. For most marketers, this is the most reliable low-friction setup.

Full-control route: self-hosted API connection

If you want to manage everything yourself, build the connection directly. That means creating a Google Cloud project, enabling the Google Ads API, generating OAuth credentials, and running your own local MCP server. You remove third-party dependency, but you also own the maintenance and debugging.

No-API route: CSV uploads

You can also skip the API and upload exports from Google Ads into Claude. This works well for ad hoc reviews, but the file is only a snapshot. Every update needs another export. It fits quarterly reviews and one-time competitor analysis better than ongoing account management.

Quickest path: use MCP

This is the fastest way to get Claude working with Google Ads.

You need:

• Claude Pro ($20/month)
• Access to your Google Ads account
• About 10–15 minutes

Step 1: Create your account

Finish signup with your email and business details.

The MCP connector includes a 7-day free trial and no credit card required. Your API credentials should arrive by email within minutes.

Step 2: Link your Google Ads account

Go to Integrations → Google Ads → Connect Account. Use Google OAuth to log in.

Approve access to:

• Campaign data
• Keyword insights
• Conversion tracking
• Audience demographics

If you manage multiple accounts, start with your primary one. Add the others later.

Access level matters:

• Admin or Standard access enables full functionality.
• Read-only access limits what Claude can do.

Step 3: Install Claude Desktop

Download Claude Desktop from claude.ai/desktop and sign in with your Claude Pro account.

This is required because MCP server connections work in Claude Desktop, not in the web app. After installation, open the app and make sure your conversation history appears as expected.

Step 4: Add the MCP connection

In Claude Desktop, open:

Settings → Features → MCP Servers → Add Server

Copy the configuration from the dashboard and paste it into the config field. It should look like this:

{
  "mcpServers": {
    "google-ads": {
      "command": "npx",
      "args": [
        "-y",
        "@google-ads-mcp"
      ],
      "env": {
        "API_KEY": "your_api_key_here",
        "GOOGLE_ADS_CUSTOMER_ID": "123-456-7890"
      }
    }
  }
}

Replace:

• "your_api_key_here" with your real API key
• "123-456-7890" with your Google Ads customer ID

You can find the customer ID in the top right corner of the Google Ads interface.

Step 5: Test the connection

Restart Claude Desktop so it loads the MCP server. Then open a new chat and enter:

"Show me my Google Ads performance for the last 7 days."

If the setup is correct, Claude should return a formatted table of campaign metrics. If it does not work, check these two things first:

• Your MCP configuration
• Your Google Ads connection in the dashboard

Step 6: Confirm wider account access

Run a few extra prompts to verify everything is working.

Examples:

• "List my top 10 keywords by cost"
• "Show campaign performance compared to last month"
• "Analyze my Quality Scores by ad group"

Each request should return useful output within 10–15 seconds. If some prompts work and others fail, review your Google Ads permissions and API quotas.

Twelve useful jobs Claude can automate

These workflows target the tasks that usually consume the most time in account management. Used properly, they can reduce weekly work from roughly 15 hours to under 3 hours.

1. Review Quality Score and prioritize fixes

Claude can scan active keywords, group Quality Scores into ranges, identify the main problem, and suggest fixes tied to ad relevance, landing pages, and CTR.

A change from Quality Score 6 to 8 can reduce CPC by 16–20%.

Prompt:

"Analyze Quality Scores for all active keywords. Group by score ranges (1-3, 4-6, 7-10). For keywords with scores below 7, identify the primary issue (relevance, CTR, landing page) and provide specific improvement recommendations. Prioritize by impression volume and cost impact."

2. Mine search terms and build negative lists

Claude can sort search terms reports into productive queries and wasteful ones. That helps you promote strong terms into exact match keywords and block irrelevant traffic with negatives.

Prompt:

"Review search terms report for the last 30 days. Identify: 1) High-performing terms (good CTR, conversions) to add as keywords 2) Irrelevant terms consuming budget to add as negatives 3) Terms with high impressions but low CTR that need investigation. Export as two lists: 'Add Keywords' and 'Add Negatives'."

3. Recommend bid adjustments

For manual campaigns and bid modifiers, Claude can compare results by device, geography, daypart, and audience. It can then recommend bid changes based on conversion rate, margins, and competitive pressure.

Prompt:

"Analyze bid performance across all dimensions: keywords, devices, locations, time periods, audiences. Identify segments performing above/below target ROAS. Recommend specific bid adjustments (% increase/decrease) for each underperforming segment. Include expected impact on volume."

4. Evaluate Responsive Search Ad assets

Claude can review RSA headlines and descriptions, rank them by CTR, conversion rate, and impression share, and suggest new variants based on the themes already winning.

Prompt:

"Analyze ad asset performance for all RSAs. Rank headlines and descriptions by CTR, conversion rate, and impression share. Identify top-performing messaging themes and patterns. Suggest 5 new headline variants based on winning elements. Flag poor-performing assets for replacement."

5. Audit account structure

This workflow finds structural problems such as keyword cannibalization, poor budget distribution, and weak ad group organization. It can also point out where to consolidate or expand.

Prompt:

"Audit my account structure. Check for: 1) Campaigns with >20 ad groups (may need splitting) 2) Ad groups with <3 keywords (consolidation opportunities) 3) Keyword overlap between ad groups causing cannibalization 4) Ad groups mixing different match types ineffectively. Provide restructuring recommendations with priority levels."

6. Reallocate budget more effectively

Claude can estimate marginal ROAS by campaign and recommend budget shifts based on performance potential, seasonality, conversion lag, and competition.

Proper reallocation can improve total ROAS by 15–25%.

Prompt:

"Analyze budget utilization across all campaigns. Calculate: 1) Budget-limited campaigns with strong performance 2) Campaigns with unused budget and poor performance 3) Marginal ROAS for potential budget increases/decreases. Recommend specific budget adjustments ($amounts) to maximize overall account performance."

7. Monitor Auction Insights

Claude can parse Auction Insights data to find rising competitors, falling positions, and openings where others have reduced activity.

Prompt:

"Analyze Auction Insights data for top-spending campaigns. Identify: 1) Competitors gaining impression share vs. last quarter 2) Keywords where our position has declined significantly 3) New competitors appearing in our auctions 4) Opportunities where competitors have reduced presence. Recommend strategic responses for each finding."

8. Diagnose landing page performance

Claude can connect ad traffic results to landing page behavior and flag URLs that win clicks but fail to convert. It can compare bounce rate, time on page, and conversion paths to suggest page improvements or traffic shifts.

Prompt:

"Analyze landing page performance by final URL. Compare: 1) Click volume versus conversion rate for each page 2) Cost per conversion by landing page 3) Quality Score impact of different landing pages 4) Pages with high traffic but poor conversion rates. Recommend traffic redistribution and page optimization priorities."

9. Find stronger audience opportunities

This workflow reviews performance across demographics, interests, remarketing lists, and Customer Match audiences. It helps identify segments worth breaking into dedicated campaigns, plus similar audiences to test next.

Prompt:

"Analyze audience performance across all campaigns: 1) Demographics performing above/below account average 2) Interest categories with strong conversion rates 3) Remarketing lists with highest lifetime value 4) Custom audiences ready for expansion. Recommend new audience segments to test and poor performers to exclude."

10. Audit conversion tracking

Claude can inspect your conversion setup for duplicate actions, suspicious values, missing Enhanced Conversions, and mismatches between Google Ads and Google Analytics.

Prompt:

"Audit conversion tracking setup: 1) Check for duplicate or overlapping conversion actions 2) Identify conversions with suspiciously low/high values 3) Compare conversion volumes to expected business metrics 4) Review Enhanced Conversions implementation status. Flag potential tracking issues and recommended fixes."

11. Produce weekly stakeholder reports

Claude can generate reports for executives, including trend summaries, campaign performance versus targets, market changes, and next steps. It can also explain major swings automatically.

Prompt:

"Generate weekly performance report for [date range]: 1) Executive summary with key metric changes 2) Campaign-level performance vs. targets 3) Top 3 wins and top 3 concerns 4) Competitive landscape changes 5) Specific action items for next week. Format for C-level audience with business impact focus."

12. Run a full account health check

This workflow performs a broad diagnostic across policy issues, bidding performance, learning phases, limited-data campaigns, budget constraints, and Google optimization recommendations. Claude can rank issues by urgency and business impact.

Prompt:

"Perform comprehensive account health diagnostic: 1) Policy violations or disapproved ads/keywords 2) Bid strategies not meeting performance thresholds 3) Campaigns/ad groups with learning phases or limited data 4) Budget constraints limiting growth potential 5) Optimization recommendations from Google. Rank issues by business impact and urgency."

Fix the most common setup error

If Claude says it cannot find the MCP server

If you get an "MCP server not found" error, Claude Desktop cannot locate or start the MCP server.

Check the following:

1. Make sure Node.js 18+ is installed.
2. Review the MCP config in Claude Desktop for typos.
3. Confirm the JSON structure matches the Step 4 example.
4. Verify the google-ads object and its contents are formatted correctly.

Key takeaways

• The quickest route is the MCP Connector, with setup in under 5 minutes.
• If you want maximum control, use the Google Ads API + self-hosted MCP option.
• CSV exports are fine for one-time reviews, but they are not live.
• Claude Desktop is required because the web app does not support MCP connections.
• With the right prompts, Claude can automate reporting, audits, budget analysis, bidding reviews, and more.