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.
Step 1 — OAuth: Click "Connect with OAuth" and authorize with your Google account. Make sure the Google Ads API is enabled in your Google Cloud Console project.
Step 2 — Developer Token (required): The Google Ads API requires a developer token on every request, separate from OAuth. Go to Google Ads → Tools & Settings → API Center and apply for a developer token. Basic access is instant. Once you have it, your HLMT admin needs to add it as GOOGLE_ADS_DEVELOPER_TOKEN in Railway environment variables.
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 →