Skip to main content
Google Ads is a Dev Testing and Conditional integration. daoco hosts Google’s official MCP package for discovery and reporting, with DAOCO-owned typed tools for controlled campaign status and daily-budget changes. 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. A Google authorization window opens immediately; 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. In an organization explicitly enabled for V1 writes, request a pause, enable, or daily-budget change. daoco first reads the resource, validates the exact mutation without executing it, and requires Confirm and apply before the approval-locked apply tool runs.
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. Production writes remain disabled until Google approves Basic Access with Ad creation / management and Reporting permissible uses.
V1 does not create or remove campaigns, manage billing or conversions, apply recommendations, or perform bulk/cross-account writes. Search campaign creation in a paused state is planned for V1.1.