Starfathom Ads Manager
An internal tool by STEFANCHO LABS · Advertiser · Internal use only · Last updated: 12 August 2026
Starfathom Ads Manager is the internal command-line tool of STEFANCHO LABS, with local reporting output. STEFANCHO LABS is the studio that publishes mobile apps under the Starfathom name. This site is the homepage for the application shown under that name on the Google sign-in and consent screen.
What follows is the detailed description and the mock-ups of the tool, set out in the order of Google’s own sample design document for developer token applications.
Business model
STEFANCHO LABS is a one-person studio in South Korea, registered as a sole proprietorship under business registration number 118-04-31442. We publish mobile apps for iOS and Android under the Starfathom name. They earn through in-app advertising and in-app purchases, and we buy installs for them ourselves. We advertise only apps we own and publish, and we do not manage ads for anyone else.
Running those campaigns by hand in the Google Ads web interface costs more clicking with every app we release, which is the whole reason for the tool.
Tool access and use
Only the owner of STEFANCHO LABS. STEFANCHO LABS is the sole advertiser and the sole user of the tool. The studio is a one-person business, so the tool has one operator and no external users. No client, customer, contractor, reseller, or other third party can sign in to it, connect an account to it, receive Google Ads data from it, or cause it to make an API request. It is not distributed, sold, licensed, or offered as a service, and there is nothing here to sign up for. We do not manage Google Ads accounts on behalf of any other person or company.
Tool design
API services called
- Create and update App install campaigns and their daily budgets, via CampaignService and CampaignBudgetService.
- Manage ad groups and the text, image, and video assets App ads use, via AdGroupService, AdGroupAdService and AssetService.
- Apply operator-confirmed changes to supported settings such as target CPA or ROAS, language, and location, via CampaignService, while Google Ads automates serving-level bidding and targeting.
- Pull performance figures for cost-per-install and retention analysis, via GoogleAdsService.search, and combine them locally with app analytics we export ourselves.
That is the entire scope. The tool does not create customer accounts, manage third-party users or billing, run keyword planning, resell API access, or expose our developer token through any other service. Expected volume is low, on the order of hundreds of operations a day, well inside the 15,000 operations a day that Basic Access allows.
Tool mock-ups
Why Basic Access is required
Setup is complete and verified. Our advertiser account is linked to our own manager account, advertiser verification was completed on 25 July 2026, OAuth credentials are issued, and our developer token is linked to Google Cloud project 124877619497 and confirmed by a live call to the Google Ads API. That Cloud project passed OAuth brand verification on 27 July 2026.
On 12 August 2026 Google automatically upgraded our developer token from Test Account Access to Explorer Access, and we verified it the same day with live calls: GoogleAdsService.search returns production data from our advertiser account, and a validate-only campaign mutation passes authorization. Explorer Access caps production use at 2,880 operations per day and excludes services we do not use, such as account creation, user management, keyword planning, and billing. We request Basic Access for the standard 15,000-operation daily limit and the full service surface, so the same tool keeps working as campaigns roll out across every app we publish.
To be exact about where the work stands: authentication, the developer-token link, and the account topology above are built and verified against the live API, and as of 12 August 2026 the token reaches our production account under Explorer Access. The campaign and reporting operations described above are specified and scoped, and we are bringing them up against our own account now. This page describes the tool we are building for our own account, not a product we sell.
Data handling
The tool signs in with a Google Account that we own and uses the Google Ads API to read and write campaign settings, budgets, ad assets, and aggregate performance metrics belonging to our own Google Ads account. This access is needed to create campaigns, review their results, and apply operator-approved changes without repeating the same work manually in the Google Ads web interface.
The tool does not request access to Gmail, Drive, Calendar, contacts, or any other Google service, and it does not access advertising accounts belonging to anyone outside the studio. It stores no personal information about third parties. Credentials stay in private local configuration, and reporting data is cached locally only for our own campaign analysis. None of it is sold, shared with third parties, or used to train machine-learning models. Anything received from Google APIs is handled under the Google API Services User Data Policy, including its Limited Use requirements. See the Starfathom privacy policy for the full statement.
Contact
Questions about this tool go to support@starfathom.com.