Display & Video 360
Read and change campaigns, insertion orders and line items, and run Bid Manager report queries.
A Display & Video 360 connection comes in two providers, and both sign in to Google. Display & Video 360 gives a playbook's functions the Display & Video 360 API, from a document Auto ships: the partners, advertisers, campaigns, insertion orders, line items, ad groups and creatives you reach, and changes to campaigns, insertion orders and line items. Display & Video 360 Reports gives them the Bid Manager API: report queries, their runs, their status and their reports. A report's file sits in Cloud Storage, which a call does not fetch.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Display & Video 360
- Read partners, advertisers, campaigns, insertion orders, line items, ad groups and creatives.
- Change campaigns, insertion orders and line items.
- Create, run, list and remove report queries, and read their reports and status.
The tools of Display & Video 360, as the connection lists them
Tools that read: displayvideo.partners.list, displayvideo.advertisers.list, displayvideo.advertisers.get, displayvideo.advertisers.campaigns.list, displayvideo.advertisers.campaigns.get, displayvideo.advertisers.insertionOrders.list, displayvideo.advertisers.insertionOrders.get, displayvideo.advertisers.lineItems.list, displayvideo.advertisers.lineItems.get, displayvideo.advertisers.adGroups.list and displayvideo.advertisers.creatives.list.
Tools that act: displayvideo.advertisers.campaigns.patch, displayvideo.advertisers.insertionOrders.patch and displayvideo.advertisers.lineItems.patch.
The tools of Display & Video 360 Reports, as the connection lists them
Tools that read: doubleclickbidmanager.queries.list, doubleclickbidmanager.queries.get, doubleclickbidmanager.queries.reports.list and doubleclickbidmanager.queries.reports.get.
Tools that act: doubleclickbidmanager.queries.create, doubleclickbidmanager.queries.delete and doubleclickbidmanager.queries.run.
An example workflow
Pacing, every morning. A schedule trigger runs the workflow at 07:00. A lookup function reads the active insertion orders and their line items, with their budgets and flight dates. A second lookup function reads yesterday's spend by line item from a report query the team set up once, through the Reports provider. A computation function works out, for each line item, the share of budget spent against the share of the flight elapsed. A reasoning function reads the line items that are far ahead or behind with the pacing rules in its prompt and proposes a change to each: a budget move, a bid change, or nothing with a reason. An interaction function sends the proposals to the trader through a Slack or Microsoft Teams connection and waits. Approved changes go through the line item patch operation, one interaction function run each. The run's history in Studio keeps every figure and every decision.
How to connect Display & Video 360
Display & Video 360
- Sign in to Google and allow Display & Video 360. The consent screen shows the permissions listed below.
Display & Video 360 Reports
- Sign in to Google and allow Display & Video 360 reporting. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Display & Video 360 to Auto, or open Settings, Agents, Connections in Auto Studio and choose Display & Video 360 or Display & Video 360 Reports.
- 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.
What it needs
- A Google account that is a Display & Video 360 user with access to the partners or advertisers the playbook reads.
- 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 Display & Video 360 API and the Bid Manager API enabled and an OAuth client registered for the runtime, as Let people add connections sets out.
Google grants Display & Video 360 as one scope, which covers deleting as well as reading; the connection's tools offer no delete of a campaign, insertion order or line item, only reads and changes.
Permissions Auto asks for
Display & Video 360:
- See, create, change and permanently delete Display & Video 360 entities and reports.
Display & Video 360 Reports:
- Read and manage Display & Video 360 reports in Bid Manager.
Good to know
A report's file lives in Cloud Storage and is read by the person or system that fetches it; a playbook records its location. Keep the Reports provider as a connection of its own, so a playbook that only reads line items never holds the reporting scope. What a function reads is kept in the run's history, where people with access to the playbook can read it.