Google Ads API — Tool Design Documentation

Submitted with the Basic Access application for developer token Iyz3T88p…Ochw

Company Innove Biz Solution LLC Website [Link]

Product AppAtlas — Android app discovery platform MCC ID 672-844-8680

([Link])

Cloud project 51017883235 Contact hello@[Link]

#

1. Business model and intended audience

Innove Biz Solution LLC operates AppAtlas, an Android app discovery and catalog platform.
AppAtlas researches open-source and independent Android applications, publishes structured
editorial profiles (features, safety, alternatives), and helps end users choose software. The tool that
uses the Google Ads API is AppAtlas's internal keyword research pipeline: it identifies which
app-related search terms real users type, how much demand each term has, and how competitive it is,
so that our editorial team covers the topics people actually search for.

Business model: the platform monetizes through standard display advertising and sponsored
placements on published content. The keyword research itself is an internal content-planning
function — the API data is not resold, not exposed via a public API, and not packaged into any third-
party product.

Intended audience: internal employees only — our content and research teams. No external users,
clients, or third parties can invoke the Google Ads API through our tool.

2. Tool architecture

Component Role Google Ads API usage

Research job queue Weekly jobs per catalog app —

(deduplicated by unique job keys)

Research worker Drains the queue; enforces per-provider Only caller of the Ads API; max 25
([Link] service) rate limits, retry with backoff, and a requests/minute, well below the 1
circuit breaker request/second Keyword Ideas limit

Credential vault AES-256-GCM encrypted storage of the —

OAuth refresh token and developer
token

Evidence store Immutable snapshots of every API Stores Keyword Planner responses for
response with SHA-256 checksums and auditability
timestamps

Editorial pipeline Turns researched terms into content —

briefs for human editors
Data flow: job queue → research worker → generateKeywordIdeas call (single keyword seed) →
response snapshot → volume/competition extraction → internal keyword tables → editorial
planning. No data flows outward from these systems to any party.

3. Google Ads API usage detail

3.1 Methods called

Method Frequency

[Link] ≤ 25 calls/minute; in practice a few hundred calls per

REST: POST week (weekly dedup per keyword)
/v24/customers/{cid}:generateKeywordIdeas

Read-only. We call no mutating methods: no campaign, ad group, ad, or budget operations of any kind. Token access to
Google Ads account data is limited to keyword metrics (search volume, competition index, bid-range micros).

3.2 Authentication design

OAuth 2.0 Desktop client in Google Cloud project 51017883235; scope requested:
[Link] .

The refresh token and developer token are stored only in our encrypted credential vault; they are
never logged, never returned by any API, and never written to source control.
Calls are authenticated per-request with a short-lived access token obtained via the refresh token;
tokens are held in memory only.

4. Compliance and data handling

No resale or redistribution: keyword metrics are used solely to prioritize internal content.
Raw API responses are never published, sold, or provided to third parties.
No user data: the tool processes keyword strings only — no end-user personal data is sent to or
received from the Google Ads API.
Rate and quota respect: client-side rate limiter (25 req/min), weekly per-keyword
deduplication, 3-attempt retry ceiling with exponential backoff, and a circuit breaker that halts a
provider for 15 minutes after 5 consecutive failures. The service fails closed on HTTP 403/429.
Auditability: every API response is stored as a checksummed, timestamped snapshot for
provenance review.
Terms adherence: the tool complies with the Google Ads API Terms of Service and the API
Access and Rate Policy; we do not circumvent blocks, scrape Google properties, or work around
quotas.

5. Tool interface (description)

The keyword research tool is an internal workspace with three surfaces:

Keyword Sources panel (admin): administrators connect data sources; the Google Ads API
connection shows only a masked key preview and a connection-test result. Credentials are write-
only from this interface.
Research panel (admin): queue of keyword research jobs with status (queued / running /
completed / retrying), record counts, and raw snapshot inspection for audit.
 Keyword tables (internal): the extracted metrics per keyword — monthly search volume,
competition index, bid range — used by editors to plan coverage. A sample row: "wifi analyzer
app" — 14,800 avg. monthly searches (US), competition index 67/100, top-of-page bid range
$0.25–$0.75 .

Document prepared by Innove Biz Solution LLC · hello@[Link] · [Link] · August 2026. This
documentation is provided for the Google Ads API Basic Access review and accurately describes the tool as implemented.