Yandex Metrica Logs API

Renta allows you to sync raw Yandex Metrica data collected through the Logs API to your data warehouse: non-aggregated session records (visits) and event records (hits), including traffic sources, UTM tags, Yandex Direct click data, device and geography attributes, goals, and e-commerce fields.

Authentication

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

Pipeline configuration

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

Report configuration

Point the pipeline at the counter and choose the report type.

1. Ad accounts.
   Choose the Yandex Metrica counter to export data from. The list contains the counters available to the connected Yandex account.
2. Report Types.
   Choose the type of raw data to export.

Parameters

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

The Parameters list shows every field available for the selected report type: over 130 session fields for Visits and over 80 event fields for Hits. With more than a hundred fields in the list, search saves the scrolling. Select All checks the whole list.

Renta also adds date fields to the list: date, year, quarter, month, week, and day fields that are calculated from the session or event date.

Fields that depend on the attribution model (traffic source, UTM tags, and Yandex Direct click fields) appear in the list as separate variants for each model: last significant source, first source, last source, and others. Pick the variants for the attribution model you use.

In the destination table, column names repeat the API names of the fields without the ym:s: and ym:pv: prefixes: ym:s:visitID becomes visitID.

Table name and date range

Name the pipeline and set the historical period to load.

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. Set it to Yesterday.

When you create the pipeline, Renta validates the configuration against the Logs API: it checks that the counter can prepare a log for the requested period and the selected fields. The Logs API accepts periods of up to one year per request, and the exact limit depends on the amount of data in the counter. If the period is too large, you get a validation error: shorten the date range and try again.

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.

How the export works

Log data is prepared on the Yandex side, so each run goes through several steps.

1. Renta creates a log request on the counter for the export window and the selected fields.
2. Yandex prepares the log asynchronously. Renta waits for the request to be processed, checking its status for up to 60 minutes.
3. Renta downloads all parts of the prepared log and loads them into the destination.
4. Renta deletes the prepared log request from the counter, so prepared logs do not pile up and spend the counter's 10 GB limit.

Sync strategy

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