google-ads-automation

IN BUILD

"I become the friction when we assume my own manual effort is part of that workflow. […] I want to do the API so this process has way less friction in future use cases."

STAGES

  1. proposal08-31
  2. requirements08-31
  3. design08-31
  4. tasks08-31
  5. build—
  6. archived—

CAPABILITY

  • google-ads-client5 requirements

OUTCOMES — AND HOW EACH IS MEASURED

  • ○1.1Authenticated client from vault-resolved env — a session under `op run` gets a working Ads client with no secret read from any filenot stated
  • ○1.2Missing credential names itself — an unset key fails fast with its registry name and a runbook pointer, not a Google stack tracenot stated
  • ○1.3One call creates a complete paused campaign — budget, campaign, ad group, ads, and keywords exist in the account, status PAUSED, IDs returnednot stated
  • ○1.4Pause and enable by ID — campaign status round-trips through the module and the returned state reflects itnot stated
  • ○1.5Change a daily budget — a dollar amount in, updated budget confirmed backnot stated
  • ○1.6Metrics for a date range — per-campaign impressions, clicks, cost, and conversions for an explicit rangenot stated
  • ○1.7Refresh token minted locally into the vault — Katy runs the helper, clicks consent once, and the output lands as vault items with every key registerednot stated

WHAT HAPPENED

  1. TASKS

    proposal and specs and design and tasks landed

    2026-08-31 · 1 pull request
    • #440feat(google-ads): shared campaign-control module via the Ads API

History read from a manifest built at 2026-09-30 (09e7bcc).

1 pull request, found by commits touching the change folder