Google Ads API — Use Case Description

Last updated: May 25, 2026

This is NOT a keyword-research-only tool. Kit Marketing does not build, offer, or sell any product whose primary purpose is keyword research. We do call KeywordPlanService, but only as a supporting step inside campaign creation and management — to size and group keywords for the campaigns we build and operate in our clients’ accounts. Keyword research is not a product we build, offer or sell, and it is not the primary purpose of our tooling.

Company information

About Kit Marketing

Kit Marketing is a Ukrainian performance marketing agency. We provide a managed-service paid acquisition function to e-commerce clients on Google Ads (Search, Shopping, Performance Max), Meta Ads, and TikTok Ads.

We manage Google Ads campaigns under our Manager Account (MCC 576-345-4890) for e-commerce clients who have signed a written advertising service contract with Kit Marketing. Every account inside our MCC belongs to a client who has signed a written advertising service contract with Kit Marketing and explicitly linked their account to our MCC.

Why we need Google Ads API access

We request Basic Access to the Google Ads API for internal agency operations only. We do not build, sell, license, or offer any third-party software, SaaS product, browser extension, white-label platform, reseller program, or other tool based on the Google Ads API.

The API is used exclusively by our own in-house team of 4 media buyers and analysts to operate the accounts inside our MCC. The Google Ads UI and Ads Editor cover manual bulk edits, but do not cover our reporting, conversion-tracking and audit-logging workflows while maintaining per-account quality and compliance with our client SLAs. Explorer Access is an evaluation tier; we need Basic Access for production use of campaign creation, management and reporting on this MCC.

Primary use cases (in order of importance)

1. Bulk campaign and budget operations

Day-to-day operation of the MCC requires programmatic actions:
— Create new campaigns from approved internal templates when onboarding a new client or launching a new product line
— Update bids and budgets in bulk in response to performance changes or client requests
— Pause / enable campaigns, ad groups, ads
— Manage campaign-level settings (locations, languages, ad rotation, bidding strategies)

API services used: CampaignService, CampaignBudgetService, AdGroupService, AdGroupAdService, AdGroupCriterionService, CampaignCriterionService, BiddingStrategyService.

Keyword and negative-keyword management is part of this workflow: we add, pause and remove keywords and negative keywords in the campaigns we build and operate for our clients. We use KeywordPlanIdeaService and KeywordPlanService as a supporting step to size and group those keywords before a campaign is built. This is a step inside campaign creation and management — it is not a product we build, offer or sell.

2. Bid and budget optimization

• Apply bid adjustments based on device, location, audience segment, and time of day
• Switch between bidding strategies (Manual CPC ↔ Target ROAS ↔ Maximize Conversions) based on account maturity and conversion volume
• Reallocate budgets across campaigns within a single client account based on observed ROAS

API services used: BiddingStrategyService, CampaignBudgetService, CampaignBidModifierService.

3. Performance reporting

• Pull campaign, ad group, and ad-level performance metrics (impressions, clicks, conversions, cost, CTR, CPC, CPA, conversion value, ROAS)
• Combine with data from Google Analytics 4 Data API and our internal CRM (PostgreSQL) to produce client-facing reports and internal dashboards
• Build internal dashboards (Looker Studio) for media buyers to monitor account health

API service used: GoogleAdsService (search / searchStream against campaign, ad_group, ad, conversion_action, asset resources).

4. Conversion tracking management

• Create and configure conversion actions for new clients
• Verify conversion tag firing and troubleshoot tracking issues
• Import offline conversions from client CRMs (with documented client consent)

API services used: ConversionActionService, ConversionUploadService.

5. Internal AI-assisted reading of campaign data

Role of Claude:
Anthropic’s Claude (accessed via Claude Code / Anthropic API) is used read-only, as an internal text-summarisation tool for our 4 media buyers. Claude receives aggregated, account-scoped performance data that has already been pulled from the Google Ads API by our team and helps the team:
— Summarise weekly performance trends in natural language
— Draft variants of ad copy that a human media buyer reviews and edits before any API write call
— Generate first-draft analyst comments for client reports

Hard architectural boundaries (not just policy promises):
— Claude has no write access to the Google Ads API. There is no integration path where a Claude response can result in a direct API write call.
— Every API write (campaign creation, bid change, budget change, ad creation, conversion action change) is initiated by a human media buyer through our internal tooling. The internal tool requires the media buyer’s authentication before issuing the write request.
— Claude does not receive end-user PII, demographic detail beyond what the Ads API itself exposes at aggregate level, or any data identifying individual end users of our clients’ websites.
— Claude is treated as a sub-processor under our standard Data Processing Agreement (see «Sub-processors» below).

What we do NOT do with Claude:
— We do not train any model — ours or Anthropic’s — on Google Ads API data.
— We do not pass Google Ads API data to Claude for the purpose of building lookalike audiences, retargeting, or any other ad-serving use case.
— We do not provide Claude outputs to external clients as a standalone product or sell access to Claude.

What this tool is NOT

To remove ambiguity:

