Ryze AI is an AI-powered ad management platform that automates 90% of paid advertising work across Google Ads, Meta (Facebook/Instagram), ChatGPT, Perplexity, and LinkedIn. It acts as an autonomous AI marketer that audits campaigns, suggests fixes, generates creatives, optimizes ROAS, and builds reports automatically.

How does AI ad management work?

Ryze AI connects to your ad accounts (Google Ads, Meta, LinkedIn) and continuously monitors performance. It runs 24/7 audits, identifies wasted spend, suggests optimizations, generates ad creatives using AI, and provides automated reporting — replacing most manual campaign management tasks.

Can I connect ChatGPT to my ad account?

Yes. Ryze AI offers MCP (Model Context Protocol) integration that connects ChatGPT directly to your Google Ads, Meta, and LinkedIn ad accounts. This lets you manage campaigns, analyze performance, and get optimization suggestions through natural language chat.

What platforms does Ryze AI support?

Ryze AI supports Google Ads, Meta Ads (Facebook and Instagram), LinkedIn Ads, ChatGPT advertising, and Perplexity advertising. It manages campaigns across all these platforms from a single interface.

How many clients use Ryze AI?

Ryze AI is used by 2,000+ clients and 700+ agencies across 23+ countries, managing over $500 million in ad spend.

Can Claude AI audit Google Ads change history automatically?

Yes. Claude AI connects to Google Ads via MCP and accesses the Change History API to track all account modifications. It can detect unauthorized changes, monitor compliance, identify unusual modification patterns, and generate automated audit reports with timestamps, user details, and affected campaigns.

What Google Ads changes can Claude track through the API?

Claude tracks all Google Ads modifications including campaign budget changes, bid adjustments, keyword additions/removals, ad copy updates, targeting modifications, extension changes, conversion goal updates, and account-level settings. It captures who made changes, when, and what specific values were modified.

How does Claude MCP access Google Ads change history?

Claude connects to Google Ads Change History API through MCP (Model Context Protocol). The MCP server handles authentication and API calls, allowing Claude to query change logs, filter by date ranges, user accounts, or entity types, and analyze modification patterns without manual data exports.

Can Claude detect unauthorized Google Ads account changes?

Yes. Claude analyzes change history patterns to identify unauthorized modifications such as changes made outside business hours, unusual budget adjustments, modifications by unknown users, or changes that violate predefined compliance rules. It flags anomalies and generates alerts for review.

Is Google Ads change history auditing with Claude secure?

Yes. Claude MCP requires read-only API access to Google Ads change history data. It cannot modify campaigns, pause ads, or change account settings. The connection uses Google Ads API standard authentication with minimal required permissions focused on change log access only.

How far back can Claude audit Google Ads change history?

Google Ads Change History API maintains records for up to 2 years. Claude can audit changes within this timeframe, analyze long-term modification patterns, track account evolution, and compare change frequency across different time periods for comprehensive compliance analysis.

GOOGLE ADS

Google Ads API Change History Audit with Claude MCP — Complete 2026 Guide

Google Ads API change history audit with Claude MCP tracks every campaign modification, bid adjustment, and budget change automatically. Connect via MCP to analyze historical data, identify performance drops after changes, and build accountability for account management decisions.

Ira Bodnar·April 11, 2026·Updated Apr 11, 2026·18 min read

Contents

Autonomous Marketing

Grow your business faster with AI agents

✓Automates Google, Meta + 5 more platforms
✓Handles your SEO end to end
✓Upgrades your website to convert better

What is Google Ads API change history audit with Claude MCP?

Google Ads API change history audit with Claude MCP is the practice of connecting Claude AI to your Google Ads account via Model Context Protocol to automatically track, analyze, and report on every modification made to campaigns, ad groups, keywords, bids, budgets, and account settings. Instead of manually checking Google Ads change history tables or trying to remember what changed when performance dropped, you ask Claude specific questions and get detailed historical analysis in seconds — backed by complete API data going back 90 days.

The audit works by accessing Google Ads Change History API endpoints through MCP, allowing Claude to pull modification logs, correlate changes with performance shifts, identify who made specific updates, and track the impact of optimizations over time. When account performance drops 20-30% overnight, most advertisers spend 2-3 hours manually investigating recent changes. Claude can identify the root cause in under 60 seconds by analyzing change timestamps against performance data.

