Hungry Minds LLC operates two direct-to-consumer web products and advertises both of them on Google Ads. We use the Google Ads API solely to manage and audit our own advertising accounts. We are not an agency, reseller, or third-party tool provider.
Advertised products
Resume Extraordinaire — resx.pro. AI-tailored resumes and cover letters.
Korean Vocabulary App — koreanvocabulary.app. SRS-based vocabulary app for Korean learners.
Both products run campaigns under a single Google Ads manager account (MCC) operated by Hungry Minds LLC. No third-party accounts are managed under this MCC.
How we use the Google Ads API
We use the API to run an internal tool that our two-person team uses to audit and, occasionally, update our own campaigns. The tool is read-mostly: the majority of calls are reporting queries.
Reporting. Pull campaign, ad-group, ad, keyword, and performance data for our own customer IDs so we can produce internal performance reports and diffs against expected configuration.
Configuration auditing. Compare the live account state against a desired-state YAML file checked into our private repository and surface drift.
Conversion upload. Upload first-party conversion events (such as free_trial_started) from our products, via the Enhanced Conversions / Click Conversions endpoints, for measurement and bidding.
Bulk edits with human approval. Propose keyword, ad copy, negative-keyword, and bid-target edits as a diff; mutations are executed only after a human reviews and approves the diff. The tool never auto-applies writes.
Device and placement exclusions. Keep mobile/tablet exclusions and negative keyword lists consistent across campaigns.
Scope
Own-account only. The tool is scoped to our own manager account and its child accounts. We do not and will not manage third-party advertising accounts.
Not a product. The tool is an internal utility. It is not resold, published, distributed, embedded in any consumer product, or exposed to end users of our SaaS products.
No autonomous mutation. Every write is gated on explicit human approval.
No access to customer data outside our own accounts.
Data handling & security
Each operator uses their own OAuth refresh token, scoped to their own Google account with access to our MCC.
The developer token, OAuth client ID, and OAuth client secret are stored in 1Password and loaded into .env.local for local use; encrypted environment variables are used for scheduled reporting.
Pulled data is stored only on operator laptops and in the internal reporting database owned by Hungry Minds LLC. It is not shared with third parties.
Every API call is logged (operator, endpoint, payload for mutations) for post-hoc audit.