Google Ads

Build Google Search campaigns — responsive search ads and keywords — on an app-owned agency account, funded by the same prepaid budget wallet as Meta, with every launch gated by your approval and a hard wallet ceiling.

Google Ads runs Search campaigns (responsive search ads + keywords) on an app-owned agency account, funded by the same prepaid budget wallet as Meta ads. You build a campaign by asking the dispatcher; the agent authors it step by step and leaves it paused until you approve going live. The wallet is the hard ceiling — a campaign's daily budget can never exceed your available balance, and if the wallet hits zero every campaign is paused.

Google Ads vs Meta

Both platforms share the same wallet and the same approval + reconciliation model, but the work differs. Meta is paid social — interest/audience targeting and image creative, produced as a one-click campaign draft plus a daily monitor. Google is Search — keyword targeting and text ads, authored conversationally through the dispatcher. There's no separate daily Google monitor yet; you pull performance on demand (see below).

Prerequisites

A funded budget wallet. Your first deposit provisions a dedicated USD Google Ads customer for the product (a 10-digit customer ID under the shared agency manager account). Until the wallet is funded, there's no account to build in. Deposits share the same tiered management fee as Meta — standard 15%, reduced 12% for deposits at or above $100 — deducted at deposit time.
Google Ads must be enabled for your workspace by the operator (it's gated on platform credentials). If it isn't configured, the agent will tell you it's unavailable rather than half-build a campaign.

Unlike Meta, Google has no Page concept — there's nothing to connect beyond a funded wallet.

Build a campaign

Ask the dispatcher in plain language:

draft a Google Search campaign for our API monitoring tool,
budget $20/day, targeting "uptime monitoring" and "api monitoring"

The agent authors the campaign as a chain of steps, each starting paused:

Daily budget — an average daily spend in your wallet's currency. This step is wallet-gated: a daily budget that exceeds your available balance is rejected before anything is created.
Search campaign — always created paused, on the Google Search and Search-partner networks (the Display/content network is off by default). The bidding strategy defaults to Manual CPC; Maximize conversions and Maximize clicks are available but need conversion tracking to perform well.
Ad group — groups the ads and keywords, with an optional default max-CPC bid.
Responsive search ad — Google assembles headlines and descriptions into the final ad. The constraints are enforced: 3–15 headlines (≤30 characters each) and 2–4 descriptions (≤90 characters each), plus optional display-URL path segments (path1/path2, ≤15 characters).
Keywords — added in a batch, each with a match type: broad, phrase, or exact.

The result is a complete but paused campaign. Review the headlines, descriptions, keywords, and budget, then approve — setting a campaign live is the only step that spends money, and it never happens without your explicit approval.

Example responsive search ad

A responsive search ad for a landing page might look like:

Final URL:    https://example.com/pricing
Headlines:    "API Uptime Monitoring" · "Know Before Users Do"
              · "5-Minute Setup" · "Free 14-Day Trial"
Descriptions: "Catch downtime in seconds with real-time alerts to Slack & email."
              "Monitor every endpoint. No credit card to start."
Paths:        /pricing /trial
Keywords:     "uptime monitoring" (PHRASE), "api monitoring" (PHRASE),
              "website monitoring tool" (BROAD), "pingdom alternative" (EXACT)

Google rotates the headlines and descriptions into combinations and learns which perform best, so give it varied, non-redundant assets.

Check performance

Once a campaign is live, ask the dispatcher for a read. Two paths exist under the hood:

Campaign performance by date range — presets TODAY, YESTERDAY, LAST_7_DAYS, LAST_14_DAYS, LAST_30_DAYS, THIS_MONTH, LAST_MONTH. Cost comes back in your wallet's currency (cents).
Custom reporting via a read-only GAQL query for ad-group- or keyword-level detail. Note that GAQL has no SUM() (totals are aggregated in code) and money fields are in micros — 1,000,000 micros = $1.

how is my Google Search campaign doing over the last 7 days?

How spend is capped

The wallet is the hard ceiling on Google Ads, exactly as it is for Meta:

Mechanism	Effect
Per-day budget cap	A campaign's daily budget can't exceed your available wallet balance — the create call is rejected otherwise.
Approval gate	No campaign is set to `ENABLED`, and no money is spent, without your explicit approval in the run.
Reconciliation	Spend is reconciled against the wallet; when the balance reaches zero, every enabled campaign is paused.

Topping the wallet back up clears the paused-for-no-budget state, but campaigns are not auto-resumed — relaunching is an explicit action you take.

Notes & limits

Search only. This loop authors Search campaigns (responsive search ads + keywords). Display, Performance Max, Shopping, and video are not covered yet.
No one-click drafter skill yet. Meta has a dedicated campaign drafter that emits a one-click deploy artifact; Google campaigns are built conversationally through the dispatcher. The approval-before-live and wallet guarantees are identical.
No daily Google monitor yet. The daily recommend-only audit (the monitor) is Meta-only today — for Google, pull performance on demand.
Everything starts paused. Both the campaign and its responsive search ad are created paused; going live is always a separate, approved step.
All money is handled in cents (USD) server-side and shown to you in your wallet's currency.