google-ads-connect

MCP onboarding for Google Ads connected mode automates server health verification, account discovery, and customer ID selection before writing the configuration to workspace memory. Run this initialization process before executing any connected-mode workflows.

Account discovery in connected mode fingerprints accessible Google Ads accounts via the MCP server, verifies data flow visibility, and helps operators select the correct customer ID to initialize downstream advertising workflows.

Run an MCP health check to verify server responsiveness, confirm account visibility, and validate data flow before conducting Google Ads audits or drafting campaigns. This ensures stable connected-mode connectivity.

Yes, connected mode requires writing the selected customer ID to workspace memory after MCP verification and account discovery. This safeguards downstream skills by ensuring they reference the correct account.

Switch accounts in connected mode whenever you need to change the active customer context. Re-run the onboarding process to discover accessible accounts, verify MCP availability, and write the new selection to workspace memory.

Connected mode onboarding limitations include strict dependency on MCP server availability and responsiveness. Without successful health checks and account visibility verification, downstream Google Ads analysis workflows cannot initialize.