Yandex Metrica vs Google Analytics: what changes when you sell in Russia

Most foreign companies arrive in Russia with a mature Google Analytics 4 setup and a reasonable question: can’t we just use that? You can, for reporting. You can’t for advertising. Yandex Direct, the paid search platform you’ll be using instead of Google Ads, reads its conversion goals from Yandex Metrica and nothing else. If Metrica isn’t installed with goals, every automated strategy in Direct optimizes for clicks, because clicks are all it can see.

So the question isn’t Metrica or GA4. It’s how to run Metrica properly alongside what you already have. Here’s what’s different and what to do about it.

What Yandex Metrica is

Metrica is Yandex’s web analytics system, roughly the counterpart of Google Analytics, free, and tightly integrated with Yandex Direct, Yandex Webmaster and Yandex’s audience tools. It’s the system most Russian websites run, often alongside GA4. The interface and help center are available in English.

Under the hood it does the familiar things: traffic sources, pages, conversions (called goals), audiences, e-commerce reports. And several things GA4 doesn’t include by default.

Five practical differences

1. Direct optimizes only toward Metrica goals. This is the one that decides everything else. A goal in Metrica is a form submission, a click on a phone number, a visit to a thank-you page, a messenger button, a purchase. Yandex Direct’s automated strategies (maximize conversions, target cost per action, pay-per-conversion) take a Metrica goal as their objective. Without one, the strategy has no objective. With a badly defined one, it optimizes toward the wrong thing, and you’ll get cheap “conversions” that aren’t inquiries.

What to do: define goals before launching ads, test that each one fires (Metrica shows goal completions in real time), and pick the goal closest to money as the strategy’s objective.

2. Session replay and heatmaps come built in. Metrica’s Webvisor records visitor sessions so you can watch how a Russian visitor actually moves through your landing page: where they hesitate, which form field they abandon, whether they scroll to the price. Click, scroll and link heatmaps are there too, plus form analytics that shows completion rates field by field. In the Google world you’d add a separate tool for this.

For a foreign company this is the single most useful feature. You can’t intuit how a Russian buyer reads a page you wrote for a different culture. Webvisor shows you. On projects where we doubled conversion without touching the budget, the diagnosis came from watching sessions, not from a dashboard.

3. Data isn’t sampled and there’s no event cap. GA4 samples in some reports and has quotas around events and properties. Metrica reports on all data for normal website volumes. Less of a headline for a small site; a real difference once traffic grows.

4. Ad blockers affect it less. Metrica’s counter is blocked less often than Google’s tags by common ad-blocking lists, so its visit counts for Russian traffic tend to run higher than GA4’s on the same site. This is not a reason to trust one and distrust the other; it’s a reason to expect the numbers to differ and to compare trends, not absolutes.

5. The Direct reports live inside Metrica. Metrica has a “Yandex Direct, costs” report that joins ad spend with on-site behavior and goals, so cost per goal by campaign, ad group and keyword is available without exporting anything. It’s the report I open first in every audit.

Where GA4 still matters

If your global reporting runs on GA4, keep it. Board-level dashboards, cross-market comparisons, attribution across your other channels: none of that should move to Metrica. The Russian campaigns become one more source in GA4, and Metrica is the operational system for running them.

Two practical notes. Tag both systems with the same UTM structure so a campaign looks the same in both. And expect the two to disagree by some percentage on visits and conversions; the causes are ad blockers, different session definitions and different bot filtering. Choose one system as the source of truth for each decision (Metrica for optimizing Yandex campaigns, GA4 for global reporting) and stop reconciling the last five percent.

Setting it up: the short version

1. Create a Metrica counter for the site and install the tag, directly or through Google Tag Manager.
2. Turn on Webvisor, heatmaps and form analytics in the counter settings.
3. Define goals: form sent, phone click, messenger click, thank-you page, purchase. Use Tag Manager events if you already have them.
4. Verify each goal fires, in real time, from a test session.
5. Link the counter to your Yandex Direct account so campaigns can use the goals.
6. For visitors from the EU or UK, load Metrica only after cookie consent, the same way you handle GA4.
7. Give your Russian-side specialist access. Reports in English are easy to produce from either system; the optimization decisions need the person who reads the market.

The mistake to avoid

The one I see most: launching Yandex Direct with GA4 on the site and no Metrica goals, then judging the campaign by GA4’s numbers a month later. The campaign has been optimizing toward clicks the whole time, the GA4 conversions were never visible to it, and the verdict “Yandex doesn’t work for us” is really “we never told Yandex what working means”.

If your Russian analytics setup is a question mark right now, the free review covers it: I’ll look at what fires, what doesn’t, and what Direct can actually see.

Frequently asked questions

Sources

• Yandex Metrica help center: yandex.com/support/metrica/en
• Yandex Metrica, "Yandex Direct, costs" report: yandex.com/support/metrica/en/sources/direct-clicks
• Yandex Direct help, automated strategies and goals: yandex.com/support/direct/en/strategies