datascale
DEEN
Contact
Ads & Conversion APIs

Google Display & Video 360: The Google-Stack DSP

Google's DSP with YouTube access, Customer Match and Ads Data Hub. Third-party segments largely gone in the EEA.

Request a setup → To the DSP comparison

Platform profile

Regions
GlobalDACH
Channels
DisplayVideoCTVYouTubeAudioDOOH
Self-serve
Yes
Data fee model
Data CPM itemised, platform fee separate
Minimum spend
Access via Google sales or certified partners; terms depend on total volume in the Google stack.

Data & targeting

  • Data marketplaceYes
  • Third-party audiencesNo
  • First-party audiencesYes
  • Clean roomYes
  • Log-level dataNo
  • Geo targetingYes
  • Deal IDsYes
  • PMPYes

Measurement

  • Brand Lift
  • Reach reporting
  • Ads Data Hub analyses

Healthcare constraints

Google's healthcare policy is the strictest in the field: no health conditions as targeting criteria, and even contextual placements are restricted per category. Get policy clearance before healthcare campaigns, legal review required.

Limitations

  • Third-party audience segments are largely gone in the EEA.
  • No user-level log export; analysis happens in the clean room (Ads Data Hub) only.
  • YouTube inventory ties you to the Google ecosystem, and exclusive deals narrow the alternatives.

A fit when

  • Plans with a YouTube and CTV share bought from one seat.
  • Google-stack teams already running Customer Match and PAIR on a solid consent basis.
  • Setups that accept clean-room analysis instead of demanding raw data.

Not a fit when

  • Your strategy depends on third-party segments in the EEA; they effectively no longer exist here.
  • You need log-level data in your own warehouse; Adform or The Trade Desk fit better.

Privacy fit and data routes

First-party routes are the strength: Customer Match on hashed CRM data, PAIR for publisher matches without handing data over. Both presuppose solid consent. The privacy fit stands or falls with the setup in front of it. Area segments run through native geo targeting, without personal identifiers and therefore without consent dependency anywhere in the data path. Policy considerations remain, per category, with legal review before launch.

Third-party data and cost

Here DV360 is the outlier of the field in the EEA: third-party audience segments are largely removed. What remains is Google's own signals, context and first-party data. Data CPMs for remaining segments are itemised; the platform fee comes on top, separately.

Measurement, clean room and log-level

User-level raw data does not leave the platform. Ever. Analysis happens in Ads Data Hub, Google's clean room, with aggregation thresholds. Brand Lift delivers solid brand KPIs, but teams that want independent attribution in their own warehouse hit an architectural limit here that no contract clause moves.

Implementation

Floodlight tags plus server-side delivery from the shared event stream, with Consent Mode V2 as the mandatory foundation underneath everything. Deals and PMPs are negotiated from the seat directly. YouTube runs through the same interface, which simplifies frequency control across channels.

Preparing AreaSignal for DV360 review

AreaSignal is in development and market-entry phase. First integrations are coming soon. For planning and integration conversations, AreaSignal delivers geo segments with geography lists, scores, confidence, exclusion flags and exports. Field context: DSP comparison.

Assumptions behind the verdict

  • DACH campaigns under GDPR constraints.
  • Consent Mode V2 is implemented; without it the measurement chain breaks before the DSP.

Sources

Related services

Topical context

  • DV360 DACH
  • Display & Video 360 privacy
  • YouTube programmatic

Do your conversions actually arrive in the ads platforms? The Paid Media Tracking Audit settles it.

Request a Paid Media Audit →

More integrations we work with

← Back to all integrations