> ## Documentation Index
> Fetch the complete documentation index at: https://docs.adriel.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Data reference

> Metrics, breakdowns, refresh cadence, and limits for the Yandex Direct data source in Adriel.

## Introduction

Yandex Direct is Yandex's paid advertising platform, serving search and display ads across Yandex Search, the Yandex advertising network, and partner sites. It is the primary paid-media channel for the Russian-speaking market. Advertisers manage campaigns, ad groups, and ads in Yandex Direct, and the connector imports the resulting structure and daily performance data through the Yandex Direct API v5.

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 Yandex Direct to Adriel](/data-sources/o-z/yandex-direct/how-to-connect).

## Data refresh strategy

### Architecture data

Architecture covers the ad account, campaigns, ad groups, and ads. It refreshes twice daily, at **01:00 and 14:00 UTC**.

### Reports data

Reports include daily performance metrics for the ad account, campaigns, ad groups, and ads.

**Cache-only.** Report data is served from Adriel's daily cache rather than fetched live on each dashboard load. When a dashboard opens, values come from the most recent cached snapshot. On connection, the cache is backfilled for the previous **365 days** at the ad account, campaign, ad group, and ad levels.

**Refresh schedule.** Reports refresh once daily:

* **10:00 PM UTC** — syncs the last **7 days** for campaign, ad group, and ad.

Data is considered reliable within the cache sync window. Data outside that window may be incomplete, missing, or less accurate.

## Architecture levels

Ad account → Campaign → Ad group → Ad

Yandex Direct has no native ad-account report level; ad-account figures are aggregated from campaign-level data. Keyword data exists in the architecture but is not available for reporting (see Limitations).

## Date range limits

To keep query sizes manageable, the connector enforces a maximum look-back window per time breakdown.

| Breakdown | Max range |
| --------- | --------- |
| Daily     | 93 days   |
| Weekly    | 1 year    |
| Monthly   | 2 years   |

## Metrics

<Note>
  **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 `Clicks` is the literal Yandex Direct API field name.
</Note>

<Note>
  Yandex reports monetary values in micro-units. Adriel divides Cost, Profit, and Revenue by 1,000,000 before storage, so the cost metrics below appear in whole currency units.
</Note>

### Delivery & clicks

| Metric               | Description                                                                                 | Data type | API Key               |
| -------------------- | ------------------------------------------------------------------------------------------- | --------- | --------------------- |
| Impressions          | Total times the ads were shown.                                                             | Number    | `Impressions`         |
| Weighted impressions | Yandex's weighted impression count, adjusting raw impressions by its viewability weighting. | Number    | `WeightedImpressions` |
| Clicks               | Total clicks on the ads.                                                                    | Number    | `Clicks`              |
| Sessions             | Sessions recorded on the linked site after an ad interaction.                               | Number    | `Sessions`            |
| Bounces              | Sessions that bounced (single-page or below-threshold visits).                              | Number    | `Bounces`             |

### Cost & spend

| Metric   | Description         | Data type | API Key |
| -------- | ------------------- | --------- | ------- |
| Ad spend | Total amount spent. | Currency  | `Cost`  |

### Conversions & value

| Metric          | Description                                                  | Data type | API Key       |
| --------------- | ------------------------------------------------------------ | --------- | ------------- |
| Conversions     | Attributed actions matching the campaign's configured goals. | Number    | `Conversions` |
| Revenue (Pixel) | Revenue attributed to conversions.                           | Currency  | `Revenue`     |
| Profit          | Profit reported by Yandex (revenue minus cost).              | Currency  | `Profit`      |

## Breakdowns

Yandex Direct reports return no field-level breakdowns (no demographic, device, geographic, or time-of-day splits). Results are grouped only by the architecture hierarchy — one marketing level per query.

### Standard hierarchy

| Breakdown  | Description                  | API Key                                 |
| ---------- | ---------------------------- | --------------------------------------- |
| Ad account | Group results by ad account. | *Aggregated from campaign-level report* |
| Campaign   | Group results by campaign.   | `CampaignId`                            |
| Ad group   | Group results by ad group.   | `AdGroupId`                             |
| Ad         | Group results by ad.         | `AdId`                                  |

## Limitations

* **Keyword level not supported** — keyword data exists in the architecture, but keyword-level performance reports are not available and are intentionally disabled.
* **Video and reach metrics not available** — reach and the video quartile/view metrics are defined internally but are not requested from the Yandex API, so they do not appear in reports.
* **Cache-only reporting** — report data is served from the daily cache, not fetched live; data outside the cache sync window may be incomplete, missing, or less accurate.
* **No native ad-account reporting level** — Yandex Direct has no ad-account report type, so ad-account figures are aggregated from campaign-level data.

## API references

* [Yandex Direct API v5 overview](https://yandex.com/dev/direct/doc/dg/concepts/about.html)
* [Reports service](https://yandex.com/dev/direct/doc/reports/reports.html)
* [Report field reference](https://yandex.com/dev/direct/doc/reports/fields-list.html)

## See also

* [How to connect Yandex Direct to Adriel](/data-sources/o-z/yandex-direct/how-to-connect) (paired how-to)
* [Meta Ads data reference](/data-sources/g-n/meta-ads/data-reference) — for another paid social/display ad platform
* [Google Ads data reference](/data-sources/g-n/google-ads/data-reference) — for another paid search and display ad platform