Skip to main content
Self-hosted AdLoop uses your own Google Cloud project: no shared user caps, no dependency on someone else’s verification review, and the consent screen shows your project to your account. adloop init walks you through this; here’s the same path for reference.
1

Create a project

console.cloud.google.com → New project. Free; no billing account needed for these APIs.
2

Enable the APIs

Under APIs & Services → Library, enable: Google Ads API, Google Analytics Data API, and Google Analytics Admin API. Optionally, for the corresponding toolsets: Tag Manager API, Search Console API, Merchant API, PageSpeed Insights API.
3

Create OAuth credentials

APIs & Services → Credentials → Create credentials → OAuth client ID, application type Desktop app. Download the JSON; the wizard copies it to ~/.adloop/credentials.json.
4

Configure the consent screen

Add yourself as a test user, or publish the app to In production (recommended: tokens for apps left in “Testing” expire every 7 days, and Basic API access below requires it).
5

Apply for Google Ads API access

Since 9 September 2026, Google Ads API access belongs to the Cloud project that owns your OAuth client. Developer tokens are sunset and no Manager Account is needed. Open the project’s Google Ads API Overview page and click Upgrade access level:A project on a Cloud free trial or with billing disabled is refused Explorer and Basic.
CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION (or DEVELOPER_TOKEN_NOT_APPROVED on older API versions) means the project is still at Test level. Apply for Explorer access; nothing in AdLoop’s configuration needs to change.
If your OAuth token keeps expiring weekly, your consent screen is still in “Testing”. Publish it to “In production” in the Google Cloud Console.

​
Adding scopes later

When AdLoop adds new Google services, existing tokens don’t cover the new scopes. AdLoop detects this and triggers a fresh consent automatically; approve all requested permissions in one go. Details in Troubleshooting.