Skip to main content

​
Introduction

Display & Video 360 (DV360) is Google’s enterprise demand-side platform for programmatic display, video, audio, and connected-TV buying. The connector ingests advertiser, insertion order, line item, and creative performance through the Display & Video API and offline reporting, so campaigns bought in DV360 report alongside other channels. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. To connect this data source, see How to connect Google Display & Video 360 to Adriel.

​
Data refresh strategy

​
Architecture data

Architecture covers ad accounts (advertisers), campaigns (insertion orders), ad sets (line items), and ads (creatives). It refreshes twice daily, at 4:00 PM UTC and 5:00 AM UTC.

​
Reports data

Cache-only. Report data is served from cached daily performance snapshots. Dashboard views aggregate from the most recent snapshot rather than fetching fresh on every load. Metrics based on uniqueness, such as reach, can appear overvalued when viewed across a period longer than one day. Initial backfill. On data source creation, the cache fills with 365 days of history for ad account, campaign, ad set, and ad. Refresh schedule. Reports refresh once per day at 7:00 PM UTC, syncing the last 10 days for ad account, campaign, ad set, ad, and the country-by-ad-account breakdown. Data is considered reliable within this sync window. Data outside the window may be incomplete, missing, or not fully accurate due to legacy caching behavior.

​
Architecture levels

Advertiser → Insertion order → Line item → Creative In the standardized model, advertiser maps to ad account, insertion order to campaign, line item to ad set, and creative to ad, so DV360 reports alongside other ad platforms. In DV360’s native hierarchy, advertisers belong to a parent partner.

​
Date range limits

DV360 offers daily and monthly date breakdowns. Each has a maximum look-back window; ranges longer than the limit are automatically shortened.

​
Metrics

How to read the API Key columnCode style like METRIC_IMPRESSIONS is the literal Display & Video 360 API metric name. Italic text describes how a value is produced when it is computed by Adriel rather than fetched from a single API field.

​
Cost and revenue

​
Delivery and clicks

​
Viewability

​
Reach

Reach is a uniqueness-based metric. DV360 counts unique users within each daily snapshot, so reach can appear inflated when aggregated across a period longer than one day. Reach also requires a country breakdown and monthly granularity to return meaningful values.
Additional Unique Reach and Coviewed Reach group metrics (for example click reach, impression reach, viewable-impression reach, and average impression frequency) and Unique Reach Audience metrics (for example percentage composition impressions and target rating points) are also available and route to DV360’s reach report types.

​
Video and audio

​
Conversions

Floodlight conversion metrics, keyed as floodlight:{activity name}, only appear when the DV360 advertiser is linked with Campaign Manager 360. Without that link, Floodlight fields are not returned.

​
Breakdowns

​
Ad hierarchy

​
Geographic

​
Time

Time breakdowns are Adriel-side aggregations of the same underlying daily snapshots, not separate data pulls.

​
Limitations

Based on the current connector, Google Display & Video 360 has the following limits:
  • Cache-only reporting — report data comes from a daily cache rather than a live fetch. Numbers outside the 10-day rolling sync window stay anchored to the last snapshot, and uniqueness-based metrics such as reach and frequency can appear inflated over long date ranges.
  • Reach requires a country breakdown and monthly granularity — requesting reach (or any Unique Reach group metric) without a country breakdown produces an API error, and reach cannot be combined with advertiser-currency segmentation. Monthly granularity is required for meaningful numbers.
  • Gender and age breakdowns are not offered by this connector — their availability varies by campaign type, which would make segmented totals inconsistent with non-segmented queries.
  • Invalid Clicks and Invalid Impressions drop with country segmentation — adding a country breakdown silently removes these two metrics from the query because they are incompatible with country segmentation.
  • Floodlight conversions require a CM360 link — Floodlight activity metrics appear only when the advertiser is linked with Campaign Manager 360.
  • Weekly date breakdown is not offered — only daily and monthly date breakdowns are available.
  • Fetch window — the maximum fetchable date range per request is 700 days, and the cache soft limit is 365 days.
  • Report generation latency — DV360 builds reports asynchronously, so time between a refresh and data availability depends on report size and Google’s job queue.
  • Custom saved queries use a separate connector — user-authored DV360 saved queries are supported through the separate DV360 Report connector, which caches a free-format report file on its own schedule.

​
API references

​
See also