Use Claude with Google Ads: a reporting and approval workflow

Prepare the account before opening Claude

Connect Google in the Adport project for the brand or client. Save the account selection and enable the accounts Claude should access. Keep client projects separate, even if one Google manager login can see several businesses.

Write down the account's reporting currency, the primary conversion you care about, and the business question for this review. For a lead-generation account, that might be qualified inquiries rather than every form event. For ecommerce, it might be purchase value with a clear treatment of refunds. Claude cannot resolve an undefined business objective by reading more rows.

Connect Claude Code with the hosted endpoint

For Claude Code, add Adport as an HTTP MCP server:

claude mcp add --transport http --scope user adport https://app.adport.dev/mcp

Complete Adport authorization for the intended project. In Claude Code, use /mcp to inspect the connection and authenticate when needed. Anthropic documents remote HTTP servers, scopes, and authentication.

User scope makes the configuration available across your local projects. It does not grant access to every Adport client project. The OAuth grant still determines the advertising workspace. If you use Claude's web or desktop connector interface instead, use the same hosted address and the current instructions in Adport's Agent access page.

Ask for evidence before asking for a change

Read the account list and period first. Then look for an explanation that distinguishes an observation from a hypothesis. A campaign spending more is an observation. A broken landing page is a hypothesis until you have checked the destination and its funnel data.

Ask for missing information explicitly. If conversion value is unavailable, the assistant should not invent ROAS. If one provider read failed or the result was truncated, the answer should say that its scope is incomplete.

Make the comparison fair

Compare periods of equal length with similar weekday coverage. Check whether the account changed budgets, conversion definitions, or bidding strategy during the comparison. Avoid combining currencies into a single spend total.

Recent clicks may convert later. Google explains how conversion lag can affect reported CPA and ROAS. Use a reporting window that fits the account's conversion cycle, and identify recent results as provisional. A quiet week in a low-volume account is a reason to investigate, not automatic evidence that a campaign should be paused.

Request one exact preview

Choose one supported action after you have reviewed the evidence. Specify the account, campaign, and requested values. Ask Claude to return the preview without applying it. The decision should be understandable without reading the entire chat.

If you approve, the applying call must match the previewed arguments and pending operation. If your intended values changed, get a new preview. Keep related proposals separate enough that you can accept one without accidentally accepting the others.

Verify the result and keep the review reusable

After an approved change, read the campaign again and check the audit history. Confirm what the platform accepted. Do not treat the model's statement that it is done as the only evidence.

Save a short review note with the reporting period, issue, decision, and follow-up date. On the next review, compare against that decision before creating another recommendation. For the underlying setup and permission checks, see the Google Ads MCP server guide. For a fuller review sequence, use the audit checklist.