Skip to main content

Introduction

Yahoo DSP (Demand-Side Platform) is a programmatic advertising platform that lets advertisers buy and manage digital inventory across Yahoo’s network and third-party publishers. The connector pulls campaign architecture and performance across display, video, native, connected TV (CTV), and digital out-of-home (DOOH) inventory. 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 Yahoo DSP to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets (line items), and ads (creatives). It refreshes twice daily at 4:00 PM UTC and 5:00 AM UTC. When the data source is created, the cache fills with 730 days of historical architecture data for the ad account, campaign, ad set, and ad levels.

Reports data

Reports include daily performance for ad accounts, campaigns, ad sets, and ads. Cache-only. Report data comes from cached daily performance snapshots produced by an asynchronous report pipeline (create a report job, poll until it completes, download the resulting CSV). Live fetch is not supported, so every dashboard query reads the most recent cached snapshot. Refresh schedule. Reports refresh every 6 hours, at 0 minutes past the hour (UTC). Each refresh syncs the last 10 days for the ad account, campaign, ad set, and ad levels. Data is considered reliable within the cache sync period; data outside this range may be incomplete or not fully accurate due to legacy caching behavior.
Metrics based on uniqueness, such as reach and unique households, can be overstated when viewed across a date range longer than one day, because daily snapshot values are summed.

Architecture levels

Yahoo DSP → Ad account → Campaign → Ad set (line item) → Ad (creative)

Date range limits

Data requested outside a breakdown’s maximum range may be truncated. Longer historical ranges remain available through the quarterly and yearly breakdowns.

Metrics

How to read the columnsData type uses Adriel’s vocabulary — Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like Ad Serving Cost is the literal Yahoo DSP report column the connector maps; italic marks a value Adriel computes or derives on its side rather than a single report column. Currency values are reported in each ad account’s configured Yahoo DSP currency.

Campaign Attributes

Campaign Structure

Click Performance

Computed Metrics

Conversion Performance

Custom conversion events are imported automatically. Any conversion event tracked in the ad account is imported and appears on dashboards only while the underlying event is active. For each imported conversion, Adriel also generates derived KPIs such as ROAS, CPA, and conversion rate, including dynamic custom conversions defined by the user.

Creative Attributes

Engagement

Video Performance

Yahoo DSP-specific

These metrics exist only for Yahoo DSP and aren’t part of any cross-connector category. Every group above is a standard category shared with other connectors.

Breakdowns

Campaign Structure

Creatives

Adriel post-processes ad creatives to generate these breakdowns.

Date

Yahoo DSP returns daily records; Adriel groups them into these views, so all time breakdowns are Adriel-side aggregations of the same underlying daily data.

Others

This grouping is provided by Adriel for organizing and rolling up report rows.

Target

Limitations

  • Cache-only reporting — reports come from cached daily snapshots, not live fetch. Every dashboard query reads the most recent snapshot, and values outside the 10-day rolling sync window (within the 730-day backfill) may be incomplete or not fully accurate.
  • Uniqueness metrics can be overstated — reach, unique households, and similar metrics are summed from daily snapshots, so multi-day ranges can overcount unique audiences.
  • No long-lived refresh token — Yahoo DSP’s JWT-bearer flow does not issue a refresh token. A fresh JWT is constructed and exchanged for a new access token (1-hour TTL) on demand whenever the current one expires. The exchange is invisible to dashboards.
  • Metric availability depends on access type — Seat access exposes the full metric set, including video completion counts and rates, viewability (Yahoo and Moat), frequency, and seat fees. General Access Network (GAN) access is limited to core delivery, click, conversion, VCPM, CPCV, and tracked-action metrics.
  • Channel-specific metrics — CTV metrics, such as unique households and average frequency per household, and DOOH metrics, such as audience impressions and average impression multiplier, appear only on those placement types; average frequency per household may be limited for EU audiences due to privacy restrictions. Yahoo Native mail-ad and tile metrics apply only to Yahoo Native placements under Seat access.
  • Date range caps per breakdown — daily breakdowns are capped at 93 days, weekly at 1 year, and monthly at 2 years; longer ranges rely on quarterly and yearly breakdowns.

API references

  • Reports are retrieved through the Yahoo DSP extreport asynchronous reporting API (create a job, poll until it succeeds or fails, then download the CSV).
  • Authentication uses Yahoo DSP’s JWT-bearer OAuth2 client-credentials flow; a short-lived access token is passed in the X-Auth-Token header.
  • Yahoo DSP API documentation

See also