All Toolkits

Google Ads

Latest version

Google Ads, is an online advertising platform developed by Google, where advertisers bid to display brief advertisements, service offerings, product listings, and videos to web users.

Authentication DetailsComposio-managed OAuth available

Frequently Asked Questions

How do I set up custom Google OAuth credentials for Google Ads?

Use your own Google OAuth app when you want your app name on the consent screen, your own API quota, or full control over the requested scopes.

You need a Google Ads account you can access and its 10-digit Customer ID. Live-account API access is controlled by the Google Cloud project that owns the OAuth client, not by a developer token on the auth config.

Create the Google OAuth app

  1. In Google Cloud Console, select the project that will own the OAuth client, or create one.

    Google Cloud console project picker

  2. Open APIs & Services → Library, search for Google Ads API, and select Enable. If the page shows Manage, the API is already enabled.

    Google Ads API page in the API Library with the Enable button

  3. Enabling the Google Ads API grants Test access only. To use production Ads accounts, open the Google Ads API Overview page for your Cloud project and apply for Explorer access. Higher usage or extra features can require Basic or Standard access. See Google's access levels and Cloud project setup.

  4. Open Google Auth Platform → Branding. If Google shows Get started, enter the app name, user support email, and developer contact email, then save.

    Google Auth Platform Branding page with app name, support email, and developer contact fields

  5. Open Audience. Choose Internal to limit the app to users in your Google Workspace organization, or External for consumer accounts and users outside it. While an external app's publishing status is Testing, only accounts listed under Test users can connect, so add every account you'll test with.

    Google Auth Platform Audience page with Testing status, External user type, and Test users

  6. Open Data Access → Add or remove scopes and add the scopes listed under Scopes below. If a scope isn't in the list, paste its full URL under Manually add scopes and select Add to table. Select Update, then Save.

    Data Access scope picker with the Google Ads adwords scope selected

  7. Open Clients → Create client, choose Web application, and give it a name.

    Create OAuth client ID form with Web application selected and a client name

  8. Under Authorized redirect URIs, add https://backend.composio.dev/api/v1/auth-apps/add. It must exactly match the oauth_redirect_uri field on your Composio auth config.

    OAuth client form with the Composio redirect URI under Authorized redirect URIs

  9. Select Create. Copy the Client ID and Client secret. Google shows the full secret only once, so save it before you close the dialog.

    OAuth client created dialog with the Client ID and Client secret

Create the auth config in Composio

  1. In the Composio dashboard, open Auth Configs → Create and select Google Ads.

    Composio Auth Configs page with the Create button

    Create Auth Config dialog with Google Ads in the search results

  2. Choose OAuth 2.0 and Your Own Credentials, then paste your Client ID and Client secret. Leave Redirect URI unchanged, keep the scopes in line with what you added in Google, and select Create Auth Config.

    Google Ads auth config form with Client ID, Client secret, Redirect URI, an empty Developer Token field, and the adwords scope

  3. Open the auth config, select Connect Account, and enter the Customer ID of the Google Ads account or manager (MCC) account you want to use, for example 123-456-7890. This is not your Google Cloud project ID. Then sign in with a Google account that can access that Ads account.

    Composio Connect Account form asking for the Google Ads Customer ID

    Google consent screen asking to manage your Google Ads accounts and data

  4. Open Accounts on the auth config and confirm the connected account shows Active. The auth config's own Enabled label doesn't confirm a connection.

    Composio auth config panel with the Google Ads connected account shown as Active

For the general flow, see Custom auth configs.

Scopes

The default auth config requests https://www.googleapis.com/auth/adwords. It's the only Google Ads API scope and includes account-management access, so it isn't read-only. The user's Google Ads account role still limits what they can do. See Google's OAuth overview for Google Ads.

Short scope names on this page leave out the https://www.googleapis.com/auth/ prefix. When you paste a scope under Manually add scopes, use the full URL, for example https://www.googleapis.com/auth/userinfo.email. Scopes already written as a full URL, such as https://mail.google.com/, go in as shown.

Developer token

If the auth config form shows a Developer Token field, you can leave it empty. It's a legacy field kept for older auth configs, and Composio no longer sends it to Google. API access comes from the Google Cloud project that owns your OAuth client.

Publish and verify the app

While an external app is in Testing, Google shows an unverified-app notice and refresh tokens expire after seven days, so users have to reconnect. Before you invite production users, select Publish app on the Audience page. A public app that requests sensitive or restricted scopes also needs Google's OAuth verification, which you start from Verification Center. Publishing doesn't complete verification on its own. Internal apps and apps in Testing can be exempt. See Google's verification requirements.

Google hasn't verified this app notice for an app in Testing

If you change the requested scopes later, reconnect the account so the user grants the new access.

What can cause Google Ads 429s?

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.

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.

Google Ads MCC/sub-account targeting
Google Ads OAuth callback token-exchange failures usually point to bad credentials
What do custom Google OAuth apps need for white-label consent?