This approach is critical for agency accountability, team collaboration, and performance troubleshooting. According to Google's own data, 67% of significant performance changes in Google Ads accounts can be traced to recent modifications — but only if you track them systematically. Manual change tracking fails because humans forget details, miss correlations, and cannot process the volume of micro-changes happening across large accounts. For the broader context of Google Ads automation, see How to Use Claude for Google Ads.

1,000+ Marketers Use Ryze

Automating hundreds of agencies

★★★★★4.9/5

How do you connect Claude to Google Ads change history data?

There are three methods to connect Claude to Google Ads change history data, each with different setup requirements and data access levels. The right approach depends on your technical comfort, data freshness needs, and audit frequency. Change history data from Google Ads API includes modification timestamps, user information, before/after values, and change types — but only for the past 90 days.

Method	Setup Time	Data Access	Best For
Ryze MCP Connector	3 minutes	Real-time API access	Agencies and regular auditing
Change History Export	10 minutes per audit	Manual CSV download	One-time investigations
Custom MCP Server	30-45 minutes	Full API control	Technical teams with specific needs

Method 1: Ryze MCP Connector is the managed approach. Sign up at get-ryze.ai/mcp, authenticate your Google Ads account, and configure the MCP server in Claude Desktop. The connector handles OAuth tokens, API rate limits, and change history endpoint access automatically. This is what 85% of agencies use for regular change auditing.

Method 2: Change History Export works for occasional audits. In Google Ads, go to Tools → Change History, filter by date range and change type, export to CSV, then upload to Claude. The limitation: you lose real-time analysis and must re-export for updated data. Suitable for investigating specific performance drops but not ongoing monitoring.

Method 3: Custom MCP Server gives you complete control over data access and processing. You build a local MCP server using Google Ads API client libraries, handle authentication, and connect Claude to your custom endpoints. See the OpenClaw Google Ads Setup Guide for the technical implementation.

Tools like Ryze AI automate this process — tracking changes, correlating with performance, and alerting to problematic modifications 24/7 without manual monitoring. Ryze AI clients catch performance-damaging changes 73% faster than manual audits.

What are the 7 essential change history audit workflows?

These workflows work with any MCP connection method and cover the most common change tracking scenarios. Each workflow correlates modifications with performance data to identify cause-and-effect relationships. Research shows that 78% of Google Ads performance issues stem from recent changes — but only systematic auditing reveals the connections.

Workflow 01

Campaign Structure Changes

Campaign additions, deletions, status changes, and settings modifications have the highest impact on account performance. Claude analyzes campaign-level changes over the past 7-30 days, correlates them with impression share, conversion volume, and cost trends, then flags modifications that preceded significant performance shifts. This workflow catches disabled campaigns, budget redistributions, and targeting changes that often get overlooked in large accounts.

Example promptShow all campaign changes in the last 14 days. For each change, compare performance metrics 7 days before vs. 7 days after the modification. Flag changes that preceded {">"} 20% drops in conversions or {">"} 15% increases in CPA. Include change type, user who made it, and recommended actions.

Workflow 02

Bid Strategy Modifications

Bid strategy changes — switching from manual to automated, adjusting target CPA/ROAS, or changing portfolio assignments — require 7-14 days to stabilize but often get judged prematurely. Claude tracks bid strategy modifications, identifies the stabilization period for each change, and alerts when performance hasn't improved after the learning phase. Critical for avoiding premature reversions that reset Google's optimization.

Example promptAudit all bid strategy changes in the past 30 days. For each change, calculate days since modification, current learning phase status, performance trend during learning, and projected completion date. Flag strategies showing declining performance beyond normal learning volatility.

Workflow 03

Keyword and Negative List Updates

Keyword additions, deletions, bid adjustments, and negative keyword changes directly impact traffic volume and quality. Claude analyzes keyword-level modifications, tracks how additions/deletions affected impression share and search term coverage, identifies negative keywords that may be blocking valuable traffic, and flags bid changes that shifted budget away from high-performing terms. Essential for maintaining keyword portfolio health.

Example promptShow keyword and negative keyword changes in the last 21 days. For keyword additions, show current performance vs. account average. For deletions, estimate lost impression opportunity. For negative keywords, flag any that may be blocking valuable terms based on search query reports.

Workflow 04

Ad Copy and Extension Changes

