TAEKWONDO.TV Reviewer documentation

TTV Holdings LLC

TTV Ad Engine

A private, internal paid-media control plane used only to research, prepare, review, and audit advertising for TAEKWONDO.TV's own accounts.

Company and purpose

Built for TAEKWONDO.TV's own advertising

TTV Holdings LLC owns and operates TAEKWONDO.TV, an independent taekwondo sports-data and media business. The public product helps people find athlete profiles, tournament schedules, draws, results, rankings, match histories, and related editorial coverage.

First-party use only

TTV Ad Engine is used by authorized TAEKWONDO.TV personnel for TTV-owned advertising accounts. It is not offered to agencies, advertisers, athletes, event organizers, or other external users.

No public control plane

There is no public account creation, sign-in, billing, third-party account management, campaign mutation endpoint, database connection, or credential on this host.

Relevant acquisition

The business use is to help people already searching for taekwondo athletes, tournaments, schedules, draws, results, rankings, and histories reach the corresponding canonical TTV destination or released app handoff.

Google Ads API functions

Narrow provider access, explicit operational boundaries

Read and reconcile

  • Read account and campaign structure.
  • Read delivery, policy, status, and search-term facts.
  • Keep provider delivery separate from first-party outcomes and backend contribution.

Research demand

  • Research athlete and tournament keyword demand.
  • Use deterministic localized candidate generation.
  • Preserve missing provider evidence as unknown rather than zero.

Prepare reviewed changes

  • Validate campaigns, ad groups, responsive ads, keywords, geographies, negatives, bids, and statuses.
  • Create or change only an exact, approved proposal.
  • Keep creation paused until a separate activation decision.

Safety model

Human approval stays between analysis and execution

  1. Deterministic input
    Canonical public TTV entities and bounded provider facts.
  2. Validation
    Local policy checks plus provider validate-before-create.
  3. Immutable proposal
    Exact payload, account, budget effect, expiry, and SHA-256 identity.
  4. Human approval
    A TTV owner reviews the precise before/after change.
  5. Paused write
    New delivery objects are created paused; deletes are blocked.
  6. Provider readback
    Material fields are queried and compared after the write.
  7. Audit
    Request identity, comparison, rollback, and stop evidence are retained privately.
  8. Separate activation
    Activation requires another bounded decision; it is never inferred.

What higher access does not change

There is no autonomous budget increase, activation, deletion, recursive optimization, or permission to spend. Standard Access changes throughput only; it does not relax TTV's proposal, approval, PAUSED-create, readback, budget, destination, privacy, or measurement controls.

Why Standard Access is requested

Deterministic localized inventory exceeds the Basic daily window

The current canonical candidate build contains 996,453 deduplicated exact-match athlete and tournament terms across nine released website locales. TTV's safety workflow validates the intended provider payload before a separately approved creation, so full validation plus creation is approximately 1,992,906 keyword operations before supporting objects and later management.

996,453current candidate terms
15,000/dayBasic Access operation window
~1.99Mvalidate-plus-create keyword operations

Higher quota is required to make deterministic review, validation, controlled onboarding, and later status management operationally feasible. It does not mean that the complete inventory will be activated simultaneously. TTV introduces bounded cohorts and stops expansion when provider reconciliation, destination health, relevance, attribution, or spending guardrails fail.

Sanitized evidence

The public diagrams show controls, not private account data

Diagram showing deterministic inputs flowing through validation, an immutable proposal, human approval, a paused provider change, readback, and audit.
Control flow. No analytical or scheduled process can manufacture approval or activation.
Diagram showing the public reviewer page separated from the private TTV Ad Engine and Google Ads account by a hard access boundary.
Access boundary. This host has no binding to the private tool, consumer application, database, user session, or provider credential.
Diagram comparing a 15,000-operation Basic Access daily window with an approximately 1.99 million-operation validated candidate workflow.
Scale justification. Counts are aggregate operational evidence; identifiers in the diagrams are explicitly synthetic.

Authentication and privacy

Credentials and customer data stay outside public output

Project-scoped access

Google Ads API access belongs to TTV's approved Google Cloud project. OAuth or service-account material, provider account identifiers, token history, private paths, proposal hashes, and credentials are never published here.

Data minimization

The integration does not export raw TTV email addresses, phone numbers, usernames, internal user IDs, payment data, customer lists, private content, or raw user search strings to the advertising provider.

No application tracking

This documentation includes no analytics tag, ad tag, consent manager, cookie, local storage, service worker, fingerprint, third-party application script, browser SDK, or application telemetry. TTV's existing Cloudflare security layer may inject a same-origin browser-verification script for non-verified traffic; it grants no access to TTV data or APIs.

Company references

Public policies and contact

Google Ads API review correspondence is handled through TTV's monitored role-based company contact at contact@taekwondo.tv.