Connect Google Ads

A Google Ads connection is a Google account, and the ad accounts it can reach. Marketing uses it to read a brand's ad spend and results, and to manage its campaigns. It is your org's or a brand's. See Connections for how connecting works in general.

Ways to connect

• Connect, through GreenMind's app, where it is open to your org.
• Use your own app: an OAuth client in your own Google Cloud project, which has its own access to the Google Ads API. Start at Google Cloud's Google Ads API page; Google's guide to the Cloud project for the Ads API explains the rest.

There is no key option.

Making your own app

1. Open the Use your own app dialog for Google Ads on the Connections page, and keep it open.
2. In the Google Cloud console, choose or create a project. Google may ask for a billing account to be linked to it before it lets you enable the Ads API.
3. Enable the API. In APIs & Services > Library, find Google Ads API and enable it.
4. Set up the consent screen. In Google Auth Platform, fill in Branding (app name, support email, your home page, privacy policy and terms addresses, authorized domain) and choose an Audience. An app for people outside your Google Workspace is External.
5. Add the scope. In Google Auth Platform > Data Access, choose Add or remove scopes, and under Manually add scopes enter the scope below. Then Update and Save.
6. Make the client. In Google Auth Platform > Clients, choose Create client, with type Web application. Under authorized redirect URIs, add the redirect URL from the dialog, copied exactly.
7. Copy the client ID and client secret into the dialog and press Connect. Sign in to Google with an account that has access to the ad accounts, and allow it.

Scopes

https://www.googleapis.com/auth/adwords

One scope covers both reading and managing.

Access to the Ads API

Google decides what a Cloud project may do with the Google Ads API, through an access level that belongs to the project. A new project may be limited at first, to test accounts for example; Google's documentation explains the levels and how to apply for more. Nothing about it is set in GreenMind.

After connecting

The brand's ad accounts are listed on Ads, where Read the accounts again asks each network for them. Google Ads names an ad account by its customer id: ten digits, without hyphens. An ad account reached through a manager account also carries the manager account's id, as the login customer id.

If it goes wrong

• Only some people can connect. While the consent screen is in Testing, only Google accounts listed as test users (Google Auth Platform > Audience) can sign in, and a connection typically has to be connected again after about a week. Publish the app, or add each account as a test user.
• Redirect URI mismatch. The redirect URI on the client differs from the dialog's.
• The API is disabled. Enable the Google Ads API in the project the client belongs to.
• That Google account reaches no ad account. Sign in with an account that has been given access to the ad account in Google Ads.
• Calls are refused for access. The project's access level does not allow it. See above.