Agent PlannersAgent Planners
Advertising

AI agent for Search Ads 360: cross-engine reporting and conversion upload

TL;DR

Search Ads 360 is available to every organization: it arrived on 18 September as a scope preview and was released to everyone the same day once Google finished verifying the doubleclicksearch scope. It is also the platform where being clear about API limits matters most — the Reporting API is reporting only, and no tool built on it can change a campaign.

Connecting it, and what it asks for

  1. 1Open Integrations and click Connect on the Search Ads 360 card.
  2. 2Sign in with an account that can see the manager.
  3. 3Ask across engines — the point of SA360 is that one question spans them.
The authorization asks for doubleclicksearch. The Reporting API is read-only by design; the single write it carries is offline conversion upload. A first goal worth typing: Compare cost per conversion across every engine account under the manager for last month.

What the agent does with Search Ads 360

  • Reports across engine accounts with search and report over the SA360 Reporting API.
  • Discovers what a query can ask for via search_fields, and reads the account's own custom columns.
  • Lists accessible customers, so a manager account can find its clients.
  • Runs anomaly detection on SA360 metrics, the same mechanism the other platforms use.
  • Uploads and updates offline conversions — the only writes the scope carries.
Six reads, three writes. All three writes are conversion-related, and that reflects Google's API rather than a decision on our side.

What no SA360 integration can do

The Search Ads 360 Reporting API is reporting only. Campaigns, bids and budgets live on the engine account — Google Ads, usually — or in the SA360 interface. Any tool that claims to manage SA360 campaigns is either reaching the engine account underneath or overstating what it does.

That makes SA360 most useful here as the cross-engine reporting layer, with campaign changes happening on the engine account that Agent Planners also connects natively.

Offline conversion upload, and when it is the wrong tool

The one write the doubleclicksearch scope carries is the legacy Search Ads 360 API's conversion insert and update. It is how closed revenue gets back to the bidding, which for lead generation is usually the highest-leverage thing available.

A row keyed by customerId needs campaignId and adGroupId alongside it, and the segmentation type must be Floodlight. If your engine account is Google Ads and the conversions are click-based rather than Floodlight, the right route is Google Ads' own click-conversion upload — the same job through a different API, and the agent picks correctly rather than failing at the last step.

A manager account reading a client's data needs the login-customer-id header, the same shape as Google Ads MCC access.

Frequently asked questions

Does Agent Planners support Search Ads 360?
Yes, for every organization. It covers reporting across engine accounts, custom columns, anomaly detection and offline conversion upload.
Can the agent manage SA360 campaigns or bids?
No — and neither can any other tool built on this API. The SA360 Reporting API is reporting only; campaigns, bids and budgets are managed on the engine account or in the SA360 interface.
What can it write to SA360?
Offline conversions only: upload, update, and update availability. Those come from the legacy Search Ads 360 API rather than the new Reporting API.
My conversions are Google Ads clicks, not Floodlight — what then?
Those go through Google Ads' own click-conversion upload rather than SA360's, because SA360 conversion rows require Floodlight segmentation. Both platforms connect natively, so it is a routing decision rather than a blocker.
Connect Search Ads 360 and try it on your own account

Start free — 2,500 credits a month, no credit card. Reads are free; every write waits for you.

Related platforms

AI agent for Google Ads
Connect Google Ads (including MCC) and let an AI agent audit performance, mine negatives, rebalance budgets and build campaigns — every write pauses for your approval.
AI agent for DV360 (Display & Video 360)
Automate Display & Video 360 — insertion orders, line items, deals, audiences and Bid Manager reporting — with native reach forecasting and human approval on every write.
AI agent for Campaign Manager 360
Connect Campaign Manager 360 and let an AI agent run ad-server reports, audit campaigns, placements, creatives and Floodlight configuration, and reconcile CM360 delivery with your buying platforms. Trafficking writes stay human-approved.

How the agent works

Getting started
Connect an ad account, write a goal in plain language, and approve what the agent ships. The five-minute path from sign-up to your first optimization.
Approvals & workflow
Plan → approve → execute. How every write pauses at an approval gate, in-app or by email magic-link, with pre-approval, auto-approve, stale-state checks and the audit log.
Agent playbooks
Concrete, multi-step jobs the agent runs end-to-end — audits, budget rebalancing, search-term mining, remarketing, PMax, and cross-account cleanups. Copy a goal and go.
Connect your platforms
Natively connect Google Ads, Microsoft Advertising, DV360, Campaign Manager 360, Search Ads 360, Meta Ads, TikTok Ads, Reddit Ads, Pinterest Ads, Snapchat Ads, LinkedIn Ads, X Ads, Google Ad Manager, AdSense, AdMob, GA4, Search Console, BigQuery, Tag Manager, Merchant Center, YouTube, Klaviyo, HubSpot, GitHub, Shopify, SHOPLINE and Stripe — plus 250+ more apps (Gmail, Outlook, Slack, Notion, Salesforce…) via Composio and your own tools via custom MCP. Pick accounts with the context picker and run one task across an entire MCC.