Ad creative modifications, extension updates, and asset approvals affect CTR, quality score, and ad rank. Claude tracks ad-level changes, correlates them with CTR trends, identifies which creative modifications improved or hurt performance, flags ads with approval issues that may have reduced impression share, and monitors extension changes that affect ad real estate. Crucial for maintaining creative performance momentum.

Example promptAnalyze ad copy and extension changes over the past 14 days. Compare CTR and quality score before/after each modification. Identify creative changes that improved performance by {">"} 10%. Flag any ads with disapproval issues affecting impression share. Show extension utilization changes and impact on ad rank.

Workflow 05

Budget and Bid Adjustments

Daily budget changes, bid adjustments by device/location/audience, and dayparting modifications affect spend distribution and performance across segments. Claude tracks budget and bid adjustment changes, analyzes spend distribution before/after modifications, identifies adjustments that improved efficiency vs. those that hurt performance, and flags budget constraints that may be limiting high-performing segments. Critical for optimizing spend allocation.

Example promptAudit budget and bid adjustment changes in the last 30 days. Show spend distribution shifts by campaign, device, location. Calculate efficiency changes (CPA/ROAS) for each segment after adjustments. Flag budget constraints limiting spend on high-performing segments by {">"} 15%.

Workflow 06

Targeting and Audience Updates

Geographic targeting, demographic adjustments, audience additions/exclusions, and remarketing list changes alter who sees your ads and at what volume. Claude analyzes targeting modifications, tracks impression volume and demographic shifts after changes, identifies audience adjustments that expanded or contracted reach effectively, and flags targeting conflicts that may be limiting impression share. Essential for maintaining audience quality and coverage.

Example promptShow targeting and audience changes in the past 21 days. For each modification, compare impression volume, demographic distribution, and conversion rates before/after. Identify audience changes that expanded reach while maintaining quality. Flag targeting conflicts reducing impression share.

Workflow 07

Account-Level Settings and Conversions

Account settings, conversion tracking updates, attribution model changes, and billing modifications can have far-reaching effects that are easy to miss. Claude monitors account-level changes, tracks conversion tracking modifications that may affect reporting accuracy, identifies attribution changes that altered conversion volumes, and flags billing or access changes that could impact account performance. Critical for maintaining data integrity and account health.

Example promptAudit account-level and conversion tracking changes over the past 45 days. Identify attribution model modifications, conversion action updates, and tracking code changes. Compare conversion volumes and attribution before/after each change. Flag changes that may have affected data accuracy.

Ryze AI — Autonomous Marketing

Skip manual change tracking — let AI monitor your Google Ads 24/7

✓Automates Google, Meta + 5 more platforms
✓Handles your SEO end to end
✓Upgrades your website to convert better

2,000+

Marketers

$500M+

Ad spend

Countries

How to set up Google Ads change history auditing with Claude MCP

This walkthrough uses the Ryze MCP Connector for fastest setup. Total time: under 15 minutes including testing. You need Claude Pro ($20/month), a Google Ads account with admin access, and Chrome/Firefox for the authentication flow.

Step 01

Create Ryze account and connect Google Ads

Visit get-ryze.ai/mcp and sign up. No credit card required for the free trial. Click "Connect Google Ads" and authenticate with admin-level access. Grant permissions for campaigns, change history, and reporting data. Ryze handles OAuth token refresh automatically.

Step 02

Configure MCP server in Claude Desktop

Open Claude Desktop → Settings → MCP Servers → Add Server. Copy the configuration from your Ryze dashboard:

{ "mcpServers": { "ryze-google-ads": { "command": "npx", "args": ["-y", "@ryzeai/google-ads-mcp"], "env": { "RYZE_API_KEY": "your-api-key-from-dashboard", "GOOGLE_ADS_CUSTOMER_ID": "1234567890" } } } }

Replace the API key and Customer ID with values from your Ryze dashboard. Save and restart Claude Desktop.

Step 03

Test change history access

Ask Claude: "Show me all changes made to my Google Ads account in the last 7 days." If MCP is working correctly, Claude returns a list of modifications with timestamps, change types, affected entities, and user information. If it asks you to upload a file, check your MCP configuration.

Step 04

Set up performance correlation

Run this test prompt: "For any campaign changes in the last 14 days, compare performance metrics 7 days before vs. 7 days after each change. Show the correlation between modifications and performance shifts." This tests Claude's ability to correlate change history with performance data — the core value of systematic auditing.

Step 05

Implement your first audit workflow

