Campaign Manager 360
Create and run reports, and read campaigns, advertisers, placements, ads, creatives and sites.
A Campaign Manager 360 connection gives a playbook's functions the Campaign Manager 360 API, from a document Auto ships. You sign in to Google and allow Campaign Manager 360 reporting and trafficking, and the connection acts as you, under your user profiles.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Campaign Manager 360
- Read your user profiles, and the campaigns, advertisers, placements, ads, creatives and sites they reach.
- Query the values a report dimension can take, and which fields a report may combine.
- Create a report, run it, and list reports and their files. A report file's content is a download that a call does not fetch; the operation answers where the file is.
The dimension and compatible-field queries are marked as tools that only read; creating and running a report count as acts, since Campaign Manager keeps them.
The tools, as the connection lists them
Tools that read: dfareporting.userProfiles.list, dfareporting.userProfiles.get, dfareporting.reports.list, dfareporting.reports.get, dfareporting.reports.files.list, dfareporting.reports.files.get, dfareporting.files.get, dfareporting.dimensionValues.query, dfareporting.reports.compatibleFields.query, dfareporting.campaigns.list, dfareporting.campaigns.get, dfareporting.advertisers.list, dfareporting.placements.list, dfareporting.ads.list, dfareporting.creatives.list and dfareporting.sites.list.
Tools that act: dfareporting.reports.insert and dfareporting.reports.run.
An example workflow
A placement check before a campaign goes live. An event trigger starts the workflow when your agent records that a campaign is ready for review. A lookup function reads the campaign's placements, ads and creatives. A computation function checks each placement against the trafficking sheet your team keeps in a Google Sheets or Excel connection: the dates, the sizes, the landing pages. A reasoning function reads the mismatches with the team's naming conventions in its prompt and writes a short list of what to fix and what is fine. An interaction function sends the list to the trafficker through a Slack connection and waits until they say the fixes are made or that the differences are intended. A second workflow, weekly, creates and runs the campaign's standard report and records where its file is, for the person who downloads it. Every check is in the run's history in Studio.
How to connect Campaign Manager 360
- Sign in to Google and allow Campaign Manager 360 reporting and trafficking. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Campaign Manager 360 to Auto, or open Settings, Agents, Connections in Auto Studio and choose Campaign Manager 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.
What it needs
- A Campaign Manager 360 user profile with access to the advertisers and campaigns the playbook reads, and API access enabled for your account by its administrator.
- 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 Campaign Manager 360 API enabled and an OAuth client registered for the runtime, as Let people add connections sets out.
Permissions Auto asks for
- Read and manage Campaign Manager 360 reports.
- Read and manage Campaign Manager 360 display ad campaigns.
Good to know
A report's file is read by the person who downloads it, not by the playbook; the workflow records the file's location. What a function reads, a campaign's placements for example, is kept in the run's history, where people with access to the playbook can read it.