How is this source different from the Yandex Metrica Logs API source?

The Yandex Metrica source exports aggregated reports built from the dimensions, metrics, and goals you select through the Reporting API. The Yandex Metrica Logs API source exports raw, non-aggregated data: each row is a single session or a single event. Use this source when you need ready-made statistics for dashboards, and the Logs API source when you need to build custom reports or join Metrica data with other sources at the user level.

Does Renta apply sampling to the data?

Renta requests every report with the maximum accuracy setting of the Reporting API and loads each day with a separate request, which keeps the sample of every request small. Yandex Metrica can still apply sampling on its side when a single day of the counter exceeds the API's sampling threshold (hundreds of thousands of sessions).

Why do figures for recent days change after the first load?

Yandex Metrica keeps updating session data for some time after the visit: about 99% of sessions are finalized within 3 days. Include the **Date** parameter in the report and set the **Overwrite period** to at least **Last 3 days**, so Renta reloads those days on every run and picks up the late updates.

Why don't I see the Goals tab in the Parameters picker?

Goal metrics are available for the **Sessions** report type. Select **Sessions** in **Report Types**, and Renta loads the goals of the selected counter into the **Goals** tab. The **Pageviews** report type works with pageview-level statistics and has no goal metrics.

Yandex Metrica

Renta allows you to sync aggregated Yandex Metrica reports to your data warehouse: session and pageview statistics built from the dimensions, metrics, and goals you select, including traffic sources, UTM tags, device and geography attributes, e-commerce revenue, and goal conversions.

Authentication

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

Your credentials are encrypted in transit and at rest, and never stored in Renta's application database. You stay in control and can revoke access from your Yandex account settings at any time.

Connect Yandex Metrica source

Follow these steps to add Yandex Metrica as a source in Renta using OAuth authentication.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the Analytics category and click the Yandex Metrica card.

Yandex Metrica card in the Analytics category of the Renta catalog

Authorize connectionStep 2

Click Log in to your Yandex Metrica account. You will be redirected to Yandex to grant access.

Authorize Yandex Metrica connection page in Renta

Choose a Yandex accountStep 3

Yandex shows the sign-in screen with the list of permissions Renta requests, including reading statistics of your own and delegated counters. Choose the account that has access to your Yandex Metrica counters and confirm. After that you are redirected back to Renta.

Yandex sign-in page with the account selection and the list of requested permissions

Name the connection and saveStep 4

Finish the setup:

Source name.
Specify a name for this data source. This is used exclusively in the Renta interface.
Access granted.
Verify that the account is connected successfully.

Click Save to finish.

If your Yandex authorization later changes (for example, after a password change), click Re-authorize on this source. The connection refreshes in place and every pipeline built on it keeps running.

Set up your Yandex Metrica connection with source name and access granted

Source createdStep 5

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Yandex Metrica source

Create a pipeline

Once the source is connected, create a pipeline to sync your Yandex Metrica data into your destination.

Create a Yandex Metrica pipeline

Link your Yandex Metrica source to a destination and configure the pipeline.

Select Yandex Metrica as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Yandex Metrica under Already connected and click Next step.

Select a source step with Yandex Metrica under Already connected

Select your Yandex Metrica connectionStep 2

Choose the Yandex Metrica connection you created earlier and click Next step.

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

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.

Yandex Metrica counter and report type selection

Ad accounts.
Choose the Yandex Metrica counter to export data from. The list contains the counters available to the connected Yandex account, shown by site name.
Report Types.
Choose the type of statistics to export.

Report type	Description
Sessions	Aggregated session statistics: visits, users, bounce rate, goal conversions, and e-commerce revenue, grouped by the dimensions you select (traffic sources, UTM tags, device, geography, and others).
Pageviews	Aggregated pageview statistics: pageview metrics grouped by dimensions such as page URL, domain, and page title.

Parameters

Select the dimensions, metrics, and goals to include in the destination table. Your dataset schema is defined by the parameters you choose here.

The picker is split into the Dimensions, Metrics, and Goals tabs: more than 300 dimensions and about 200 metrics for the Sessions report, over 100 dimensions and 9 metrics for the Pageviews report. Search is the fastest way through lists this long. Select All checks the open tab.

The Dimensions tab also includes date fields calculated by Renta from the session or pageview date: year, quarter, month, week, and day fields. When you select a calculated date field, Renta adds the date to the report automatically.

The Goals tab appears for the Sessions report. Renta loads the goals of the selected counter and offers per-goal metrics: conversion rate, visitor conversion rate, target visitors, target visits, goal achievements, achievements per visitor, and goal-based revenue. Composite goals get the same set of metrics for each step.

Dimensions that depend on the attribution model (traffic sources, UTM tags, and Yandex Direct click data) appear in the list as separate variants for each model: last significant source, first source, last source, last Yandex Direct click, cross-device variants, and automatic. Pick the variants for the attribution model you use.

In the destination table, column names repeat the API names of the parameters without the ym:s: and ym:pv: prefixes: ym:s:visits becomes visits. Revenue metrics are exported in the currency of the counter, and the currency code is removed from the column name. Renta also adds a counter_id column to every row.

Include the Date parameter in the report. With it, the destination table is partitioned by the date column and Renta loads data incrementally. It also enables the Overwrite Period setting, which appears below the date range once Date is selected. Without it, Renta reloads the whole date range on every run.

The Reporting API does not support every dimension and metric combination. For example, publisher content dimensions cannot be combined with standard session metrics. Renta validates the selected parameters against the API when you create the pipeline: if the combination is not supported, you get a configuration error. Remove the incompatible parameters and try again.

Table name and date range

Name the pipeline and set the historical period to load.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.
Date start.
The first date of the extraction period.
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.

Yandex Metrica keeps updating session data for some time after the visit: about 99% of sessions are finalized within 3 days. Set the overwrite period to at least Last 3 days to capture the late updates.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

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

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

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

Pipelines list with the new Yandex Metrica integration

How the export works

Renta builds the report from the Reporting API day by day.

Renta determines the export window: the full date range on the first run, or the incremental window on scheduled runs.
For each day in the window, Renta requests the report with the maximum accuracy setting of the Reporting API and reads the response in pages of 10,000 rows. Requesting one day at a time keeps each sample small, so sampling rarely kicks in.
Renta reads the currency from the counter settings and requests revenue metrics in that currency.
The parsed rows are loaded into the destination table; each row carries the counter_id of the counter it came from.

Sync strategy

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

Strategy	Supported report types	Description
Incremental	Sessions and Pageviews reports that include the Date parameter	Each row carries its date, and the destination table is partitioned by the `date` column. On every run Renta requests the window from the last successful run minus the overwrite period to the end of the date range: the affected daily partitions are deleted and inserted again, and older partitions stay untouched.
Full reload	Sessions and Pageviews reports without the Date parameter	The table has no date column to partition by, so Renta requests the report for the whole configured date range and replaces the dataset on every run.

Changing the selected parameters updates the table schema, so the next run after the change reloads the entire date range.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.