Reporting
Campaign, keyword, and search term performance across all of the campaign types we manage, exported to files our team reads and turns into client reports.
We manage Google Ads accounts for our clients, and we built one internal tool to do it consistently. This page describes what that tool is, what it does, and who is allowed to use it. It is not a product, and there is nothing here to sign up for.
It is a command-line tool, built in-house on the official Google Ads API Python client library. It runs on GETCGO company workstations and is used only by GETCGO staff. It works on the client accounts linked under our Google Ads manager account (MCC), and on nothing else.
It is not a public product. There is no client login and there are no external users. It is not sold, it is not resold, and no API access is provided to any third party. Clients receive exported reports, prepared by our team.
The tool has no graphical interface, so this is what working with it looks like. Account and campaign numbers are masked here. The last two commands are the same command twice: the first prints the change it would make and stops, and only the one carrying --apply actually makes it.
Campaign, keyword, and search term performance across all of the campaign types we manage, exported to files our team reads and turns into client reports.
Monitoring the client accounts linked under our manager account, and managing their conversion tracking settings.
Daily budgets, pausing and enabling campaigns and keywords, and adding negative keywords.
Creating Search and Performance Max campaigns, ad groups, keywords, ads, and asset groups, from a structure agreed with the client beforehand.
Keyword ideas and search volume estimates, used while planning what to build.
Opening a new Google Ads account under our manager account when we take on a new client.
Conversion actions and goals, and a daily upload of lead-quality adjustments from our clients' lead sheets, so bidding learns from qualified leads.
The tool runs in dry-run preview mode by default. A command that would change something prints what it would do and then stops. Nothing reaches a client account until a member of our team has read that preview and run the same command again with --apply.
gads budget --campaign 111 --amount 200
gads budget --campaign 111 --amount 200 --apply
Operated by GETCGO staff on company workstations. The tool authenticates as us and reaches nothing outside this account.
The advertising accounts we manage. Clients receive exported reports from them, prepared by our team.
Does not exist. No client login, no third-party API access, nothing sold or resold.
Usage grows with campaign work: about 3,300 Google Ads API operations a day on average. A full campaign build for one client is around 5,000 operations, plus the validation run Google counts the same way. Every change is validated as a dry run first, and a guard refuses oversized requests.