How Yandex Metrica works with tags
Yandex Metrica tracks all clicks on links with a tag. For example, this can be a direct click on a link saved in a browser or a link included in an email. Yandex Metrica can process the following types of tags:
Tag label |
Note |
Standard reports are created for tags. Data for the The Ad systems, Social networks, Messengers, and Recommendation systems reports are also generated from UTM tags. |
|
|
The tag is added by Yandex Direct. Example: Data about ad click-throughs is available in the “Yandex.Direct” reports group: In these reports, statistics only reflect registered clicks that weren't filtered out by the anti-fraud system. |
|
The tag is set by Yandex Market. For data about traffic from Yandex Market, see the Ad systems report. Example: |
|
The tag is used to identify keywords from Yandex Search. Example: You can view the queries in the Keywords report. |
|
Used for tracking Google Ads. To determine sources with the tag |
|
Used for tracking QR code click-throughs. See click-through data in the Sources, summary report. Example: |
|
The tag is set by Yandex PromoPages. For data about traffic from Yandex PromoPages, see the Ad systems report. Example: |
Yandex Metrica gets tag information from the first pageview in a user's session. If there isn’t a tag in the first pageview, it isn’t detected for the entire session.
Parameters of tags used for determining the source:
Ad systems |
Mailing lists |
Social networks and websites |
Search engines, messengers |
Recommendation systems |
|
|
|
|
|
Note
Tag content is recognized correctly if the site uses UTF-8 encoding.
How to correctly create a tag
The first parameter is always added after a “?”, while all others are added after a “&”. Tags also should not contain superfluous characters (for example, %2B).
Parameter |
Description |
Note |
|
Traffic source |
The tag is required to track incoming traffic from social media and ad platforms (except for Yandex Direct). |
|
Traffic channel |
The tag is used to track incoming traffic from QR codes, social media, messengers, email newsletters, and recommendation systems. If the value is |
|
Campaign name |
— |
|
Campaign content |
— |
|
Keyword |
— |
utm_source values for correctly detecting the source
Ad systems
adfox
— for AdFoxadmitad
— for Admitadadnews
— for AdNewsadnous
— for ADNOUSadriver
— for AdRiveradvcake
— for ADV.Cakeadvmaker
— for AdvMaker.ruaport (aport.ru)
— for AportAvitoPromo
— for Avito Promobegun
— for Begunbing
— for Bing AdsB2BContext
— for B2BContextcity_ads
— for CityAds Mediacriteo
— for Criteodirectadvert (directadvert.ru)
— for Direct/ADVERTdrivenetwork
— for DriveNetworkepn, epnbz
— for E.PNfacebook (fb, facebook.com, fb.com)
— for Facebook*;flocktory
— for Flocktorygdeslon, gdeslon_cpa
— for Gde Slon?giraffio
— for giraffe.io (AppCity)google (adwords, adsense)
— for Googleinstagram
— for Instagram*kavanga
— for Kavangaladycenter
— Ladycenterlink
— for LinkRUmagna
— for Magna Contextmarketgid
— for MarketGidmedialand
— for Medialandmerchant
— for Google Merchantmoimir
— for Moi mir Mail.runnn (nnn.ru)
— for NNN (National News Network)odnoklassniki
— for Odnoklassnikiozon
— for Ozonperfluence
— for Perfluenceprice (price.ru, priceru, price-gmc)
— for Price.ruprre
— for PRRE.RUrtbhouse
— for RTB Housemytarget (targetmailru)
— for myTarget (Target Mail.ru)taboola
— for Taboolatiktok
— for TikToktorg.mail.ru
— for Mail.ru Markettrorer (rorer)
— for RORERTtarget
— for tTargetvideonow
— for Videonow.ruvkontakte (vk, vk.com)
— for VKvk_ads, vkads, vk-ads, vkr
— for VK Adswhisla
— for Whislayoutube
— for YouTube
Social networks
vk
,vkontakte
,vk.com
— for VKfacebook
,fb
, orfacebook.com
— for Facebook*twitter
ortwitter.com
— for Twitterok
,odnoklassniki
,ok.ru
, orodnoklassniki.ru
— for Odnoklassnikilivejournal
— for Live Journalplus.google.com
orgoogleplus
— for Google+my.mail.ru
— for Mail.ru My Worldlinkedin
orlinkedin.com
— for LinkedIndelicious
— for delicioustumblr
ortumblr.com
— for Tumblrinstagram
orinstagram.com
— for Instagram*pinterest.com
— for Pinterestreddit
— for Redditstumbleupon
— for StumbleUpon
Messengers
skype
— for Skypetelegram
— for Telegramviber
— for Viberwechat
— for WeChatwhatsapp
— for WhatsApp
Recommendation systems
mirtesen.ru
— for MirTesenrambler
— for Rambler
Search engines
yandex
— for Yandex searchgoogle
— for Google searchgo.mail.ru
— for Mail.ru search
If you specify a value in the UTM tag for utm_source
that isn't listed above, Yandex.Metrica will assign the sessions to the source Other search engine: determined by tags.
utm_medium values for correctly detecting the source
Ad systems
banner
cpa
cpc
cpm
cpp
cpv
display
paidsearch
ppc
Social networks
social
social-network
social-media
sm
social network
social media
Recommendation systems
rec
Search engines
organic
Other sources
email
ore-mail
— for incoming traffic from email newsletters.qr
orqrcode
— for traffic via QR codes.messenger
— for incoming traffic from instant messengers.
Note
If the utm_source
value is featured in the recommended list and the utm_medium
value isn't, Yandex Metrica detects the traffic source by utm_source
. This applies to traffic sources where the utm_medium
tag is optional.
If you don’t use all the parameters in the tag, pay attention to their sequence:
https://example.com/?utm_source=link&utm_medium=cpc&utm_campaign=new
Use the utm_referrer
parameter to allow Yandex Metrica to correctly detect the source of a click-through when there is a JavaScript redirect, or when users navigate to your site with the HTTP protocol from a site that is only available over HTTPS (more information about switching to HTTPS).
For the value, enter the address of the site that the click-through came from. Example:
https://example.com/?utm_referrer=example-source.com
where
example.com
is your site.example-source.com
is the referral source.
If you specify the full address of a site with the HTTP or HTTPS schema as the value, then you need to encode this URL. For example, you want to specify the address https://example.com
. The encoded address will look like this: https%3A%2F%2Fexample.com
.
When listing the Openstat tag parameters, use “;” to separate them.
https://example.com/?_openstat=openstat_service;openstat_campaign;openstat_ad;openstat_source
where
openstat_service
— traffic sourceopenstat_campaign
— campaign IDopenstat_ad
— ad IDopenstat_source
— site ID
Example:
https://example.com/?_openstat=adfox;moscow;discount;top
openstat_service
values for correctly detecting the source
Use the following values to track incoming traffic from ad platforms:
adfox
— for AdFoxadmitad
— for Admitadadnews
— for AdNewsadnous
— for ADNOUSadriver
— for AdRiveradvcake
— for ADV.Cakeadvmaker
— for AdvMaker.ruaport (aport.ru)
— for AportAvitoPromo
— for Avito Promobegun
— for Begunbing
— for Bing AdsB2BContext
— for B2BContextcity_ads
— for CityAds Mediacriteo
— for Criteodirectadvert (directadvert.ru)
— for Direct/ADVERTdrivenetwork
— for DriveNetworkepn, epnbz
— for E.PNfacebook (fb, facebook.com, fb.com)
— for Facebook*flocktory
— for Flocktorygdeslon, gdeslon_cpa
— for Gde Slon?giraffio
— for giraffe.io (AppCity)google (adwords, adsense)
— for Googleinstagram
— for Instagram*kavanga
— for Kavangaladycenter
— Ladycenterlink
— for LinkRUmagna
— for Magna Contextmarketgid
— for MarketGidmedialand
— for Medialandmerchant
— for Google Merchantmoimir
— for Moi mir Mail.runnn (nnn.ru)
— for NNN (National News Network)odnoklassniki
— for Odnoklassnikiozon
— for Ozonperfluence
— for Perfluenceprice (price.ru, priceru, price-gmc)
— for Price.ruprre
— for PRRE.RUrtbhouse
— for RTB Housemytarget (targetmailru)
— for myTarget (Target Mail.ru)taboola
— for Taboolatiktok
— for TikToktorg.mail.ru
— for Mail.ru Markettrorer (rorer)
— for RORERTtarget
— for tTargetvideonow
— for Videonow.ruvkontakte (vk, vk.com)
— for VKvk_ads, vkads, vk-ads, vkr
— for VK Adswhisla
— for Whislayoutube
— for YouTube
Use email
or e-mail
to track incoming traffic from email newsletters. This value should be placed in the openstat_service
or openstat_source
parameters.
Example:
https://example.com/?from=transition-source
To track incoming traffic from email newsletters, use the email
or e-mail
values.
Display tags in reports
Tag data is sorted according to how the groups are positioned on the report page, and shown in two ways:
Learn more
- How Yandex Metrica detects the traffic source
- Learn more about the Tags report group
- How to solve the problem with UTM tags
Questions and answers
Are values passed in UTM tags case-sensitive?
- Yes. Yandex Metrica distinguishes the case that the UTM tag value is specified in. For example,
utm_source=Vkontakte
is not the same asutm_source=vkontakte
. This affects displaying information in Yandex Metrica reports and uploading and deleting data on ad campaign expenses. To check the tag values already used in Yandex Metrica, see the UTM Tags report.
Useful links |
Online training |
Banned in Russia.
A URL parameter processed by Yandex Metrica using a special algorithm. It’s not displayed in the “URL parameters” report. Instead, it’s included in special reports. This lets you create more intuitive and thorough analytic segments.