Pipeboard for Google

How Pipeboard uses it: Runs GA4 reports (standard, realtime, pivot) and lists the properties, dimensions, metrics, and conversion events available to you. This is the read access behind every reporting answer.

How Pipeboard uses it: Used only when you explicitly ask to change a property setup — creating or updating custom dimensions and metrics, or creating and deleting conversion events. Never used to alter your historical analytics data.

How Pipeboard uses it: Reads campaign, keyword, and performance data and applies the changes you ask for — creating, updating, or pausing campaigns, ad groups, keywords, and budgets. New campaigns are created in PAUSED status by default so you review before anything goes live.

How Pipeboard uses it: Two things, both of which you ask for explicitly. Reading: Pipeboard lists the Search Ads 360 customers (advertisers and manager accounts) you can access, runs the reporting queries you request — campaign, ad group, keyword performance, spend and conversions — and reads your custom column definitions and the API’s field metadata to build those queries. Writing: when you ask it to, Pipeboard uploads offline conversions (sales that closed off-site, by phone, CRM or in store), restates the value of a conversion after a refund or return, and marks a Floodlight activity’s uploads complete for a period so bidding is not left waiting on data. Those writes only ever add or correct conversion records you supply. Pipeboard cannot create, edit, pause, or delete campaigns, ad groups, keywords, budgets or bids in Search Ads 360 — no tool and no API we call can do that.

How Pipeboard uses it: Reading: Pipeboard lists the DV360 advertisers your Google account can reach, together with the partner that owns each one, and reads the campaigns, insertion orders, line items, creatives and targeting inside the advertiser you ask about. Writing is introduced separately and only ever applies a change you asked for in that conversation; nothing is created, paused or edited on its own.

How Pipeboard uses it: Display & Video 360 has no reporting inside its own API — every report runs through Bid Manager. Pipeboard uses this to build and run the reports you ask for (spend, impressions, delivery by campaign, line item, creative or audience) and to read the results back. The report definitions it creates are named with a "pipeboard:" prefix so you can recognise them in your own DV360 account.

How Pipeboard uses it: Reads your verified properties, Search performance data, sitemaps and URL inspection results — that is what answers every reporting question. The same permission covers the changes you explicitly ask for: submitting or deleting a sitemap, and adding or removing a site from Search Console. Pipeboard never edits your website or its content; it only manages these Search Console entries on your instruction.

How Pipeboard uses it: Reads your Merchant Center accounts, products, and diagnostics (issues, price competitiveness, best sellers, performance) and, when you ask, updates product attributes such as destinations and custom labels. Used only to surface insights and apply the changes you request.

How Pipeboard uses it: Lists folders and the image/video files inside them, and downloads a file you choose so it can be uploaded as an ad creative. Read-only: Pipeboard never creates, edits, or deletes anything in your Drive, and the file content is used only to complete the upload you asked for.