Its own export, its own format
The VK account exports separately and in its own shape, so reconciling it with Meta and Google only happens by hand — and only when somebody finds the time.
Valkiria has no native VK Ads connection: account data arrives through an external data connector, a CSV export or manual entry. From there VK spend is measured with the same metrics as every other platform, and nothing is written back to the VK account.
The VK account exports separately and in its own shape, so reconciling it with Meta and Google only happens by hand — and only when somebody finds the time.
The spreadsheet is built on Monday and the budget moves on Thursday: VK's share of the result is judged on numbers that no longer hold.
VK performance sits in a file on a contractor's or a single manager's machine, so the channel's whole history disappears when they do.
On the integrations page you choose the route for VK: an external data connector, a CSV export from VK Ads, or manual metric entry.
Date, campaign, impressions, clicks, CTR, CPC and spend land in the project database and stay as channel history, not as a one-off spreadsheet.
VK lines up next to Meta, Google and TikTok on identical metrics. Not one change is sent back to the VK account in the process.
The native VK Ads connection is switched off in Valkiria and the product says so: you pick the data route explicitly, with no fake connect button.
VK Ads spend can come in through Windsor.ai, Funnel, Airbyte or RapidAPI — whichever service you already pay for.
With no connector in place, a VK Ads export is uploaded as a file and mapped onto the same fields as every other platform's data.
Small campaigns can be kept by hand: the numbers are stored in the project and appear in shared reports next to synced data.
Impressions, clicks, CTR, CPC and spend are normalised, so VK's share of the result is visible without a separate spreadsheet.
Valkiria neither creates nor changes VK campaigns: in this product the channel exists purely as a reporting data source.
No. The native VK Ads connection is disabled in Valkiria and the authorisation path deliberately does not work. Channel data is loaded through an external data connector, a CSV export from VK Ads, or manual metric entry instead.
Through one of the external connectors — Windsor.ai, Funnel, Airbyte or RapidAPI — or as a CSV file from the account. Loaded rows are mapped onto the shared fields: date, campaign, impressions, clicks, CTR, CPC and spend.
No, and this is not a settings question: there is no write path to VK in the product at all. Everything Valkiria does with this channel is read the loaded data and show it next to your other platforms.
Start with CSV: an export from VK Ads is uploaded as a file and then behaves exactly like synced data. Smaller campaigns can be entered by hand so the channel does not drop out of the shared report.
It will only be switched on once VK Ads API access and safe handling of the account are proven in review. We are not promising a date: until that exists, it is more honest to show VK as a data source than as a managed account.
All it takes is choosing a data route — connector, CSV or manual entry. Nothing inside the VK account changes.