AdvertisingOAuth 2.0 (Google) + developer tokenPricing verified 2026-10-06
Google Ads API
Import Google Ads accounts, sync spend and conversions, launch campaigns, run automated rules and upload offline conversions from the CRM.
AProvider definition
- Provider
- Google Ads API
- What it does
- Google Ads (Search, YouTube, Display, Performance Max) for Performance Marketing. Uses the OAuth client from “Google (YouTube, Business Profile)” plus a Google Ads developer token.
- Why we need it
- Import Google Ads accounts, sync spend and conversions, launch campaigns, run automated rules and upload offline conversions from the CRM.
- Used in
- Performance ads · CRM conversion sync
BAccount requirements
- Account type
- Google Ads manager (MCC) account + developer token
- Prerequisites
- Google OAuth client with the Google Ads API enabled
- Verification
- Developer token access levels are reviewed by Google.
CConnection method
- Authentication
- OAuth 2.0 (Google) + developer token
- Credentials
- Uses the Google OAuth client (Google Cloud Console) credentials — no separate key.
- Where to enter it
- Your workspace: App → Integrations → Providers & API keysWorkspace owner or admin. Keys added here are used only by your workspace (AI keys here don't use plan credits).
- Ad accounts: App → Performance ads → Ad accountsConnect each ad account with OAuth, or paste an access token.
Setup steps
- 1Create or use a Google Ads manager account; open Tools → API Center and apply for a developer token.
- 2Enable the Google Ads API in the Cloud project; add the ads redirect URI below to the OAuth client.
- 3Enter the developer token (and manager customer ID if you access clients through an MCC).
- 4Performance ads → Ad accounts → Connect Google Ads.
DPermissions & API scopes
| Scope / permission | Why it's needed | Requested by |
|---|---|---|
| https://www.googleapis.com/auth/adwords | Read and manage campaigns, budgets and conversions. | Google Ads connection |
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — no fee for the API; ad spend is billed by Google Ads.
- Card or billing account required?
- Not for the API.
- Paid plan / costs
- None for API access.
- Quota and usage limits
- Test access: test accounts only. Explorer access: about 2,880 operations per day on production accounts. Basic: 15,000 operations per day. Standard: no daily operation cap for most services.
- Production restrictions
- Review for Basic/Standard access had a backlog in 2026.
Checked against official/current sources on 2026-10-06. Provider pricing changes often — re-check before publishing.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/google_ads/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
| Field | Required | Example / default | Notes |
|---|---|---|---|
| Developer token | Yes | •••••••• | Google Ads → Tools → API Center. Test-level tokens only work with test accounts. |
| Manager (MCC) customer ID | Optional | 123-456-7890 | Optional. Set when you access client accounts through a manager account. |
| API version | Optional | v21 |
Paste these into the provider's console
- Authorized redirect URI (add to the Google OAuth client)
https://api.socialmati.com/api/oauth/ads/google/callback
Connecting an ad account (Google Ads)
Covers Search, YouTube, Display, Performance Max, Shopping. Connect with OAuth from Performance ads → Ad accounts, or paste a token:
- • OAuth refresh token (adwords scope) (required)
- • Customer ID (required) — 123-456-7890
- • Manager customer ID (optional)
HTesting
- 1Connect an ad account; Performance ads → Overview shows the last 30 days of spend.
ITroubleshooting
| Problem | What to do |
|---|---|
| DEVELOPER_TOKEN_NOT_APPROVED | A test-level token only works with test accounts — apply for higher access. |
| USER_PERMISSION_DENIED | Set the manager customer ID when accessing client accounts through an MCC. |
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Remove the app in Google account → Third-party apps; reset the developer token in API Center.
- Disconnect in the application
- App → Integrations → Providers & API keys or App → Performance ads → Ad accounts → open the card → Remove / Disconnect. Connected accounts can be disconnected per brand.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- Campaigns, ad groups, metrics and conversion actions of connected accounts.

