Transfer of costs
With Yandex Metrica, you can track the effectiveness of any traffic sources on your tag. To do this, you can transfer expense information to Yandex Metrica for all traffic sources or for individual advertising systems. Data can be transferred:
- Using Yandex Metrica integrations for uploading advertising expenses.
- A special-format CSV file. Uploading is possible in the Yandex Metrica web interface and via API.
Transfer of costs by traffic source
If a traffic source cannot be tagged with UTM tags or you do not need detailed advertising expenses down to individual campaigns, ads, or placement types, you can still send expenses for such source. To transfer expenses, specify the Source
(TrafficSource
) and Traffic Source (detailed)
(TrafficSourceDetail
) parameters in the expense upload. The list of values for these parameters is specified in the table.
All Yandex Metrica integrations for uploading advertising expenses support automatic traffic source transfer.
To see which metrics are calculated based on the uploaded data and what you can do with them, go to the Sources, costs and ROI report.
Yandex Metrica integrations for uploading advertising expenses
Advertising system |
How to pass data |
Note |
Yandex Direct |
Data is transmitted automatically. |
Alert If you upload expenses manually, they will be duplicated with those transferred automatically, and the report will be incorrect. |
Google Ads |
Set up integration in Yandex Metrica. |
The source of expenses will be indicated as Ad Clicks — Google Ads |
Facebook Ads |
Set up integration in Yandex Metrica. |
The source of expenses will be indicated as Ad Clicks — Facebook. If |
Transfer of costs with a special-format CSV file
To transfer ad campaign data to Yandex Metrica, create a CSV file that fits the expense transfer format for Metrica.
Sample of file for uploading data
Fields for transmitting data
Field name |
Required |
Description |
Example |
|
Yes |
Period that data is transmitted for. It can be a day or an interval of time. In the Unix Time Stamp format according to the ISO 8601 standard (YYYY-MM-DD). To specify a date range, use /. |
2020-02-18 2020-01-18/2020-02-18 |
|
Yes |
The amount spent on advertising without VAT. |
50,000 |
|
No |
Three-letter ISO 4217 currency code. If the currency isn't specified, Yandex Metrica uses the currency specified in the tag settings to generate reports. |
RUB |
|
Yes* |
First-level traffic source. Acceptable values are given in the table. |
ad |
|
No |
Second-level traffic source. Acceptable values are given in the table. |
vk |
|
Yes* |
The value of the UTM tag that is specified in the URL of the link in the ad. Note the case of the characters in the tag value. |
vk |
|
No |
new |
|
|
No |
cpc |
|
|
No |
shirt-blue |
|
|
No |
shirt |
|
|
No |
Number of clicks on ads. |
100 |
* The UTMSource
field is required if the TrafficSource
field is not specified.
Available TrafficSource and TrafficSourceDetail values
TrafficSource |
TrafficSourceDetail |
|
Internal traffic |
|
— |
Direct traffic |
|
— |
Link traffic |
|
Specify the domain in |
Search engine traffic |
|
|
Ad traffic |
|
|
Cached page traffic |
|
— |
Undefined |
|
— |
Mailing traffic |
|
— |
Traffic from social networks |
|
|
Messenger traffic |
|
|
QR code traffic |
|
— |
Recommendation system traffic |
|
Search engine traffic
Name |
ID |
Other search engine: Identified by tags |
|
Yandex |
|
|
|
|
|
blekko |
|
Rx24 |
|
Gigabase |
|
AOL |
|
Zen News |
|
|
|
MyStart by IncrediMail.com |
|
Winamp Search |
|
Search on NUR.KZ |
|
Topsy |
|
|
|
|
|
|
|
Webalta |
|
Magna |
|
Lycos |
|
|
|
My Web Search |
|
|
|
|
|
Conduit |
|
Babylon Search |
|
Alexa Web Search |
|
|
|
|
|
|
|
|
|
Alhea |
|
AltaVista |
|
|
|
Aport |
|
|
|
|
|
|
|
Baidu |
|
|
|
|
|
Bing |
|
Coc Coc |
|
|
|
|
|
DAEMON search |
|
|
|
|
|
DuckDuckGo |
|
Ecosia |
|
|
|
|
|
Gde.ru |
|
|
|
|
|
GoGo |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Search on ICQ.com |
|
|
|
|
|
|
|
|
|
k9safesearch |
|
Search on KM.RU |
|
|
|
Liveinternet |
|
Live Search |
|
|
|
|
|
|
|
MSN |
|
|
|
|
|
|
|
|
|
Nigma |
|
|
|
|
|
|
|
Search on QIP.ru |
|
Quintura |
|
Qwant |
|
Rambler |
|
|
|
|
|
|
|
|
|
|
|
|
|
Seznam |
|
Skydns |
|
|
|
|
|
|
|
Sogou |
|
|
|
Sputnik |
|
Startpagina |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Wikia Search |
|
wow |
|
|
|
Yaani |
|
Yahoo! |
|
|
|
|
|
Zapmeta |
|
Ad traffic
Name |
ID |
Google Ads |
|
Begun |
|
Krasnoyarsk.biz |
|
Link.ru |
|
MadBanner |
|
Magna-context |
|
RORER |
|
Stavka.ru |
|
WebAlta |
|
Yandex Market |
|
|
|
Kavango |
|
|
|
|
|
AdRiver |
|
AdFox |
|
MediaTarget |
|
DirectPoint |
|
TBN |
|
LitBN |
|
SoftBN |
|
AdLand |
|
Linkad |
|
Ukrainian Banner Network |
|
Banner Bank |
|
BannerHost |
|
List Banner Exchange |
|
Pravda Banner Network |
|
Land Banner Network |
|
IBN |
|
BigBN |
|
Display advertising |
|
|
|
Tovary@Mail.Ru |
|
VK |
|
|
|
Odnoklassniki (OK) |
|
Moi Mir |
|
B2BContext |
|
B2BCAdNewsontext |
|
People Group |
|
|
|
Adlabs Media Network |
|
Admitad |
|
Medialand |
|
MyTarget |
|
Aport |
|
|
|
MarketGid |
|
adPremium |
|
ExoClick |
|
LadyCenter |
|
POST RMBN |
|
Direct/ADVERT |
|
Recreativ |
|
AdWolf |
|
Adonweb |
|
AdBlender |
|
AdvertLink |
|
SharedAdDomain |
|
Adnxs |
|
Targetix |
|
adhood |
|
Criteo |
|
Google Merchant |
|
Avito Context |
|
Sociomantic |
|
Ttarget |
|
Yandex: Display |
|
Avito Promo |
|
Yandex Advertising Network: RTB blocks |
|
ADNOUS |
|
VigLink |
|
|
|
Rare.ru |
|
BingAds |
|
Whisla |
|
Taboola |
|
Other advertising: identified by tags |
|
YouTube |
|
|
|
DriveNetwork |
|
NNN |
|
Nadavi |
|
|
|
coccoc |
|
Relap |
|
TikTok |
|
Yandex PromoPages |
|
RTB House |
|
Yandex: Direct |
|
VK Ads |
|
Ozon |
|
Traffic from social networks
Name |
ID |
VK |
|
|
|
|
|
Odnoklassniki (OK) |
|
Liveinternet |
|
LiveJournal |
|
Leprosorium |
|
|
|
Google+ |
|
Moi Mir@Mail.ru |
|
ORKUT |
|
Ya.ru |
|
Moi Krug |
|
Vkrugudruzei.ru |
|
Linked in |
|
juick |
|
|
|
|
|
FriendFeed |
|
|
|
|
|
Privet.ru |
|
|
|
|
|
mixi |
|
|
|
|
|
|
|
|
|
tumblr.com |
|
|
|
|
|
|
|
|
|
Postila.ru |
|
Fotostrana.ru |
|
|
|
|
|
|
|
StumbleUpon |
|
Other social media: Identified by tags |
|
YouTube |
|
Messenger traffic
Name |
ID |
Other messenger: Identified by tags |
|
Telegram |
|
|
|
Viber |
|
Skype |
|
|
|
Yandex Messenger |
|
|
|
VK |
|
Recommendation system traffic
Name |
ID |
Other recommendation system: Identified by tags |
|
Zen |
|
Google Discover |
|
Opera Personal News |
|
Sony News Suite |
|
|
|
Pulse |
|
MirTesen |
|
Toutiao |
|
Rambler |
|
Note
You can upload data for the last 360 days and no more than 30 days ahead.
You can send a CSV file with data:
-
In Yandex Metrica, go to Settings → Upload data.
-
In the Advertising expenses section, click Upload.
-
Upload the prepared file.
-
In the window that appears, specify the following:
-
TrafficSource
andTrafficSourceDetail
values. -
Value of the
UTMSource
tag (the ad system that the file was uploaded from).
Make sure that the case in which the UTM tag value is specified matches the case in the ad URL. -
column in the file corresponds to the field
Data
. -
column in the file corresponds to the field
Expenses
.
Select the type of amount separator that is used in the file uploaded in Step 1 — a comma or dot. -
column in the file corresponds to the field
Clicks
. -
the currency in which the expenses are specified.
If the currency is not specified, Yandex Metrica uses the currency from the tag settings for report generation. -
other UTM tags and their values from the list.
You can enter a single value for all tags. For example, for theUTMMedium
tag you can specify the valuecpc
.
-
-
Click Upload data.
If you upload a file with data for the same period, the new file will replace the previously uploaded one.
If a time period is specified in the file, Yandex Metrica will evenly distribute the numerical values (for example, expense, number of clicks, and so on) in it for displaying in the report.
Useful links |
Online training |
Banned in Russia.
* The UTMSource
field is required if the TrafficSource
field is not specified.