Use your own Google Cloud project for Google Ads

What you'll have at the end: your own Google Cloud project with Google Ads API access, ready to connect to OpenAdManager.

Who needs this: If you use OpenAdManager's programmatic access (MCP or API) to Google Ads, you should obtain your own Google Cloud Platform account and Google Ads API access.

Signing in with Google and asking questions about your ad accounts works without any of this. This page is for the programmatic route: your own tools, scripts or AI apps calling Google Ads through OpenAdManager's MCP or API.

Why Google asks for it

Google ties Google Ads API access to a Google Cloud project and a developer token, and its rules apply to the project that holds them. Bringing your own keeps that access, and its quota, under your own account.

Set it up

1. Create a Google Cloud project. In the Google Cloud console, create a project, or pick one you already use for ads.
2. Turn on the Google Ads API. In that project, open APIs and services, search for "Google Ads API" and enable it.
3. Get Google Ads API access. In a Google Ads manager account, open the API Center and apply for a developer token. Google reviews the application. Read Google's own guide first: Google Ads API: get started.
4. Create an OAuth client in the same project (APIs and services, Credentials) and set up the OAuth consent screen for it.
5. Write to us. Email support@openadmanager.com with your project's name (never a secret or a token). We will help you connect it.

What we never ask for

Do not send a client secret, a refresh token or a password by email. We will tell you how to hand over what is needed without putting a secret in a message.

Changes and limits

Your own Google Ads API quota and Google's rules apply to your project. OpenAdManager's plan limits still apply to what your AI does through us. See pricing and how Google Ads data is used.