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.

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.

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

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.

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

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

Table name

Name the pipeline and the destination table.

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.

Date range

Set the historical period to load.

1. Date start.
   The first date of the extraction period.
2. 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.

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 the Date dimension.