Can one pipeline export several ad accounts?

No. Each pipeline exports statistics for one VK Ads account. Create a separate pipeline for every account you need. All of them can share the same VK Ads connection.

I connected an agency account. Which ad accounts can I select?

For an agency connection, the **Ad accounts** list shows the client accounts of the agency. Pick the client whose statistics you want to export and create a separate pipeline for each one.

Where do the UTM columns take their values from?

From the UTM parameters configured in the ad group settings in VK Ads. Renta resolves dynamic placeholders, so the destination table contains final values with real campaign and ad identifiers.

VK Ads

VK Ads reports statistics at the level of individual ads: one row per ad per day. You assemble the report yourself from dimensions and metrics: spend and clicks, post engagement events, video views, per-slide carousel statistics, viewability, and the UTM tags configured in the ad group settings.

Renta exports this report to your data warehouse and adds the attributes of the objects behind each row: campaign and ad group names, package id, and the moderation status of the ad.

Authentication

Renta uses OAuth to authenticate with VK Ads. You will be redirected to VK Ads to grant Renta limited access to your ad account.

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 VK Ads account settings at any time.

Connect VK Ads source

Follow these steps to add VK Ads 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 Advertising category and click the VK Ads card.

VK Ads card in the Advertising category of the Renta catalog

Authorize connectionStep 2

Click Log in to your VK Ads account. You will be redirected to VK Ads to grant access.

Authorize VK Ads connection page in Renta

Grant access in VK AdsStep 3

VK Ads shows the access request for the Renta application and asks which account to share. Keep your own account selected and click Разрешить доступ (Allow access). After that you are redirected back to Renta.

VK Ads access request page with the account selection and the Allow access button

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 VK Ads authorization later changes, click Re-authorize on this source. The connection refreshes in place and every pipeline built on it keeps running.

Set up your VK Ads 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.

Create a pipeline

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

Create a VK Ads pipeline

Link your VK Ads source to a destination and configure the pipeline.

Select VK Ads as the sourceStep 1

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

Select a source step with VK Ads under Already connected

Select your VK Ads connectionStep 2

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

Report configuration

Point the pipeline at the ad account you need.

VK Ads ad account and report type selection

Ad accounts.
Choose the VK Ads account to export data from. Each pipeline exports statistics for one account. For an agency connection, the list shows the client accounts of the agency.
Report Types.
VK Ads exposes one report type, Custom report: an ad-level statistics report that you assemble from dimensions and metrics.

Parameters

Select the VK Ads fields to include in the destination table. The parameters you choose here define the table schema.

VK Ads dimensions selection with the Select All button

On the Dimensions tab, check the fields that describe the ad behind each row: Date, campaign name and id, ad group name and id, package id, ad id and name, and Ad moderation status. Use the search field to find a parameter by name, or click Select All.

On the Metrics tab, check the figures to export: impressions, clicks, spend, goals and cost metrics, post engagement events, unique user reach and frequency, video views by watch depth, per-slide carousel clicks and shows, viewability, playable ad and offer events, and ROMI. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter.

The report includes ads and ad groups in every status. Renta requests the statistics with conversion attribution.

The five UTM dimensions (utm_source, utm_medium, utm_campaign, utm_content, utm_term) return the values configured in the UTM settings of the ad group. Renta resolves the dynamic placeholders in these values, so the destination table contains final identifiers instead of the placeholder text.

Placeholder	Replaced with
`{ad_id}`	The id of the ad in the row.
`{campaign_id}`	The id of the campaign the ad belongs to.
`{campaign_name}`	The name of the campaign the ad belongs to.
`{client_id}`	The id of the exported ad account.

The UTM schema dimension returns the raw parameter string as it is set in VK Ads.

Include the Date dimension in the report. With it, each row in the destination table is one day, the table is partitioned by the date column, and Renta loads data incrementally. Without it, Renta reloads the whole date range on every run.

Table name

Name the pipeline and the destination table.

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 range

Set the historical period to load.

Date start.
The first date of the extraction period.
Date end.
The last date of the extraction period. Leave it as Today to keep collecting new data on every run.

VK Ads returns statistics one day at a time and enforces request quotas, so a wide historical range takes noticeably longer to load than a few days. Renta paces its requests to stay within the quotas.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run.

On each run, Renta re-fetches the report 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.

VK Ads can update statistics for recent days after they are first loaded, for example when conversions are attributed later. Set the overwrite period to several days to capture these 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 VK Ads integration

Sync strategy

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

Strategy	Supported report types	Description
Incremental	Custom report (with the Date dimension selected)	Each row is one day, and the destination table is partitioned by the `date` column. On every run Renta reloads the window from the last successful run minus the overwrite period to the end of the date range: those daily partitions are deleted and inserted again, and older partitions stay untouched.
Full reload	Custom report (without the Date dimension)	The table has no date column to partition by, so Renta requests the whole configured date range and replaces the dataset on every run.

Changing the selected dimensions or metrics 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.