Yandex Direct

Yandex Direct exposes its statistics through a set of report types, from account-level totals to search queries, plus a custom report you group yourself. Renta exports any of them to your data warehouse, along with campaign and ad group metadata: impressions, clicks, cost, conversions, revenue, and video metrics.

Authentication

Renta uses OAuth to authenticate with Yandex. You will be redirected to Yandex to grant Renta limited access to your Yandex Direct account.

Pipeline configuration

On the final step, choose which Yandex Direct data to export and how Renta loads it.

Report configuration

Choose the report type first. It defines the grouping of the statistics and the set of fields available in the Parameters picker.

Parameters

Select the fields to include in the destination table. Your dataset schema is defined by the parameters you choose here.

Every row in the picker shows the display name with the API name below it: Campaign Id for CampaignId. The API name becomes the column name in the destination table, and values that Yandex Direct reports as empty arrive there as NULL.

Check the fields to export, or click Select All. The Selected tab counts everything you picked.

The statistics reports also offer calendar fields, so you can group the data without writing date functions in the warehouse. Week-based fields come in two variants: weeks starting on Sunday and ISO weeks starting on Monday.

The Custom report type also has utm_source, utm_medium, utm_campaign, utm_content, utm_term, and Ad URL. Renta fills these columns from the link of the ad, so they carry the tags you set in Yandex Direct. They work for text campaigns, dynamic text campaigns, and CPM banner campaigns; rows from campaigns of other types are exported with their statistics, but their UTM columns stay empty.

Dynamic parameters in ad URLs

Yandex Direct lets you put dynamic parameters into an ad link, so that the link passes the campaign, the keyword, or the device on to your analytics. Renta substitutes the values of the row, so the exported columns hold readable data instead of placeholders.

An ad tagged with utm_campaign={campaign_id} gives you the campaign identifier in the utm_campaign column.

A parameter that is not on this list stays in the exported value exactly as it appears in the link.

VAT and discount

Choose how Yandex Direct calculates the cost metrics before it returns them to Renta. Both settings apply to the whole report.

Cost metrics arrive in the advertiser's currency with two decimal places.

Table name and date range

Name the pipeline and set the historical period to load. A wide range takes noticeably longer on the first run than a few days.

1. Integration name.
   The name of the pipeline. It is used exclusively in the Renta interface.
2. Table name.
   The destination table name. You can keep the auto-generated name or enter your own.
3. Date start.
   The first date of the extraction period.
4. Date end.
   The last date of the extraction period. You can pick a fixed date or a relative option such as Today.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run. The setting appears once the Date parameter is selected.

On each run, Renta re-fetches the data starting from the date of the last successful run minus the overwrite period. The affected days are deleted from the destination table and inserted again, while older data stays untouched. The options range from Without overwrite data to Overwrite all data; the default is Last 1 day.

Schedule

Choose how often the pipeline runs.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Limitations

The Reports API sets boundaries that apply to every pipeline built on this source.

Sync strategy

The synchronization strategy depends on whether the report includes the Date parameter.