Skip to main content
Google Ads scripts run inside your account with upload limits. API v23 runs outside with ScopeManifest constraints and tamper-evident audit — the same Conductor that manages Meta and Amazon simultaneously.

Google Ads API v23 — bid adjustments, creative generation, causal ROAS without the UI.

API-only writes. Shopping + Performance Max + Search in one Conductor.

Start freeSee pricing

EXSEL connects to Google Ads via the official Google Ads API v23. All bid adjustments, budget changes, and creative writes go through the API — no browser extension, no UI automation, no SERP scraping. Product Studio alpha integration enables AI image generation for Shopping ads. Causal ROAS is confirmed via DoWhy 3-refuter gate (p < 0.05) before EXSEL recommends bid changes. Shopping, Performance Max, and Search campaigns are supported. Connector is $29/mo; first connector is free on the free plan. ---

What we do via Google Ads's official APIs

  • Google Ads API v23 for bid / budget / creative writes.
  • Product Studio alpha integration for image generation.
  • Causal ROAS across campaigns.
  • Ad-disapproval ACKs (safety floor).

What we refuse to do (it's in the code)

  • Extension-based automation — not our path.
  • SERP scraping for bid intelligence — never (we use official API signals).

How it feels in the ClientConductor

Your ClientConductor's Google Ads actions respect the per-action ModeGate mode you set. Default on every AI specialist = manual (Conductor drafts, you approve). Opt-in per AI specialist to 2FA-gated autonomous or tamper-evident audit mode. See [/agents#client-conductor](/agents) and [/security](/security).

---

Pricing

Connector SKUPriceQuota
Google Ads connector$29/mo5k writes + 20k reads (defaults)

Zero-suspension posture

  • No platform has ever suspended a merchant because of us — architecturally enforced (G47).
  • Scope manifest quarterly-reviewed in CI.
  • Credentials never leave merchant device for any UI-driven action (Companion path).
  • Tamper-evident audit available for sensitive workloads (ADR-044).

Exit-intent drawer

> Before you go — the scope manifest for Google Ads. > 1-page PDF. Every action we're allowed to take, every action we refuse. Share with procurement. > > [ you@company.com ] > [ Send me the manifest → ]

---

Close

3 numbered steps: 1. [ Start free ] — pick Google Ads as your one free connector. 2. Run the Conductor on read-only for a week. 3. Unlock one AI specialist when the value is obvious.

---

Frequently asked questions

Q: What does Google Ads API v23 allow EXSEL to do that Google Ads Scripts cannot?

Google Ads Scripts run client-side in the browser and are limited by the JavaScript runtime's capabilities and quota. The Google Ads API v23 is a server-side REST/gRPC API with higher rate limits, full access to the resource hierarchy (campaigns, ad groups, ads, keywords, bidding strategies), and support for batch mutations. EXSEL calls the API from a server-side process — your Google Ads credential is authenticated once via OAuth; EXSEL executes API calls asynchronously within ModeGate constraints, not inline in a browser session.

Q: What is Google Product Studio alpha and what can EXSEL do with it?

Google Product Studio is Google's AI-powered image generation tool for Shopping ads, currently in alpha access for eligible Merchant Center accounts. When your account has alpha access, EXSEL can request image variations of your product photos via the Product Studio API endpoint — a different background, a lifestyle context, a seasonal overlay. The generated images are returned to EXSEL, reviewed via your configured ModeGate mode (Manual by default), and submitted to your Shopping campaign if approved. EXSEL does not generate images independently of Product Studio for Google campaigns.

Q: How does EXSEL measure causal ROAS across Performance Max campaigns?

Performance Max campaigns bundle Search, Shopping, Display, YouTube, and Discover into a single campaign. Google's attribution model for PMax is last-click with some data-driven attribution. EXSEL runs its own causal analysis layer using DoWhy — it instruments a 3-refuter gate (Placebo, Data Subset, Random Cause) with p < 0.05 required on all 3 and Cohen's |d| ≥ 0.2 before attributing ROAS improvement to a specific EXSEL bid action. This does not replace Google's attribution; it is an additional causal confirmation step that gates whether EXSEL recommends repeating the action.