To detect anomalies in Google Ads with Claude or ChatGPT, connect your Google Ads account to PaidSync.ai and ask the assistant to check the account for anomalies, which flags large changes against the previous week. It compares the last 7 days with the 7 before and flags changes of more than 20 percent in spend, CTR and conversions. It only reads.
An anomaly check tells you something moved before you notice it in a report. Claude runs the check, then digs into what changed:
detect_anomalies compares the last 7 days with the prior 7 and flags changes above 20 percent in spend, CTR and conversions.get_campaign_performance breaks results down by campaign so you can find which one moved.get_change_history shows who changed what and when, which often explains a swing.detect_anomalies, get_campaign_performance and get_change_history only read your account.
| Tool | What it does |
|---|---|
| detect_anomalies | Flags large week-on-week changes |
| get_campaign_performance | Locates the campaign behind a swing |
| get_change_history | Checks whether an edit caused the change |
A flag is not a fault. A drop in spend can follow a pause you chose, and a rise in conversions can follow a promotion. The value is that you are told, so you can check the change history and decide whether it is expected.
These steps use Claude to detect anomalies. PaidSync.ai also works in ChatGPT, and the prompts are the same.
Sign up at paidsync.ai, then connect Google Ads on Google's own sign-in screen. There is no developer token and no Google Cloud project. Use the Google login that has access to the account where you want to detect anomalies.
Open Claude's connector directory, add PaidSync.ai and sign in. Ask "list my Google Ads accounts", then pick the account where you will detect anomalies.
Ask the assistant to detect anomalies in the account. It compares two 7-day windows.
For each flag, ask for campaign performance to see which campaign moved, and the change history for recent edits.
Decide whether the swing is expected, needs a fix, or needs watching for another week.
Run the check again after a week and see whether the flagged items settled. Repeated flags on one campaign are a sign to look at it closely.
Use these two prompts to detect anomalies, in this order.
detect_anomalies, get_campaign_performance and get_change_history only read the account, so nothing here edits a campaign.detect_anomalies, get_campaign_performance and get_change_history work with a key that cannot change anything. Tokens are encrypted at rest.Every Google Ads tool PaidSync.ai offers is on the Google Ads MCP server page, including the tools used to detect anomalies.
In Google Ads, compare two date ranges in the campaigns table and look for large changes. With PaidSync.ai, ask Claude or ChatGPT to run the anomaly check and it lists the flagged metrics.
A change of more than 20 percent between the last 7 days and the 7 days before, in spend, CTR or conversions.
Yes. PaidSync.ai connects Google Ads to ChatGPT and to Claude, and the same tools run in both, so you can ask it to detect anomalies the same way you would in Claude.
A connected Google Ads account. The check needs at least two weeks of data to compare.
PaidSync.ai is free for 15 tasks a month with no card, enough to detect anomalies and see the result. Pro starts at $99 a month. See pricing.
PaidSync.ai runs 630+ tools across 14 ad and analytics platforms. Connect your accounts once and use them in the AI assistant you already work in.
Get Started Free Book a Demo