Search Ads 360
Run reports with the Search Ads 360 query language, and list the accounts, fields and custom columns you can read.
A Search Ads 360 connection gives a playbook's functions the Search Ads 360 Reporting API, from a document Auto ships. You sign in to Google and allow Search Ads 360 reporting, and the connection acts as you, for the accounts you reach. If you reach client accounts through a manager account, give its customer ID when you connect, and Auto sends it with every call as login-customer-id.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Search Ads 360
- Run a report with the Search Ads 360 query language over campaigns, ad groups, keywords, ads and their metrics, across the engines the account manages.
- List the accounts you can reach, the report fields a query may name, and the custom columns of an account.
The connection reads only; the Reporting API changes nothing.
The tools, as the connection lists them
Tools that read: searchads360.customers.searchAds360.search, searchads360.customers.listAccessibleCustomers, searchads360.searchAds360Fields.search, searchads360.searchAds360Fields.get, searchads360.customers.customColumns.list and searchads360.customers.customColumns.get.
An example workflow
A cross-engine keyword report for a client, every Friday. A schedule trigger runs the workflow at 15:00. A lookup function runs one query for the week's keywords with impressions, clicks, cost and conversions, by engine, and another reads the account's custom columns so that the client's own metrics come along. A computation function works out cost per conversion by engine and keyword and keeps the top and bottom twenty. A reasoning function reads them with the client's goals in its prompt and writes the week's commentary in the agency's voice: what moved, why it probably moved, and what the team proposes. An interaction function sends the commentary and the table to the account lead through an Outlook connection, who edits before anything reaches the client. The run's history in Studio keeps every week's rows, so a prediction function can forecast next month's conversions from them, with a likely range.
How to connect Search Ads 360
- Sign in to Google and allow Search Ads 360 reporting. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Search Ads 360 to Auto, or open Settings, Agents, Connections in Auto Studio and choose Search Ads 360.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
Auto asks for one value when you connect:
| Value | What it is |
|---|---|
manager_id, optional | The customer ID of the manager account you reach other accounts through, ten digits without hyphens; leave it empty when you connect an account directly. |
What it needs
- A Google account with access to the Search Ads 360 accounts the playbook reads, directly or through a manager account.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, a Google Cloud project of your own with the Search Ads 360 Reporting API enabled and an OAuth client registered for the runtime, as Let people add connections sets out.
Google grants Search Ads 360 as one scope, which names managing; the Reporting API the connection reaches offers reads alone.
Permissions Auto asks for
- Read and manage Search Ads 360 advertising data.
Good to know
A query's rows are kept in the run's history, where people with access to the playbook can read them. Search Ads 360's reporting is a day behind for some engines, as its interface is.