Skip to main content

Introduction

Yahoo Japan Display Ads (YDA, also known as YDN) is the display advertising product of Yahoo! JAPAN Ads, covering banner, native, and video placements across the Yahoo! JAPAN network and its partner sites in Japan. The connector imports account structure and daily performance through the Yahoo Ads Display API, and standardizes them into Adriel’s internal model. As a marketing connector, metrics, breakdowns, and currencies are standardized so widgets can aggregate across sources without additional configuration. Compared with Yahoo Japan Search Ads, Display Ads adds video and viewability metrics plus audience (age, gender), prefecture, and site breakdowns, and does not support keyword-level reporting. To connect this data source, see How to connect Yahoo Japan Display Ads to Adriel.

Data refresh strategy

Architecture data

Architecture covers ad accounts, campaigns, ad sets (ad groups), and ads. It refreshes at 4:00 PM UTC and 5:00 AM UTC.

Reports data

Reports include daily performance for ad accounts, campaigns, ad sets, and ads. Cache only. Report data comes from cached daily performance snapshots. When a dashboard loads, values are aggregated from the last snapshot rather than fetched live. Because of this, metrics based on uniqueness (such as reach) can be overvalued when viewed over a range longer than one day. Initial backfill. When the data source is created, the cache is filled for the last 93 days at the ad account, campaign, ad set, and ad levels. Refresh schedule. Report data refreshes on three overlapping schedules:
  • 7:00 AM UTC, every 5 days — syncs the last 90 days
  • 8:00 PM UTC and 3:00 AM UTC daily — syncs the last 5 days
  • 4:00 PM UTC daily — syncs the last 30 days
Each schedule covers the ad account, campaign, ad set, ad, and audience/geo breakdowns (device, country, location, age, gender, region). Data is considered reliable within the cache sync period; data outside this range may be incomplete, missing, or not fully accurate due to legacy caching behavior.

Architecture levels

Ad account → Campaign → Ad set (ad group) → Ad Keyword-level reporting is not supported for Display Ads and always returns empty.

Date range limits

To keep query sizes manageable, the connector enforces these maximum look-back windows per time breakdown:

Metrics

How to read the columns Data type uses this vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean. API Key in code style like Impressions is the literal field returned by the Yahoo Ads Display API. Italic text describes how a value is produced when it is derived by Adriel rather than mapping to a single API field.

Delivery & clicks

Cost & spend

If an ad account’s currency differs from the Adriel workspace currency, costs are converted to the workspace currency using the current day’s exchange rate.

Conversions & value

Any conversion event tracked in the ad account is imported automatically, but only appears on the dashboard when the underlying event is active in the account. For each imported conversion, Adriel also generates derived KPIs — CVR, CPA, and ROAS.

Custom conversion events

Each conversion event active in the ad account produces its own set of metrics. For an event named [conversion_name]:

Video performance

Viewability

Viewability metrics are specific to Display Ads. When the Site breakdown is active, VIEWABLE_CLICK and MATERIAL_VIEWABLE_IMPS are excluded from the results.

Engagement

Campaign structure & metadata

The connector also exposes raw Yahoo Ads fields prefixed “Yahoo Japan Ads:” — including Title1–3, Description 1–2, Final URL, Display URL, Destination URL, Directory1–2, Tracking URL, Focus Device, Show ads on, Ad Type, Ad strength, Label, Custom parameter, and campaign / ad set / ad tracking IDs. Each maps to the platform field of the same name.

UTM tracking

UTM values are parsed by Adriel, not returned by Yahoo. Adriel reads the UTM query parameters from each ad’s configuration and landing URL and exposes them as metrics for rollup.

Breakdowns

Standard hierarchy

Audience & geography

Device & placement

Time & date grouping

Time and date breakdowns are Adriel-side aggregations of the same underlying daily data.

Creative analysis

Adriel post-processes ad creatives to generate these breakdowns.

UTM tracking

Yahoo does not return UTM values; Adriel parses them from each ad’s configuration and landing URL and exposes them as breakdowns for grouping.

Overview & status

These grouping options are provided by Adriel for cross-connector consistency.

Limitations

  • Cache only — report data comes from cached daily snapshots, not live queries. Uniqueness-based metrics (such as reach) can be overvalued over ranges longer than one day, and data outside the cache sync period may be incomplete or inaccurate.
  • No keyword reporting — keyword-level reports and the keyword breakdown are not supported for Display Ads and return empty.
  • Site breakdown constraints — the Site (ad delivery URL) breakdown cannot be combined with the ad level, and it drops the VIEWABLE_CLICK and MATERIAL_VIEWABLE_IMPS metrics.
  • Limited impression share — only budget-loss and rank-loss impression share fields are available; exact-match, search-top, and absolute-top variants are not.
  • Date range caps — daily 93 days, weekly 1 year, monthly 2 years.

API references

See also