Skip to main content
This guide shows you how to register your own app with Google to obtain your OAuth credentials (client ID & secret). These are required to let your users grant your app access to their Google Ads accounts.
You will need to pass a security review to go live with your integration.Follow our guide to get approved as fast as possible.

​
Create your OAuth App

1

Create a Google Cloud account

If you don’t already have one, sign up for a Google Cloud account.
2

Create a new project

  1. Go to the Google Cloud Console.
  2. Click on the project dropdown at the top left of the page.
  3. Click New Project.
  4. Enter a Project Name for your project.
  5. Under Location, select the appropriate organization or folder where this project should belong.
    If you’re not part of an organization, it will default to No organization
  6. Click Create and wait for the project to be created.
  7. Select it from the project dropdown.
3

Enable the APIs you need

  1. Go to the API Library in the Google Cloud Console.
  2. Search for Google Ads API and click Enable.
4

Configure the OAuth consent screen

  1. Go to APIs & Services > OAuth consent screen in the Google Cloud Console.
  2. Click Get started.
  3. Fill in all the required fields in the App Information form.
  4. Click Next. Select the appropriate Audience:
    • External: For applications available to any Google user
    • Internal: For applications restricted to users within your Google Workspace organization
  5. Click Next. Fill in the Contact Information; these are the email addresses that Google will use to notify you about any changes to your project.
  6. Click Next, then check the I agree to the Google API Services: User Data Policy checkbox, and click Continue.
  7. Add the scopes your application needs. Under Data Access, click Add or Remove Scopes and select the scopes that correspond to the APIs you enabled.
Make sure to select scopes based on the APIs you enabled earlier when setting up the app. See Google’s OAuth 2.0 Scopes documentation for all available scopes.
  1. Under Audience, click Add users if you selected External user type (required for testing before verification).
In “Testing” mode with an external user type, refresh tokens expire in 7 days unless only basic scopes are used (userinfo.email, userinfo.profile, openid, or their OpenID Connect equivalents). You can remove this 7-day limit by switching from Testing to Production in step 8 below.
5

Create OAuth 2.0 credentials

  1. Go to APIs & Services > Credentials in the Google Cloud Console.
  2. Click Create Credentials and select OAuth client ID.
  3. Select Web application as the application type.
  4. Enter a name for your OAuth client.
  5. Under Authorized redirect URIs, add https://api.nango.dev/oauth/callback.
While setting up the OAuth credentials, the Authorized JavaScript origins should be your site URL (https://app.nango.dev if you’re testing from the Nango UI).
  1. Click Create.
  2. A dialog will appear with your client ID and client secret. Save these credentials securely as you’ll need them when configuring your integration in Nango.
Google allows up to 100 refresh tokens per account per OAuth client ID. New tokens overwrite the oldest without warning when the limit is reached.
6

Get your Google Ads developer token

The Google Ads API requires a developer token on every request, separate from your OAuth client ID and secret.
  1. Sign in to a Google Ads manager account (create one if you don’t already have one).
  2. Go to Admin > API Center.
  3. Copy your developer token.
New developer tokens start at “Test Account Access,” which only works against Google Ads test accounts. To use it with real (production) accounts, apply for Basic or Standard access from the same API Center page — this can take a few days to be approved. See Google’s access levels documentation for details.
If you access your users’ Google Ads accounts through a manager (MCC) account, you’ll also need that manager account’s customer ID (without hyphens) — this is login_customer_id. If every one of your end users brings their own manager account instead, you can skip this step and let them enter it during connect.
7

Apply your developer token to every connection

The developer token isn’t something Nango asks each end user for — it belongs to your app, not to any individual Google Ads account. Set it once as a connection config default instead:
If you also always access accounts through the same manager account, include login_customer_id in the same object so it’s set automatically instead of shown in the Connect UI:
If your end users each have their own manager account instead, leave login_customer_id out of the defaults — it’ll appear as an optional field in the Connect UI for them to fill in themselves.
Pass developer_token under integrations_config_defaults.<INTEGRATION-ID>.connection_config when creating a connect session via the create connect session API — it’s marked automated: true in the provider config, so it never appears in the Connect UI and must be supplied by your backend at session-creation time.login_customer_id is a regular, optional connection_config field, not automated. Include it in the same defaults object if your integration always uses one fixed manager account; omit it if it varies per end user, and it’ll be collected in the Connect UI instead.
8

Start building your integration

Follow the Quickstart to build your integration.
9

Verify your app

Most Google Ads scopes are marked “sensitive” by Google.You can develop your integration in test mode, but you need to pass a security review to go live.Follow our guide to prepare and pass as quickly as possible.
For applications using sensitive or restricted scopes, Google requires verification and a security assessment. This process can take several weeks to complete.
10

Publish your app (switch from Testing to Production)

To move your OAuth app from testing to production:
  1. Go to APIs & Services > OAuth consent screen > Audience.
  2. Click Publish App to switch your app from testing to production.

​
Important considerations

Refresh token expiration For information on why Google refresh tokens expire, see Why is my Google refresh token expiring?. For Google OAuth basics, see Google’s OAuth 2.0 documentation. For more details on Google Ads scopes and API implementation, see Google Ads API documentation.