Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.meshpilot.app/llms.txt

Use this file to discover all available pages before exploring further.

Google Ads connects via Google OAuth. Once connected, the Ads agent gets visibility into your Search, Performance Max, and Display campaigns on the same hourly cadence as Meta.

​
What it unlocks

  • Google campaigns in the Ads surface — alongside Meta in the unified spend-by-platform module.
  • Google-aware Ads-agent proposals — pause, scale, bid-strategy adjustments tuned to Google’s campaign types.
  • GAQL access in the cockpit — under the hood Mesh Pilot uses Google’s Ads Query Language to read campaign state efficiently.

​
Scopes requested

Standard Google OAuth 2.0 with the Google Ads API scope. Mesh Pilot also requires a Google Ads developer token (already configured at the workspace level — you do not provide this).

​
Where data flows

  • Google → cockpit: ad-account state via GAQL queries on an hourly poll. Cached for fast rendering.
  • Cockpit → Google: only on your approval, via the Google Ads API.

​
Token lifetime

Google access tokens are short-lived (1 hour). Refresh tokens don’t expire. Mesh Pilot refreshes access tokens automatically before they hit zero.

Connect Google Ads

Open Settings → Integrations.