How to connect Google Ads to Claude: no code, no terminal

The Google Ads interface shows data but does not interpret it. Claude interprets but cannot see the data. Most advertisers lose time copying between the two; the exported table is stale before it reaches Claude.

Once connected, that split disappears: Claude pulls the current data itself, answers in context and, where needed, presents the change as a preview.

Tecrube’s MCP connector works from a single address you paste into Claude’s add-connector screen. No terminal, no package install, no config file.

The order: create a free Tecrube account, connect Google Ads with Google OAuth in the /app member panel, copy the Claude address from the Connectors page and add it as a connector in Claude settings. The authorisation screen appears once; after that Claude sees the tools.

To confirm it works, type “Summarise my account” in a new chat. The first 75 credits are free and no payment details are requested for setup.

Analysis: “List ad groups where cost rose but conversions fell in the last 14 days.” Claude pulls the table and links the causes to search term and bid changes.

Execution: “Add these four search terms as exact-match negatives at account level.” Claude shows the preview; once you approve, Tecrube writes the change to the account.

Planning: “Draft a search campaign for a new service with a daily budget of 30 dollars.” The result is created as a paused campaign; going live is the final step and it stays yours.

For daily questions and report summaries the fast model is enough. Multi-step work, such as restructuring forty ad groups, produces fewer errors on the stronger model.

The connector is model-independent; the same address works in Claude on the web, on desktop and in Claude Code. Switching models never requires a new setup.

Write tools never let Claude touch the account directly; every write request becomes a preview on the Tecrube side and waits for approval. An unapproved request waits in the dashboard; nothing is written to the account until you approve it.

A single budget increase above 50% is refused, removing campaigns is not in the toolset, and every step is logged with a timestamp. Revoke access in your Google account and the connector stops immediately.

After connecting, tie Claude to a weekly routine: search term cleanup on Monday, budget check on Wednesday, creative performance on Friday. Three questions, three previews, three approvals.

Pro ($49) is enough for one account; if you manage several clients, the Agency plan ($99) lets you switch accounts inside a single chat.

Give a date range: “last 30 days” or “last week versus the week before”. Questions without a range can lead to the wrong comparison.

State the goal: saying “by cost per conversion” or “by revenue” decides which metric Claude puts first. The same table yields different answers under different goals.

Ask for analysis before change: the pattern “explain the cause first, then propose” makes previews easier to read. When Claude writes the reasoning, your approval rests on data, not a guess.

After applying these three rules in a few chats, save the questions you use most. A ready list for the weekly routine is the easiest way to get the same quality of analysis every Monday, and it helps teammates use the same method.

Can connectors be used on Claude’s free plan? Adding remote connectors depends on Anthropic’s plan scope and may change over time. If you cannot see the connector screen, you can reach the same tools through Claude Code or Tecrube’s /app panel.

Could Claude change the wrong account? The preview always shows the account name and ID. With several accounts connected, do not approve until you have confirmed the account in the preview; Tecrube also announces account switches in the chat.

Can I use Claude and ChatGPT at the same time? Yes. Both clients can connect to the same Tecrube account. Whichever client a change comes from, it lands in the same approval queue and the same log, so different tool preferences in the team cause no friction.

What should I do first after setup? Start with reads: account summary, the last 30 days of campaign performance and a search term analysis. Once comfortable, try the approval step with a small write, such as adding a single negative keyword.