API management

Bulk changes through the API, checked in the interface.

The approach

Some changes are too big for the interface. Five hundred negatives across twelve campaigns. Conversion values updated from last quarter's CRM data. Budgets reset from a spreadsheet. Offline conversions uploaded daily. These go through the Google Ads API or scripts, and AI writes most of that code.

Nothing stands until a person has looked at it in the interface. That is the rule. The machine produces the change, the change is reviewed where its effect is visible, then it is applied. Every change gets a log entry and a way back.

What this covers

Account-level negative and brand lists. Most accounts have never had either. Brand lists match Google's own entity for a brand, so they catch misspellings and variants the way a keyword negative never will. We build the job-seeker list, the competitor list and the complaints list once, at account level, and every campaign inherits them.

Conversion value updates from the CRM. Quarterly, or monthly where volume allows, the per-action values are re-derived and pushed.

Bid caps, budgets and schedules across portfolios.

Search term mining at scale, with the machine proposing and a person deciding.

Structural changes when the account needs them, staged so the client can see each step.

Since 17 August 2026 Google has changed how a target behaves on a budget-capped campaign. Managing that interaction properly across an account is exactly the kind of work that needs a script and a reviewer, and it is the reason the weekly loop exists.

What you get

A change log you can read. An approval step you can see. Rollback for anything we push. The scripts, documented, in your account.

Related: 17 August: Google converted a setting into a job · Brand lists vs negative keywords

Book a call