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.

Connect Yandex Metrica source

Go to the CatalogStep 1

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

Authorize connectionStep 2

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

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.

Name the connection and saveStep 4

Finish the setup:

1. Source name.
   Specify a name for this data source. This is used exclusively in the Renta interface.
2. 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.

Source createdStep 5

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

Create a Yandex Metrica pipeline

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

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 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 the destination connectionStep 4

Choose the destination connection you want to load data into and click Next 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.

1. 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.
2. Report Types.
   Choose the type of statistics to export.

Parameters

Select the dimensions, metrics, and goals to include in the destination table. What you pick here is the schema of your dataset.

The Dimensions list also carries date fields that Renta works out from the session or pageview date. Pick one and Renta puts the date into the report as well.

Fields that depend on the attribution model, such as traffic sources, UTM tags and Yandex Direct click data, appear once per model. Take the ones for the model you report on.

Column names in the destination table repeat the API names without the ym:s: and ym:pv: prefixes, so ym:s:visits arrives as visits. Renta exports revenue metrics in the currency of the counter and drops the currency code from the name. Every row also gets a counter_id column.

Not every set of parameters is supported by the Reporting API. See Parameter compatibility before assembling a wide report.

Include undefined values

Yandex Metrica drops a session from the report when any of the selected parameters has no value for it. This setting controls whether those sessions still reach your table.

With Yes, the default, such sessions arrive with an empty value in that column. With No, Yandex Metrica excludes them from the report.

The setting matters more the wider the report is, because a session reaches the table only when every selected parameter is filled for it. A counter with no search traffic has no value for firstSearchEngine in any session, so with No a report containing that parameter comes back empty.

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. 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.

Parameter compatibility

The Reporting API does not accept every combination of dimensions and metrics, and an unsupported set does not always announce itself.

Some sets the API rejects outright. Renta validates the selected parameters against the API when you create the pipeline, so you see a configuration error straight away and the pipeline is not created. Publisher content dimensions behave this way: Article Title, Article Author, and Article Published Date are rejected alongside standard session metrics such as visits. Remove the parameters named in the error and try again.

The rest the API accepts, then returns nothing for them. Validation passes, the pipeline is created, and every run afterwards finishes successfully without a single row. firstSearchPhrase together with Date Time behaves this way: the pair returns nothing regardless of the counter or the date range.

Search phrases combine with fewer parameters than anything else in this source. When you need them, keep the report down to the search phrase, the search engine, Date, and the metrics.

Sync strategy

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