To diagnose why a campaign is not delivering in Google Ads with Claude or ChatGPT, connect your Google Ads account to PaidSync.ai and ask the assistant to diagnose why a campaign is not delivering, which reads every status level Google exposes and lists the reasons. It checks the campaign, ad group, ad and keyword, plus budget, bidding, payment and ad policy. It only reads.
When a campaign shows no impressions, the cause can sit at four different levels. One tool checks them all:
diagnose_google_zero_delivery reads the status and status reasons at campaign, ad group, ad and criterion level, plus budget, bidding strategy, payment, conversion goals and ad policy.get_ad_policy_issues lists disapproved or under-review ads with their policy topics.get_spend_by_day returns spend per day, which shows exactly when delivery stopped.diagnose_google_zero_delivery, get_ad_policy_issues and get_spend_by_day only read your account.
| Tool | What it does |
|---|---|
| diagnose_google_zero_delivery | Finds the reasons a campaign is not serving |
| get_ad_policy_issues | Checks whether ads are disapproved |
| get_spend_by_day | Shows the day spend dropped |
The tool returns the raw reason Google sent, and labels how much each finding is worth, so a minor flag is not mistaken for the cause. It also checks spend over the lookback window, which confirms that delivery really stopped.
These steps use Claude to diagnose why a campaign is not delivering. PaidSync.ai also works in ChatGPT, and the prompts are the same.
Start at paidsync.ai, then link Google Ads through Google's own sign-in screen. No developer token and no Google Cloud project are involved. The login you choose must reach the account where you will diagnose why a campaign is not delivering.
Add PaidSync.ai from Claude's connector directory and sign in. Ask "list my Google Ads accounts" and choose the one to diagnose why a campaign is not delivering in.
Give the assistant the campaign, and narrow to an ad group or ad if you know where the problem sits.
Ask it to diagnose zero delivery. The result lists the reasons at each level with how much weight each deserves.
Deal with the most serious finding first, such as a disapproved ad, a budget of zero or a payment problem, then run it again.
Check the daily spend in the days after your fix. If spend returns, the diagnosis was right. If not, run the diagnosis again and read the next finding.
Use these two prompts to diagnose why a campaign is not delivering, in this order.
diagnose_google_zero_delivery, get_ad_policy_issues and get_spend_by_day only read the account, so nothing here edits a campaign.diagnose_google_zero_delivery, get_ad_policy_issues and get_spend_by_day 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 diagnose why a campaign is not delivering.
In Google Ads, check the campaign status, then the ad group, the ads and the billing settings in turn. With PaidSync.ai, ask Claude or ChatGPT to diagnose the campaign and it checks all of them at once.
Status and reasons at the campaign, ad group, ad and keyword level, plus budget, bidding strategy, payment mode, conversion goals and ad policy.
Yes. PaidSync.ai connects Google Ads to ChatGPT and to Claude, and the same tools run in both, so you can ask it to diagnose why a campaign is not delivering the same way you would in Claude.
A connected Google Ads account and the campaign. An ad group, an ad and a lookback window are optional.
PaidSync.ai is free for 15 tasks a month with no card, enough to diagnose why a campaign is not delivering 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