UTM tracking in Yandex Metrica
Yandex Metrica is Yandex's free web analytics platform, widely used for Russian-language and regional sites. It reads standard UTM parameters from the landing URL to attribute traffic in its source reports, and ties natively into Yandex Direct, so UTM tagging is how non-Yandex sources stay attributed alongside Direct.
Standard UTM in Metrica reports
Yandex Metrica recognizes the standard UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) from the landing URL and surfaces them in its traffic-source and UTM reports. For sources outside the Yandex ecosystem, these tags are how the channel is attributed.
Because attribution derives from the URL, the tags must be present on the landing pageview the Metrica counter records.
- Standard UTM parameters recognized in source reports
- Used for non-Yandex sources attribution
- Derived from the landing URL pageview
Interaction with Yandex Direct
Yandex Direct links natively to Metrica, so Direct clicks can be attributed through that integration as well as via UTM. Keep your Direct UTM convention consistent so the two views reconcile rather than double-count.
For every other channel — email, partners, regional networks — apply clean lowercase UTM so Metrica groups them correctly next to Direct.
How it appears in analytics and logs
A campaign appearing in Yandex Metrica's UTM/source reports confirms the landing URL carried tags; Direct clicks may appear via native linking even without manual UTM, so reconcile the two.
Diagnostic use case
Attribute non-Yandex campaigns in a Yandex Metrica deployment using standard UTM parameters, while Yandex Direct integrates natively for its own clicks.
What WebmasterID can help detect
WebmasterID records the same UTM-tagged landing hit as a campaign touch server-side, giving a source signal independent of the Metrica tag for cross-checking regional campaigns.
Common mistakes
- Assuming Metrica auto-attributes non-Yandex sources without UTM tags.
- Letting Direct's native linking and manual UTM disagree and double-count.
- Inconsistent casing splitting one campaign across Metrica rows.
Privacy and accuracy notes
Yandex Metrica UTM values describe the campaign, not the person. Region remains a coarse edge estimate, and WebmasterID records the campaign touch without raw IP, exact location, or a visitor identity.
Related pages
- Yandex Direct UTM tracking
Yandex Direct is Yandex's advertising platform for search and display across the Russian-language web. To attribute its clicks in third-party analytics, add UTM parameters to your landing-page URLs and let Yandex Direct substitute its dynamic macros (such as the campaign and keyword placeholders) at click time. Yandex documents the available macros for building tracking URLs.
- UTM tracking in Matomo
Matomo supports campaign tracking through its own mtm_ parameters and can also be configured to read the standard utm_ parameters. The mtm_campaign and mtm_keyword tags map to Matomo's Campaigns reports, while utm_ values can be mapped via Matomo's campaign parameter settings. This page covers how Matomo consumes both schemes and where the data surfaces.
- UTM for regional ad platforms
Western analytics defaults recognize Google, Bing, and Meta, but treat regional giants such as Yandex, Naver, Kakao, Baidu, VK, and LINE as unknown referrals or direct. This page is a cross-cutting guide to applying consistent UTM tagging across regional ad platforms so each appears as its own channel, with macros where the platform supports them.
- Privacy-first analytics
Cross-check regional campaign attribution server-side.
Sources and verification notes
- Yandex Metrica Help — UTM tagsDocuments Yandex Metrica reading UTM parameters for source attribution.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.