Does Yandex Metrica Require Cookie Consent?
Last updated: September 9, 2026
A standard Yandex Metrica counter, installed per the usual instructions, starts working the moment the page loads — it sets its own cookies (e.g. _ym_uid, _ym_d) and collects IP address, user agent, and on-page behavior (session recordings, click/scroll maps) before the visitor has interacted with the page at all. That's exactly the situation Russia's 152-FZ targets: processing data that can identify a person before consent was ever given.
Is Metrica's data "personal data"
Per Roskomnadzor guidance, cookie identifiers and IP addresses count as personal data because, combined with other signals, they can identify a specific visitor. It doesn't matter that Metrica itself doesn't store a name or phone number — legal status is determined by whether identification is possible, not by how "personal" the individual fields look.
Removing analytics isn't the answer
You don't need to drop analytics — the law doesn't ban Yandex Metrica, it requires getting consent before the counter starts collecting data, and letting visitors opt out. The problem is purely technical: the standard Metrica snippet has no built-in way to wait for consent — it has to be initialized manually at the right moment.
How this works in practice
- The cookie banner has to render before the counter loads at all — not alongside it, not after;
- The counter has to be initialized programmatically only after the visitor picks "Statistics" — not embedded as a static tag in
<head>; - If consent is declined or withdrawn, the counter shouldn't fire again on later visits.
Cookiestack handles this without manual wiring: enter the Counter ID in your domain settings and the widget injects and initializes Metrica itself, only after "Statistics" consent. See the Yandex Metrica integration guide for details.
Not just Metrica
The same logic applies to Google Analytics/Consent Mode v2, Yandex Direct and VK Ads pixels, click-map tools, and any other tracker — if the snippet fires unconditionally on page load, consent is effectively absent even if a banner is visually present on the site.
This article is for informational purposes only and is not legal advice. Consult a qualified data protection lawyer for your specific situation.