Skip to main content
Integrations · Google Ads
A Guild agent reads Google Ads performance data and makes campaign, ad group, and budget changes on your behalf. Guild injects the API key server-side so agent code never sees the credential. Credential policies let you restrict which operations each agent can perform before any request reaches Google Ads.

Book a demo

See how teams govern agents that use Google Ads.

Talk to sales

Get access to Guild, then connect Google Ads to your first agent.

What the Google Ads integration exposes

The integration provides tools for account discovery, GAQL reporting, and mutations across campaigns, ad groups, ads, and budgets. Query tools accept any Google Ads Query Language statement and return performance and account data. Mutation tools update statuses, adjust bids in micros, and change daily budget amounts. Tools follow the google_ads_ naming prefix.

How it works

1

Open credentials in Guild

Go to Access & setup > Credentials in Guild. Click Connect, select google-ads, and paste your key into the API Key field.
2

Import and spread the tools

Import GoogleAdsTools from the integration package and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs.
3

Scope the credential

By default a credential serves every workspace the account owns. You can scope it to one workspace, one member, or one agent from the credentials page or the installed agent’s detail page.

Why Google Ads access needs governing

Google Ads mutations are immediate and affect live spend. Guild’s credential proxy enforces credential policies before any request reaches Google Ads, so you can write ALLOW and DENY rules that restrict agents to specific operations, such as read-only GAQL queries, without touching the credential itself. Rules can be scoped to individual agents or workspaces, so a reporting agent and a budget-management agent can share one credential with different permissions. Guild stores the API key server-side and injects it at request time; agents never see it. Every request is auditable through Guild’s standard run history. Restricting a workspace to its own credentials prevents agents in that workspace from using the organization’s shared Google Ads credential.

About the Google Ads integration

Agents can query Google Ads data using GAQL to retrieve performance and account information. They can adjust campaign and ad group statuses, update budgets and bids, and pause or enable individual ads. Account discovery lets agents list all accessible customer accounts. The integration is guildai~google-ads.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect Google Ads

In Guild, go to Access & setup > Credentials, click Connect, select google-ads, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the google_ads_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~google-ads:

Frequently asked questions

Yes. Write a credential policy with DENY rules on the mutate operations, or an ALLOW rule scoped to google_ads_search_google_ads and google_ads_search_google_ads_stream only. The credential proxy blocks any other operation before it reaches Google Ads.
No. The catalog entry for guildai~google-ads lists no webhook events, so the integration does not receive push notifications from Google Ads.
Open the installed agent’s page in the workspace, choose Dedicated to this agent, and paste the API key. That credential serves only that agent and does not affect other agents or workspaces.
Budget amounts use amountMicros in account currency micros, where one currency unit equals 1,000,000 micros. Bid updates use cpcBidMicros on the same scale.

Put a governed agent on Google Ads this week

Book a demo

See how teams govern agents that use Google Ads.

Talk to sales

Get access to Guild, then connect Google Ads to your first agent.
Also runs on Guild: Affinity · Attio · Brex · Gong Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 20, 2026