A cookie banner is there so a site visitor can say yes or no, and Yandex Metrica and ad pixels start only after yes. Without a banner the counter either starts for everyone at once, or it gets removed badly and the report goes empty. You can set this up without a programmer in the Auralix builder: https://auralix.tech/en/tools/cookie-banner
Why a banner, if there is no cookie article
152-FZ has no separate article about cookies. That does not mean a banner is mandatory in Russia, and it does not mean it is unnecessary. This is not legal advice.
As amended on 26 July 2026, Article 3 calls personal data any information from which a person can be identified, directly or indirectly.[1] Metrica distinguishes browsers and records how a person moved around the site.[3] That trail can turn out to be personal data. Article 3 does not discuss the counter itself, and I will not add a conclusion it does not contain.
Article 6 says processing is allowed in the cases listed there. One of them is the person's consent to processing of their data.[2] The list does not end there. So "consent is in the law, therefore a banner is mandatory" is as loose a link as "there is no cookie article, so count everyone in silence." A lawyer draws the conclusion for your site. The question here is different: when the site turns on the thing that distinguishes browsers and feeds ads.
In this setup the banner is a switch. Analytics and ads after consent, not before it. They click yes, the counters start. They click no, they do not. Until there is a button, the site decides for the visitor, and it usually decides "we count."
On the page about warning visitors, Yandex qualifies its sample separately. Their banner text is only an example of how a notice can look. They do not take responsibility for legal compliance and recommend asking a lawyer.[4] The sample sentence, "This site collects visit statistics and visitor data," is not a legal conclusion.
If people from the EU visit you, GDPR applies to those visitors separately. Metrica's page about it is about the General Data Protection Regulation and about people in the European Economic Area, not about Russia.[5] A banner for a Russian site and Metrica's GDPR page are not the same thing, even if the buttons look similar from the outside.
What happens if there is no banner
The counter from the Metrica dashboard is usually pasted into the site and counts everyone who opened the page. Nobody asked the person. The visit is already in the report, there is no banner yet, and the numbers are already there. To the owner this looks like normal statistics. For the visitor there was no question.
I have also seen the other picture. The counter was removed, removed badly, and in the morning the chart sat at zero even though people were coming in. The first thought, to switch something off in the Metrica dashboard, leads the wrong way. An empty chart does not get fixed in the dashboard. Do not switch the counter off because the numbers dropped.
Without a banner the choice is false: either you count everyone in silence, or you count no one, because the counter no longer starts. A cookie banner for the site leaves a third path: you asked, and the report includes the people who said yes.
Yandex writes that without the visitor's consent the counter will not load.[4] People who refused will not appear on the chart. The chart will be lower than in the week when everyone was counted. That is the cost of asking, not a breakage, and not a reason to turn the counter off in the dashboard.
What can run before consent, and what after
Before the answer it is fine to show the banner itself and remember the choice. Without that memory the banner will appear again, including for someone who already clicked. In Yandex's example the logic is: no memory, show the banner; memory present, start the counter. One answer can be counted on all pages of the site.[4]
The same bucket holds what the site cannot work without. A login, so the person is not thrown out on every navigation. A cart, so the product does not disappear between product pages. That is not Metrica and not an ad pixel. The site remembers its buyer, the report is still quiet, and those are different jobs.
After yes you can turn on Metrica, Webvisor, meaning a recording of movement around the page, and Meta, VK, and TikTok pixels. A recording of movement is not "just how many people came in." Do not turn it on before consent. Ad pixels also leave their own trace in the browser, so they wait for yes, not for the page to open.
After no those counters do not start. A lower chart is expected. The week before the banner and the week after it cannot be read as one traffic series: before, a visit entered the report if the counter managed to start; now, only consent does. Do not switch the counter off in the Metrica dashboard. A switched-off counter will not bring refusals back and will not explain why everyone was counted before the banner.
The counter sends data about the page when it is actually running on the site.[6] Until it starts, there is little data. An empty chart after a bad removal, and a full chart when the counter runs for everyone at once, are solved by one move: ask the person and turn analytics on only after yes.
How to put the banner up without a programmer
Doing it by hand takes a long time, and the old counter from the dashboard easily stays on the site: the banner draws buttons, and visits are already being written on their own. The Auralix builder is there so you do not call a programmer: https://auralix.tech/en/tools/cookie-banner
The basic Accept / Decline banner is free, with Auralix branding. It installs in one line. The preview is live: you see it on a phone and on a computer before the banner is on the site. Metrica and other counters are tied to the banner. They start on consent, not from the site header on their own, while the person has not clicked yet.
This is a tool for the button, not the text of the law, and not a substitute for what a lawyer should read. The lawyer looks at the wording. The builder looks at whether yes turns Metrica on and no does not.
Yandex describes the same fork: warn the person and do not load the counter until there is consent.[4] For the owner of a small site the builder is shorter than assembling a banner from someone else's sample and then guessing why the chart is lying.
Put the banner up and check it in a clean window
Put the banner up, tie Metrica to it, and open the site in a clean browser window. Click nothing. Yandex usually shows data in the report 10–15 minutes after the event, sometimes later.[6] There should be no visit before the button. Click Accept and check again: the visit is there. In another clean window, where there is no choice yet, click Decline: there is no visit.
If there is a visit before the button, the old counter is still counting everyone on its own. If there is no visit after Accept, Metrica is not tied to the banner. If there is a visit after Decline, the switch did not work.
A cookie banner for the site is there so the visitor can say yes or no, and Metrica and ad pixels start only after yes. Without a banner you are left with two bad pictures: everyone is counted in silence, or the report is empty. The builder closes that without a programmer: https://auralix.tech/en/tools/cookie-banner
Sources
[1] https://www.consultant.ru/document/cons_doc_LAW_61801/4f41fe599ce341751e4e34dc50a4b676674c1416 — Article 3. Basic concepts, 152-FZ, as amended on 26 July 2026 [2] https://www.consultant.ru/document/cons_doc_LAW_61801/315f051396c88f1e4f827ba3f2ae313d999a1873 — Article 6. Conditions for processing personal data, 152-FZ [3] https://yandex.ru/support/metrica/ru/general/cookie-usage — Temporary files set by Yandex Metrica [4] https://yandex.ru/support/metrica/ru/general/notification — Warning about statistics collection [5] https://yandex.ru/support/metrica/ru/general/gdpr — GDPR compliance [6] https://yandex.ru/support/metrica/ru/general/how-it-works — How Metrica works
