Stop 1 of 9 · Set once
Connectors and the ten-minute audit
Wire Google Ads and GA4 to Claude, then get a ranked findings table for any account in ten minutes, read only.
What it is
Twelve accounts and one hour before the first call. Opening twelve interfaces is not an audit, it is a morning. This stop connects Claude to Google Ads and GA4 so it can read an account directly, and gives Nour one prompt that returns a ranked findings table in ten minutes. Everything here is read only, and the rule that runs through the whole course starts now: no bid, no budget and no status changes without a human doing the clicking.
Check the connector before you trust it
MCP is how Claude talks to an outside system: one server, one set of tools. Whether Claude can reach Google Ads or GA4 for your agency depends on what has been set up, and that changes. Before a client account goes near it, check three things and write the answers into the Account audits Project:
- Settings, Connectors: is there a built-in entry for the platform, or does your agency point Claude at a custom server?
- The tool list the connector shows as you add it: does it only read (list campaigns, get metrics, pull search terms), or does it also write (update budget, set status, add a negative)?
- Who operates the server, and where the token lives.
A write tool in the list is not a reason to skip the connector. It is a reason to finish stop 2 before you use it. If there is no connector for your platform, everything in this course still works from exports. The audit takes fifteen minutes instead of ten.
The six checks, in this order
| Check | The finding you want |
|---|---|
| Pacing against monthly budget | Projected month end, over or under, in dollars |
| Cost per lead, 7 days against 28 | Which campaigns moved, and by how much money |
| Search terms with spend, no conversions | A dollar total and the terms behind it |
| Performance Max asset groups | Where the spend actually went |
| GA4 landing pages by device | Where the click stops converting |
| Conversion actions and windows | Anything being counted twice |
Cheap findings first. By the time Nour reaches conversion windows she already knows whether this account is a pacing problem or a quality problem.
Try this
Using the Google Ads and GA4 connectors on [account name], read only. Cover the last 28 days against the previous 28. Work through these in order: pacing against monthly budget, cost per lead by campaign for 7 days against 28, search terms with spend over $25 and zero conversions, Performance Max spend by asset group, GA4 landing pages by device, and conversion actions with their attribution windows. Return one findings table with three columns: finding, dollars at risk this month, what to check next. Rank by dollars. Change nothing, and list any check you could not complete because the data was not available to you.
Take the top three findings from the audit above. For each, show me the rows and totals you used, the exact date range and the attribution window in force. Then tell me which of the three you are least confident about, and what evidence would change your mind.
Using the GA4 connector on [property name], read only. For the campaigns whose cost per lead rose in the audit, show sessions, engagement rate and key events by landing page and by device for the same 28 days. Tell me which of those campaigns has an ads problem and which has a landing page problem, and give me the single number that decides it.