Why can't I set Date end to Today?

The Logs API provides data only for fully completed days: the end of the requested period must be earlier than the current date. Set **Date end** to **Yesterday**. With this setting every run picks up the most recent completed day.

How is this source different from the Yandex Metrica source?

The Yandex Metrica source exports aggregated reports built from dimensions and metrics through the Reporting API. The Yandex Metrica Logs API source exports raw, non-aggregated data: each row in the destination table is a single session or a single event. Use the Logs API source when you need to build custom reports, attribution models, or join Metrica data with other sources at the user level.

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.

Does the export consume the counter's Logs API quota?

Only while a run is in progress. Yandex limits the total size of prepared logs to 10 GB per counter, so after downloading the data Renta deletes the prepared log request from the counter. Prepared logs do not accumulate between runs.

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.

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 Logs API source

Follow these steps to add Yandex Metrica Logs API 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 Logs API card.

Yandex Metrica Logs API card in the Analytics category of the Renta catalog

Authorize connectionStep 2

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

Authorize Yandex Metrica Logs API 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 Logs API 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 Logs API source

Create a pipeline

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

Create a Yandex Metrica Logs API pipeline

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

Select Yandex Metrica Logs API as the sourceStep 1

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

Select a source step with Yandex Metrica Logs API under Already connected

Select your Yandex Metrica Logs API connectionStep 2

Choose the Yandex Metrica Logs API 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 Logs API 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.
Report Types.
Choose the type of raw data to export.

Report type	Description
Visits	One row per session. Fields cover session identifiers, date and time, entrance and exit pages, traffic sources and UTM tags, Yandex Direct click data, device, browser, and geography attributes, goals, e-commerce purchases and products, and offline calls.
Hits	One row per event (page view). Fields cover the page URL and title, referer, UTM tags, device, browser, and screen attributes, geography, and flags such as link clicks, file downloads, and page view markers.

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.

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.

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

The Logs API provides data only for fully completed days, so the end of the period must be earlier than the current date. With Date end set to Today, pipeline creation fails with a validation error.

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.

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 Logs API integration

How the export works

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

Renta creates a log request on the counter for the export window and the selected fields.
Yandex prepares the log asynchronously. Renta waits for the request to be processed, checking its status for up to 60 minutes.
Renta downloads all parts of the prepared log and loads them into the destination.
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.

Strategy	Supported report types	Description
Incremental	Visits and Hits 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 a new log for 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	Visits and Hits reports without the Date parameter	The table has no date column to partition by, so Renta requests a log 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.