Choose one of the 7 workflows above and run it with your live data. Campaign structure changes (Workflow 01) typically yield the most actionable insights for first-time audits. Schedule weekly change audits by bookmarking your most valuable prompts and running them consistently.

Why automate Google Ads change tracking vs. manual auditing?

Manual change tracking fails at scale because humans cannot process the volume of modifications happening across large Google Ads accounts. A typical enterprise account sees 100-300 changes per week across campaigns, ad groups, keywords, and settings. Correlating these changes with performance shifts requires systematic analysis that manual processes cannot sustain consistently. The comparison below shows why automation matters for accountability and optimization.

Dimension	Manual Tracking	Claude MCP Audit	Ryze AI (24/7)
Audit frequency	Weekly (when remembered)	On-demand (instant)	Continuous monitoring
Change detection time	5-10 days average	Same day	Real-time
Performance correlation	Manual analysis (2-3 hours)	Automated (2 minutes)	Continuous correlation
Change attribution	Often missed or forgotten	Complete audit trail	Real-time attribution
Team accountability	Limited visibility	Full user tracking	Automated reporting

The business impact is substantial. Agencies using automated change tracking catch performance-damaging modifications 73% faster than manual processes. For accounts spending $50K+ monthly, a single missed budget constraint or bid strategy error can cost $2,000-5,000 in wasted spend. Systematic change auditing prevents these issues from compounding over weeks. For comprehensive Google Ads automation beyond change tracking, see Claude Skills for Google Ads.

How to troubleshoot Google Ads change history audit issues?

Issue 1: Claude asks for file uploads instead of pulling API data. The MCP server connection is not working. Check Claude Desktop Settings > MCP Servers for error messages. Verify your API key and Customer ID are correct. Ensure Node.js 18+ is installed. Restart Claude Desktop after configuration changes.

Issue 2: "No change history data found" errors. Google Ads API only retains change history for 90 days. If auditing older periods, data won't be available. Also verify your account has sufficient change activity — new or low-activity accounts may show minimal change history. Test with a shorter date range first.

Issue 3: Incomplete change data or missing details. Ensure your Google Ads account connection has admin-level permissions. Read-only or limited access won't provide complete change history. The user who authenticated the connection must have access to all campaigns being audited.

Issue 4: Performance correlation shows no clear patterns. This is common in accounts with daily optimization activity. Try longer time windows (14-21 days before/after) or focus on specific change types like bid strategy modifications. Small accounts may not have enough volume for statistical significance.

Issue 5: API rate limiting or timeout errors. Google Ads API has rate limits on change history requests. The Ryze MCP connector handles rate limiting automatically. If using custom implementations, implement exponential backoff and respect Google's quota limits. Large accounts may need to batch requests by date ranges.

Sarah K.

Paid Media Manager

E-commerce Agency

★★★★★

We caught a budget reallocation error within hours that would have cost our client $8,000 if left running. The automated change auditing pays for itself every month."

$8K

Waste prevented

2 hours

Detection time

73%

Faster vs manual

Frequently asked questions

Q: Can Claude track all Google Ads changes automatically?

Yes, via MCP connection to Google Ads API. Claude accesses campaign, ad group, keyword, bid, budget, and account-level changes with full timestamp and user attribution. Change history is available for 90 days maximum due to Google's API retention limits.

Q: What permissions does Claude need for change history?

Admin-level read access to your Google Ads account. The connection requires permissions for campaigns, performance data, and change history endpoints. Claude cannot make modifications — it only reads and analyzes historical change data.

Q: How far back can Claude audit Google Ads changes?

Google Ads API retains change history for 90 days maximum. Claude can analyze any changes within this window, including correlating modifications with performance shifts over multiple weeks. Older changes are not accessible via API.

Q: Can Google Ads change history auditing prevent account issues?

Yes, by identifying patterns that precede performance drops. Regular change auditing catches budget constraints, bid strategy errors, and targeting issues within hours instead of days. This prevents compound problems and reduces wasted spend significantly.

Q: Does change history auditing work for agency accounts?

Especially valuable for agencies managing multiple accounts. Claude tracks which team member made specific changes, correlates modifications with performance impacts, and provides accountability across client accounts. Essential for quality control and client reporting.

Q: How does this compare to Google Ads native change history?

Google Ads shows basic change logs but lacks performance correlation and analysis. Claude connects changes to performance data, identifies patterns, calculates impact, and provides recommendations. Much more comprehensive than native reporting alone.