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.

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.

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

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

1. 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.
2. Metrics.
   The numeric columns. Select at least one metric: a report without metrics has nothing to count and AppMetrica rejects it.

Unselect All clears the picker, and the Selected tab shows the current choice.

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.

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

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.

Sync strategy

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