>_

SpendSignoff documentation

The always-on operator for your ad accounts. Read and draft from your AI client — approve before anything goes live.

Ad platform

Integrate Google Display

Google Display campaigns are coming soon as a distinct surface. They ride the same Google OAuth connection as Google Ads, read-first, and follow the same draft-before-live model. This guide describes the planned surface.

Your AI can read and draft — it can never spend without your approval.

Status: coming soon

Dedicated Google Display handling is not live yet. Today you connect Google Ads, and Search campaigns are the supported draft surface. This page documents the planned Display-specific support so the read-first model is clear before it ships.

Google Display will use the same Google OAuth connection you already grant for Google Ads — no new link. The operator will read Display campaign structure and spend, then draft budget and bid changes you approve, with the same two-step control as the live surface.

Planned read-and-draft surface

Display campaigns sit inside the Google Ads tree. The operator is planned to read and draft against these objects via propose_change:

  • Display campaigns — status, daily budget, and bid strategy.
  • Ad groups — default bids, status, and the audiences or topics attached.
  • Budgets — campaign-level daily budgets, for reallocation.
  • Bids — target CPA and target ROAS where the strategy allows.
  • Audiences and placements — read for context; not editable in V1.
  • Performance — impressions, clicks, cost, conversions, and ROAS over recent windows.

How a change will happen

1

Use your Google Ads link

No new OAuth — Display rides the existing Google connection, which is issued mcp.read and mcp.draft only.

2

The operator reads structure and spend

It will read Display campaigns, ad groups, budgets, and recent performance to find pacing and bid problems.

3

It drafts a change

A proposed budget or bid change will land as a draft with the before → after diff and projected impact. Nothing live.

4

You approve and push live

You will review the draft and run the two-step Approve & push live → Confirm control before any write reaches the account.

Write access stays dormant until you approve

The same guarantee holds for Display: the Google connection grants read access, not spend authority. No write reaches your account until you approve a specific draft. There is no mcp.approve scope issued to the AI.

Not yet supported

Display-specific drafting is not active today — connect Google Ads and the operator works on Search campaigns now. Responsive display creative editing, placement and audience curation, and topic targeting are out of scope for the planned V1 surface.

Next

Google Ads

Live today — the same Google connection that Display will ride once it ships.

    Integrate Google Display — SpendSignoff Docs