Date: 2026-04-15

Decision

Moved the google-ads-daily-negatives scheduled task off the Adspirer MCP (500 ops/day, 300 ops/hour cap) and onto direct Google Ads API calls via google-ads-python. Same credentials that power the local google-ads-mcp repo.

Why

Cleanup volume for SAIL - Car Accidents 2026 alone is 3,000+ ops (2,239 remaining removes + 251 adds). At Adspirer's rate cap that is 5-7 days of drain-the-queue. At the native API rate cap it is a single session.

Backend priority order (now in task prompt)

1. Direct Google Ads API via google-ads-python — credentials at /mnt/Projects/_repo-staging/claude-ads/.env and /mnt/Projects/_repo-staging/shared-infrastructure/.env.credentials
2. Local google-ads-mcp server at /mnt/Projects/_repo-staging/google-ads-mcp/
3. Pipedream Google Ads connector (if added to Cowork MCP list)
4. Adspirer MCP (last resort only)

Credentials reference

• MCC ID: 867-659-9345 (login_customer_id = 8676599345)
• Client account: 381-391-6687 (customer_id = 3813916687)
• Developer token: in .env.credentials
• OAuth client id + secret + refresh token: in claude-ads/.env
• Login email: aguiarlawmarketing@gmail.com

What changed

• Scheduled task prompt rewritten to list the four-backend priority order.
• CONTINUATION_STATE.md updated in the audit folder with a ready-to-run google-ads-python snippet for bulk CampaignCriterionService.mutate_campaign_criteria operations.
• Next run of google-ads-daily-negatives will use the direct-API path and should drain the remaining 2,239 removes + 251 adds in one pass.