Skip to main content
Google Ads is a Dev Testing and Conditional integration. daoco hosts Google’s official MCP package for discovery and reporting. DAOCO-owned tools can atomically create a complete paused responsive Display campaign, create paused Display foundations, handle campaign status and daily-budget changes, upload images, and create paused responsive ads. Workspace users do not enter client IDs, secrets, endpoints, developer tokens, or scopes.

​
Connect Google Ads

1

Enable Dev Testing

A workspace owner or admin must enable Dev Testing integrations in Settings -> Preview features.
2

Open the Google Ads card

In daoco, open Connections -> Integrations -> Dev Testing and choose Google Ads.
3

Choose Connect

Choose Connect. The first connection from a browser asks you to confirm the daoco callback before Google opens. FastMCP remembers that approval for later connections from the same browser and callback. There is no workspace configuration form.
4

Approve Google Ads access

Sign in with a Google user who can access the ad account and approve https://www.googleapis.com/auth/adwords. Google does not define a separate write scope.
5

Verify from chat

Ask /integration for an account or campaign summary. You can then request a paused Display campaign and ad group, a campaign pause, enable, daily-budget change, image upload, or a new responsive ad. daoco validates the exact mutation without executing it and uses the normal connected-app approval panel before applying it.
The Connect button remains unavailable until daoco’s Google Ads developer token and OAuth app are configured for Dev Testing and the service is online. Google Ads writes also require shared service authorization configured by daoco. This service boundary does not replace the approval shown in chat.
New Display campaign foundations use a private daily budget, Manual CPC bidding, and paused campaign and ad-group statuses. The setup does not add targeting or enable serving. New ads are also created paused. Responsive search ads require an existing Search ad group. Responsive display ads require a Display ad group plus a landscape image of at least 600 x 314 and a square image of at least 300 x 300. daoco checks both images again when approval is redeemed so changed URLs cannot silently change the approved creative. When no Display campaign exists, daoco can validate the private budget, paused campaign, paused ad group, both images, and paused responsive Display ad as one atomic request. It collects the complete budget, bid, EU political-ad declaration, copy, URL, and creative first, then presents one approval. Google creates all resources or none of them. The approval covers that exact validated proposal, not the short-lived Google preview token. If the token expires while the approval waits for review, daoco validates the same proposal again and applies it under the existing approval. Any change to the account, budget, bid, copy, images, targeting, or status needs a new approval. If the connected Google Ads identity opens a manager account, daoco reads its account hierarchy before any write. The manager customer ID is used only as the login context. Campaigns and their budgets are created in an enabled, non-manager client account. daoco selects the client automatically when there is exactly one eligible account and asks you to choose when several are available. This integration does not remove campaigns, create Search campaigns, configure campaign targeting, manage billing or conversions, apply recommendations, or perform unrestricted bulk mutations.