Google Ads
Org-level connection
Google Ads is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
How to connect
Prerequisites: Make sure the Google Ads API is enabled in your Google Cloud Console project and your account has the necessary access.
Click "Connect with OAuth" below and sign in with the Google account that manages your Google Ads account. After connecting, you'll be asked to enter your Google Ads Customer ID — find it in the top-right corner of your Google Ads dashboard (the 10-digit number, remove hyphens).
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for Google Ads. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
https://www.googleapis.com/auth/adwords | Full Google Ads access (campaigns, keywords, reports) | Read / Write |
Troubleshooting
"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/google to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g., Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
Still stuck? We're happy to help.
Contact support →