Skip to main content

​
Introduction

Google Display & Video 360 Report is a data source variant for Google Display & Video 360 (DV360) that imports pre-configured offline reports rather than querying campaign data directly. Advertisers save a report in the DV360 UI with a title prefixed Adriel_ (for example, Adriel_2025-01-01_report_campaign); Adriel identifies matching saved reports, runs them via the DoubleClick Bid Manager API, and streams the resulting CSV into a per-asset cache. Because the metrics and breakdowns are defined inside DV360 by the user, this connector behaves like a query-driven data source — the shape of the data comes from the saved report, not from a fixed Adriel schema. To connect this data source, see How to connect Google Display & Video 360 Report to Adriel.

​
Data refresh strategy

​
Architecture data

This connector does not import a separate campaign / insertion order / line item hierarchy. Each Adriel asset corresponds to a single saved DV360 report, identified by its report title and the DV360 queryId.

​
Reports data

Reports are re-run through the DoubleClick Bid Manager API on a daily schedule. Each refresh calls queries.run on the saved DV360 report, downloads the resulting CSV from Google Cloud Storage, and atomically replaces the cached rows in the per-asset Postgres cache table. Refresh schedule. Daily at a fixed UTC hour (pending tech reviewer confirmation). Refresh strategy. ATOMIC_REPLACE — the cache is fully rewritten on each successful run; partial-day updates are not supported.

​
Metrics

How to read the columnsThe Data type column uses the platform’s ten-value vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.The API Key in code style is the literal column name returned in the DV360 report CSV. Because the report is user-defined, the exact set of columns depends on which metrics were selected when saving the report in DV360.
The metric catalog is defined by the saved DV360 report, not by Adriel. Any metric that DV360 allows in a saved report is available in Adriel once the report is saved with the Adriel_ prefix. Common examples include:

​
Breakdowns

Like metrics, breakdowns come from the saved DV360 report. Any column marked as a grouping field in the DV360 report becomes a breakdown in Adriel.
Common breakdowns include:

​
Time and date grouping

Time breakdowns available in Adriel widgets rely on the report having a native Date column. When present, Adriel groups the daily rows into common views for reporting.
These time groupings are provided by Adriel rather than by the saved DV360 report, so they carry no report column name.

​
Limitations

  • User-defined schema. Metrics and breakdowns are only what the saved DV360 report exposes. Adding or removing columns requires editing the DV360 report and re-syncing.
  • One asset per saved report. Each Adriel connection is bound to exactly one DV360 saved report (matched by queryId).
  • Title-prefix filtering. Only saved DV360 reports whose title begins with the Adriel_ prefix are surfaced during connection setup.
  • ATOMIC_REPLACE refresh. The cache is rewritten in full each run; there is no partial or streaming update.
  • Report generation timing. Data availability in Adriel depends on the DV360 report being successfully generated and stored in Google Cloud Storage before Adriel’s refresh window.

​
API references

​
See also

  • How to connect Google Display & Video 360 Report (paired how-to)
  • Google Display & Video 360 data reference — for the standard entity-hierarchy connector
  • Google Ad Manager data reference — for the report-style GAM equivalent