How is this source different from the AppMetrica Logs API source?

This source exports aggregated reports: one row per combination of the dimensions you selected, with counts and sums in the metric columns. The AppMetrica Logs API source exports raw rows, where each row is a single event or a single installation. Use this source for ready-made statistics, and the Logs API source when you need event-level data to build your own aggregations.

Can one pipeline export several applications?

No. The **Counters** list accepts one application, and the exported rows carry no application identifier. To export several applications, create a separate pipeline for each one and give each pipeline its own table name.

Which time zone are the dates in?

AppMetrica records events in the time zone configured for the application, under **Settings** > **Main** > **Time zone UTC** in the AppMetrica interface. Renta does not convert dates, so the values in the destination table follow that setting.

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

AppMetrica attributes an install to the date the app was first opened, but it keeps matching that install to a click for 10 days after the click, and up to 30 days depending on the tracker settings. Campaign and publisher figures for past dates therefore keep resolving. Events sent above the daily limit are also buffered and written later. Set the **Overwrite period** to cover the days you expect to change.

Does AppMetrica sample the data?

AppMetrica can apply sampling on its side when a report covers a large number of users. The sample is decided by AppMetrica and is not exposed as a setting in Renta.

AppMetrica

AppMetrica splits app statistics into in-app activity and user acquisition through trackers. Renta exports either of them as an aggregated table: you pick one report type, then the dimensions and metrics that form its rows.

Authentication

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

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 AppMetrica source

Follow these steps to add AppMetrica 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 AppMetrica card.

The AppMetrica Logs API card next to it is a different source. It exports raw event and installation rows instead of aggregated reports.

AppMetrica card in the Analytics category of the Renta source catalog

Authorize connectionStep 2

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

Authorize connection page for a new AppMetrica connection in Renta

Choose a Yandex accountStep 3

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

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

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 AppMetrica connection with the source name field and the access granted block

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 AppMetrica source in the Active status

Create an AppMetrica pipeline

Link your AppMetrica source to a destination and configure the pipeline.

Select AppMetrica as the sourceStep 1

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

Select a source step with AppMetrica under Already connected

Select your AppMetrica connectionStep 2

Choose the AppMetrica 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 AppMetrica data to export and how Renta loads it.

Report configuration

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

AppMetrica application and report type selection on the pipeline settings step

Counters Choose the application to export data from. The list contains the applications available to the connected Yandex account, shown by application name. One pipeline exports one application.

Report Types Choose the type of statistics to export. One pipeline exports one report type.

Report type	What it covers	Metrics
General events	In-app activity, grouped by attributes of the app and the device: app version, device type, operating system, screen resolution, and geography.	Users, Sessions, Devices
Custom events	The events you send from the app yourself, with the same app and device attributes plus the event label. The parameters you attach to an event are available as averages and sums.	Users, Sessions, Devices, Client Events, Average Parameters, Sum Parameters
Campaigns	Tracker clicks, grouped by campaign and publisher: how much traffic each acquisition source sent.	Clicks
Installs	Attributed installations, grouped by campaign and publisher: which acquisition sources the installs came from.	Install Devices

Parameters

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

Dimensions.
The attributes rows are grouped by. Each entry shows the label and the API name below it, so ym:i:campaign appears under Campaign.
Metrics.
The numeric columns. Select at least one metric: a report without metrics has nothing to count and AppMetrica rejects it.

Use the search field to find a parameter by name, or click Unselect All to clear the picker. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter with the minus button.

In the destination table, column names repeat the API names of the parameters without the ym:ge:, ym:ce:, ym:c:, and ym:i: prefixes: ym:ge:appVersion becomes appVersion. Renta also copies the description of each parameter into the description of the corresponding column.

Date parameters

The Dimensions tab of the General events and Custom events reports contains date fields: Date and Today, plus calendar fields such as Year, Quarter, Month, Week, and Day of week. Renta derives the calendar fields from the event date, and adds the date to the report automatically when you select one of them.

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 a date parameter is selected. Without it, Renta reloads the whole date range on every run.

The Campaigns and Installs reports have no date parameters at all. Their tables get no date column, which means every run reloads the full date range. Use them for the totals of the selected period, and take the daily breakdown of acquisition from the General events report.

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.

AppMetrica limits a Yandex account to 5,000 report requests per day, counted across every pipeline built on that account. If you load years of history for several pipelines at once, AppMetrica answers with a Too Many Requests error. Load long history in parts, or wait until the quota resets.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run. The setting appears once a date parameter is selected in Parameters.

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.

AppMetrica keeps matching installs to clicks for 10 days after the click, and up to 30 days depending on the tracker settings, so acquisition figures for past dates keep changing. Set the overwrite period to cover the attribution window you use.

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.

AppMetrica 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 AppMetrica integration in the Completed status

Sync strategy

The synchronization strategy depends on whether the report includes a date parameter.

Strategy	Supported report types	Description
Incremental	General events, Custom events (with the Date or Today parameter selected)	Each row carries its date, and the destination table is partitioned by that 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	Campaigns, Installs, and also General events and Custom events when no date parameter is selected	The report returns no date column to partition by, so Renta requests 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.