Google Ads API CLI: preparing the infrastructure.
Designed and prepared a local CLI service on Node.js + TypeScript for obtaining advertising statistics from the Google Ads API and further generating AI-ready reports.
The project has reached full technical readiness: a CLI skeleton has been created, Google Cloud, OAuth, MCC, Developer Token, refresh token, and linkage with the advertising account have been set up. The API check has successfully reached Google's final system limitation: awaiting approval for Basic Access to work with real advertising accounts.
1. A separate Google Ads API CLI project has been created.
A separate working folder has been created:
F:\GOOGLE_ADS_API_Stats
The project was not mixed with the Meta Ads CLI to avoid breaking the already functioning system for Meta. Inside, the main project files have been prepared: package.json, tsconfig.json, .env.example, .gitignore, README.md, PROJECT_CONTEXT.md, project_config.json, as well as the structure src/ with CLI, config, Google Ads client, services, and utilities.
2. TypeScript CLI skeleton has been assembled.
Basic commands have been implemented:
doctor
doctor --ping
customers / accounts
campaigns
report
The report command already creates a skeleton Markdown report in the reports/ folder, without tokens and secrets.
3. The Google Ads API library has been connected.
A dependency has been added to the project:
google-ads-api ^23.0.0
A read-only client has been prepared for future GAQL queries, normalization of customer_id, login_customer_id, error handling for the Google Ads API, and protection against write/mutate requests.
4. Google Ads Manager Account / MCC has been set up.
A manager account has been created:
Me4Hik Google Ads Manager
It is needed for the agency model: the client’s advertising account remains with the business owner, while management and API access go through the MCC.
5. Developer Token has been obtained.
A Developer Token has been created in the Google Ads API Center. At this stage, it has the status of Test Account Access, so an application for Basic Access has been submitted for real accounts.
6. Application for Google Ads API Basic Access has been submitted.
A design document has been prepared and attached for the Google Ads API Compliance Team. The document describes that the tool operates as a local read-only CLI for reporting and analytics, does not create or modify campaigns, ads, bids, budgets, or keywords.
7. Google Cloud Project has been set up.
A separate Google Cloud Project has been created:
Google Ads API CLI
The Google Ads API has been enabled in it, and the Google Auth Platform has been configured.
8. OAuth has been configured.
An OAuth Client has been created, the OAuth Playground has been set up, a refresh token has been obtained, and all key .env fields have been filled:
GOOGLE_ADS_DEVELOPER_TOKEN
GOOGLE_ADS_CLIENT_ID
GOOGLE_ADS_CLIENT_SECRET
GOOGLE_ADS_REFRESH_TOKEN
GOOGLE_ADS_CUSTOMER_ID
GOOGLE_ADS_LOGIN_CUSTOMER_ID
GOOGLE_ADS_API_VERSION
9. The entire access chain has been verified.
The command doctor --ping reached the Google Ads API. OAuth errors, redirect URI, client secret, refresh token, MCC linkage, and customer ID have been sequentially resolved.
The final check has only hit the expected system blocker:
The developer token is only approved for use with test accounts.
This means the infrastructure is ready, but Google must approve Basic Access.
Practical value
This stage is important because the Google Ads API is not just about “getting a token.” It is necessary to link together:
Google Ads MCC
Developer Token
Google Cloud Project
OAuth Client
Refresh Token
Customer ID
Login Customer ID
local CLI
secure storage of secrets
After Basic Access approval, the service can be further developed: obtaining campaigns, expenses, clicks, conversions, search queries, devices, geography, and generating full AI-ready reports for analysis in ChatGPT.
#GoogleAdsAPI #GoogleAds #PPC #PerformanceMarketing #MarketingAutomation #NodeJS #TypeScript #CLI #OAuth2 #GoogleCloud #GAQL #AdsAnalytics #AIAnalytics #ChatGPT #AdvertisingAnalytics #ReportAutomation #ContextualAdvertising
The project has reached full technical readiness: a CLI skeleton has been created, Google Cloud, OAuth, MCC, Developer Token, refresh token, and linkage with the advertising account have been set up. The API check has successfully reached Google's final system limitation: awaiting approval for Basic Access to work with real advertising accounts.
1. A separate Google Ads API CLI project has been created.
A separate working folder has been created:
F:\GOOGLE_ADS_API_Stats
The project was not mixed with the Meta Ads CLI to avoid breaking the already functioning system for Meta. Inside, the main project files have been prepared: package.json, tsconfig.json, .env.example, .gitignore, README.md, PROJECT_CONTEXT.md, project_config.json, as well as the structure src/ with CLI, config, Google Ads client, services, and utilities.
2. TypeScript CLI skeleton has been assembled.
Basic commands have been implemented:
doctor
doctor --ping
customers / accounts
campaigns
report
The report command already creates a skeleton Markdown report in the reports/ folder, without tokens and secrets.
3. The Google Ads API library has been connected.
A dependency has been added to the project:
google-ads-api ^23.0.0
A read-only client has been prepared for future GAQL queries, normalization of customer_id, login_customer_id, error handling for the Google Ads API, and protection against write/mutate requests.
4. Google Ads Manager Account / MCC has been set up.
A manager account has been created:
Me4Hik Google Ads Manager
It is needed for the agency model: the client’s advertising account remains with the business owner, while management and API access go through the MCC.
5. Developer Token has been obtained.
A Developer Token has been created in the Google Ads API Center. At this stage, it has the status of Test Account Access, so an application for Basic Access has been submitted for real accounts.
6. Application for Google Ads API Basic Access has been submitted.
A design document has been prepared and attached for the Google Ads API Compliance Team. The document describes that the tool operates as a local read-only CLI for reporting and analytics, does not create or modify campaigns, ads, bids, budgets, or keywords.
7. Google Cloud Project has been set up.
A separate Google Cloud Project has been created:
Google Ads API CLI
The Google Ads API has been enabled in it, and the Google Auth Platform has been configured.
8. OAuth has been configured.
An OAuth Client has been created, the OAuth Playground has been set up, a refresh token has been obtained, and all key .env fields have been filled:
GOOGLE_ADS_DEVELOPER_TOKEN
GOOGLE_ADS_CLIENT_ID
GOOGLE_ADS_CLIENT_SECRET
GOOGLE_ADS_REFRESH_TOKEN
GOOGLE_ADS_CUSTOMER_ID
GOOGLE_ADS_LOGIN_CUSTOMER_ID
GOOGLE_ADS_API_VERSION
9. The entire access chain has been verified.
The command doctor --ping reached the Google Ads API. OAuth errors, redirect URI, client secret, refresh token, MCC linkage, and customer ID have been sequentially resolved.
The final check has only hit the expected system blocker:
The developer token is only approved for use with test accounts.
This means the infrastructure is ready, but Google must approve Basic Access.
Practical value
This stage is important because the Google Ads API is not just about “getting a token.” It is necessary to link together:
Google Ads MCC
Developer Token
Google Cloud Project
OAuth Client
Refresh Token
Customer ID
Login Customer ID
local CLI
secure storage of secrets
After Basic Access approval, the service can be further developed: obtaining campaigns, expenses, clicks, conversions, search queries, devices, geography, and generating full AI-ready reports for analysis in ChatGPT.
#GoogleAdsAPI #GoogleAds #PPC #PerformanceMarketing #MarketingAutomation #NodeJS #TypeScript #CLI #OAuth2 #GoogleCloud #GAQL #AdsAnalytics #AIAnalytics #ChatGPT #AdvertisingAnalytics #ReportAutomation #ContextualAdvertising
 |
Arseny Antonenko
 Kyiv 11 0
|
Available for hire
11 Safes completed
1 arbitration
On the service 4 years
Offer work