• ❌ NOT a keyword-research-only tool. KeywordPlanService is called only as a supporting step within campaign creation, never as a standalone product.
• ❌ NOT a third-party SaaS. No public web interface; no signups; not sold; not redistributed.
• ❌ NOT a reseller / white-label platform. Each client is a direct contract client of Kit Marketing.
• ❌ NOT an autonomous AI bidding tool. Every API write is triggered by an authenticated human action.
• ❌ NOT a data broker. Google Ads API data never leaves the systems described in «Sub-processors» below.

Who has access to API data

• In-house team: 4 employees and long-term contractors of Kit Marketing, all under signed NDAs and a written Data Processing Agreement (DPA) that mirrors the requirements of the Google API Services User Data Policy. Onboarding includes mandatory training on the Limited Use requirements.
• Scope of access: limited to accounts inside our MCC 576-345-4890, which our clients have explicitly linked to us via the Google Ads Customer Manager link.
• Access logging: all API write actions are logged in our internal audit log (timestamp, acting user, MCC, customer_id, resource, before/after state). Logs are retained for 24 months for audit purposes.

Data we will request via the API

• Campaign / ad group / ad / asset structure (read & write)
• Performance metrics (impressions, clicks, conversions, cost, CTR, CPC, CPA, ROAS, conversion value)
• Conversion actions (read & write)
• Audience and demographic reports at the aggregated level Google Ads exposes (no individual-user data)
• Account-level settings (budgets, bidding strategies, location/language targeting)

We will not request or process any individually identifiable end-user data beyond what Google Ads itself exposes inside advertiser accounts at the aggregate level.

Data retention

Sub-processors

The following sub-processors process Google Ads API data on our behalf, each covered by a written DPA / equivalent contractual terms:

Limited Use & Google API Services User Data Policy compliance

Kit Marketing’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements:

• We do not transfer Google Ads API data to third parties, except as necessary to provide the contracted service to the client whose account the data came from, or to the listed sub-processors above under written DPA terms.
• We do not use Google Ads API data for serving ads (no retargeting, no personalized advertising built on this data, no lookalike audience modelling).
• We do not allow humans to read user data beyond what’s required for the contracted advertising service.
• We do not sell Google Ads API data.
• We do not use Google Ads API data to train AI or machine-learning models — either our own or those of our sub-processors. Where Anthropic’s Claude is used, it is used under the Anthropic API terms that contractually prohibit training on customer inputs.

Full Privacy Policy with the Limited Use disclosure: https://kit-marketing.com.ua/privacy-policy/

Incident response

In the event of a suspected data incident affecting Google Ads API data, we will:
1. Isolate the affected systems within 24 hours of confirmation
2. Notify the affected client(s) within 72 hours
3. Notify Google API support if the incident relates to API access misuse
4. Conduct a post-incident review and update controls

Google APIs we use

• Google Ads API (this application)
• Google Analytics 4 Data API (already enabled in the same Cloud project)
• Google Merchant Center API (already enabled — used for clients running Shopping campaigns)

RU (короткая версия)

Google Ads API — описание use case

Это НЕ инструмент, единственное назначение которого — подбор ключевых слов. KeywordPlanService мы вызываем только как вспомогательный шаг при создании и ведении кампаний.

Компания: Kit Marketing (ФОП Цвєтков Ілля Олександрович)
MCC: 576-345-4890
Адрес: вул. Незалежної України, 3, м. Запоріжжя, Запорізька область, Україна, 69000
Privacy Policy: https://kit-marketing.com.ua/privacy-policy/

Что делаем через API

Управляем кампаниями Google Ads в аккаунтах, прилинкованных к MCC 576-345-4890. Используем API для создания и ведения кампаний, ставок, бюджетов и отчётности. Только для внутренней работы агентства, не SaaS.

AI Claude — только чтение

Claude используется как read-only ассистент для наших 4 медиабайеров. Никаких автономных изменений: каждое API write делается аутентифицированным сотрудником. Claude никогда не имеет write-доступа к Ads API. Данные не используются для обучения моделей.

Полный документ — выше на английском.

UA (коротка версія)

Google Ads API — опис use case

Це НЕ інструмент, єдине призначення якого — пошук ключових слів. KeywordPlanService ми викликаємо лише як допоміжний крок під час створення та ведення кампаній.

Компанія: Kit Marketing (ФОП Цвєтков Ілля Олександрович)
MCC: 576-345-4890
Адреса: вул. Незалежної України, 3, м. Запоріжжя, Запорізька область, Україна, 69000
Privacy Policy: https://kit-marketing.com.ua/privacy-policy/

Що робимо через API

Керуємо кампаніями Google Ads в акаунтах, прилінкованих до MCC 576-345-4890. Використовуємо API для створення і ведення кампаній, ставок, бюджетів та звітності. Лише для внутрішньої роботи агенції, не SaaS.

AI Claude — лише читання

Claude використовується як read-only асистент для наших 4 медіабаєрів. Жодних автономних змін: кожен API write робиться автентифікованим співробітником. Claude ніколи не має write-доступу до Ads API. Дані не використовуються для навчання моделей.

Повний документ — вище англійською.