Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Explain why Google Ads quota errors happen after login (#3778)
## Summary - Add a Google Ads toolkit FAQ entry for quota errors after a successful OAuth login. - Clarify that `RESOURCE_EXHAUSTED` with developer-token rate scope is tied to the Google Ads developer token quota, not the user's connected Ads account. - Recommend retrying after Google's retry window or using a custom OAuth/client setup with a dedicated Google Ads developer token for production workloads. ## Tests - `bun run lint:links` - `bun run test`
Abhishek Patil committed
Jul 9, 2026 at 15:16 UTC
f4d09832fcc426bc852d3948a125e6d0a51690b8
1 file changed
+7
docs/content/toolkits/faq/googleads.md
new
+7
@@ -0,0 +1,7 @@
1
+## Why am I getting Google Ads quota errors after a successful login?
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.
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.
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).