1
-## Why am I getting Google Ads quota errors after a successful login?
1
+## Google Ads developer token now belongs on the auth config, not connection initiation
2
3
-Google Ads API requests use both an OAuth access token and a Google Ads developer token. A successful OAuth connection only confirms that the user granted access; it does not mean the developer-token quota is dedicated to your project.
3
+Google Ads was changed so the developer token lives on the auth config itself, not on each connection initiation request. Older auth configs created before this change do not have the developer token field, and new connections through those auth configs can fail because the token is no longer accepted at the connection level. Create a new Google Ads authConfig with the developer token included, then create a fresh connection through that authConfig.
4
5
-If you use Composio's managed Google Ads connector, requests may use Composio's shared Google Ads developer token. Errors like `RESOURCE_EXHAUSTED`, `rateScope: DEVELOPER`, or `Number of operations for basic access` mean Google is throttling that developer-token quota, even when your connected Google Ads account has low usage.
5
+
6
7
-For a short-term retry, wait for the retry window returned by Google. For production workloads, create a custom Google Ads auth config with your own OAuth client credentials and Google Ads developer token, so quota and access limits are isolated to your Google Ads setup. See [custom auth configs](/docs/auth-configuration/custom-auth-configs).
7
+## What can cause Google Ads 429s?
8
+
9
+A Google Ads 429 / `RESOURCE_EXHAUSTED` is an upstream Google Ads API limit, not a Composio billing-plan or tool-call quota. Google Ads enforces limits on the underlying developer token, account, request pattern, service, and resource usage.
10
+
11
+This can happen with Composio-managed credentials or with custom Google Ads credentials. Reduce request volume, add backoff, simplify expensive queries, and use an owned Google Ads OAuth app/developer token for production isolation where possible.
12
+
13
+## Google Ads MCC/sub-account targeting
14
+
15
+For Google Ads manager-account (MCC) setups, `GOOGLEADS_LIST_ACCESSIBLE_CUSTOMERS` can succeed while GAQL/reporting or campaign calls against a child account fail. Two common Google errors are:
16
+
17
+- 403 `USER_PERMISSION_DENIED` with guidance that, when accessing a client customer, the manager customer ID must be set in the `login-customer-id` header.
18
+- `REQUESTED_METRICS_FOR_MANAGER` when metric fields are queried directly from the MCC manager account instead of a child/customer account.
19
+
20
+Treat this as MCC targeting/account-context, not OAuth. Reconnecting alone does not fix it unless the user had connected the wrong account context.
21
+
22
+Correct call shape:
23
+
24
+- target child/customer account ID in the request path, for example `/customers/{child_customer_id}/googleAds:searchStream`
25
+- manager/MCC customer ID in the `login-customer-id` header
26
+
27
+## Google Ads OAuth callback token-exchange failures usually point to bad credentials
28
+
29
+The `OAuth callback failed during token exchange` error usually means the credentials used to complete the auth flow are incorrect, most often the client secret. Re-enter or update the client secret in the Google Ads auth config, make sure there are no leading/trailing spaces, and initiate a new connection.
30
+
31
+## What do custom Google OAuth apps need for white-label consent?
32
+
33
+For Google toolkits, creating a new authConfig with the user's OAuth app credentials is not enough for full white-label consent. They also need to route the callback through their own domain using their own redirect URI so Google displays the configured consent screen for that OAuth app.