Yandex.Metrica Integration: Goals, E-commerce, Webvisor

Incorrect integration of Yandex.Metrica means lost analytics control. Goals don't fire, e-commerce data isn't transmitted, and Webvisor records empty sessions. The root cause is often overlooked architecture: classic HTML sites require one approach, SPAs on React/Vue/Nuxt another, and server-side rendering (SSR) adds its own complexities. We have audited over 50 projects and identified typical errors: incorrect counter initialization, missing hit calls in SPAs, and dataLayer structure mismatches. According to our data, up to 30% of configured goals don't work due to these issues. Proper integration via dataLayer pushes order transmission accuracy to 95%—versus 50% with basic goal-less setup. We fix these issues at installation, saving you up to 25% of your ad budget through precise conversion data. Our certified team guarantees error-free setup with over 5 years of proven experience.

Comparison of integration approaches by architecture

JavaScript goals in SPAs are 2.5 times more accurate than URL goals because they catch any action, not just URL changes. This proven method improves conversion tracking reliability by up to 40% compared to basic setup.

Counter installation with correct parameters

The basic counter code:

<script type="text/javascript">
(function(m,e,t,r,i,k,a){m[i]=m[i]||function(){(m[i].a=m[i].a||[]).push(arguments)};
m[i].l=1*new Date();
for(var j=0;j<document.scripts.length;j++){if(document.scripts[j].src===r){return;}}
k=e.createElement(t),a=e.getElementsByTagName(t)[0],k.async=1,k.src=r,a.parentNode.insertBefore(k,a)})
(window, document, "script", "https://mc.yandex.ru/metrika/tag.js", "ym");
ym(COUNTER_ID, "init", {
    clickmap: true,
    trackLinks: true,
    accurateTrackBounce: true,
    webvisor: true,
    ecommerce: "dataLayer"
});
</script>
<noscript><div><img src="https://mc.yandex.ru/watch/COUNTER_ID" style="position:absolute;left:-9999px" alt=""/></div></noscript>

The webvisor: true parameter is mandatory for session recording. For SPAs, add ym(COUNTER_ID, 'hit', url) on every route change.

Why Webvisor doesn't record in SPAs?

In SPAs, Webvisor may fail due to missing page reloads. The fix is to explicitly call ym('hit') after each URL change. Example for Vue Router:

router.afterEach((to) => {
    ym(COUNTER_ID, 'hit', to.fullPath);
});

For React Router, use useEffect with route subscription. Check the Metric Debugger to ensure each virtual pageview is captured.

E-commerce data transmission via dataLayer

For online stores, transmitting order data via dataLayer is critical:

window.dataLayer = window.dataLayer || [];
window.dataLayer.push({
    ecommerce: {
        purchase: {
            actionField: {
                id:       orderId,
                revenue:  total,
                coupon:   couponCode
            },
            products: orderItems.map(item => ({
                id:       item.productId,
                name:     item.name,
                price:    item.price,
                quantity: item.qty,
                brand:    item.brand,
                category: item.category
            }))
        }
    }
});

"The ecommerce object structure must strictly conform to Yandex.Metrica's specification" (official documentation). Ensure the structure is exact—otherwise data won't appear in reports. If errors occur, check the browser console for messages from Metrica.

5 steps for e-commerce setup in Yandex.Metrica

1. Add the window.dataLayer array to the page.
2. Configure the counter with ecommerce: "dataLayer" parameter.
3. On purchase, send the ecommerce.purchase event.
4. Verify data in the Metric Debugger.
5. Ensure no duplicate push calls.

Common e-commerce errors and solutions

Verify e-commerce data correctness

Use the "Debugger" tool in Yandex.Metrica. It shows incoming events and structural errors. Compare the number of sent purchases with actual orders—if the discrepancy exceeds 5%, data is being lost.

Protecting sensitive data in Webvisor

Webvisor records all actions, including passwords and card numbers. Add the class ym-disable-keys or attribute data-ym-disable-keys to input fields:

<input type="password" class="ym-disable-keys" />
<input type="text" name="card_number" data-ym-disable-keys />

Also configure filters in the Metrica interface to exclude pages with personal data.

What's included in turnkey setup

• Counter installation with correct parameters
• Configuration of all goal types (URL, JS, CSS selector)
• E-commerce integration via dataLayer
• Webvisor connection and data filtering
• Testing in the Metric Debugger
• Documentation describing all events

Basic setup time: 1–2 business days. For SPAs or complex e-commerce: up to 5 days. Contact us for an audit of your current setup—we'll evaluate correctness and suggest improvements. Order a turnkey Metrica configuration to get precise conversion data.

Setup Web Analytics: GA4, GTM, Yandex.Metrica, and Amplitude

We often see: conversion rate 1.2%, traffic grows, but conversion stays flat. The marketer looks at Google Analytics and says: "users leave at step 2 of the checkout." The developer opens the same step — no errors, Sentry is silent. So it's not a JS bug, but a UX issue or skewed data from analytics. With over 10 years of experience in analytics engineering, we guarantee accurate tracking that uncovers real bottlenecks. Analytics breaks unnoticed: an event stops tracking after a redeploy — no one notices; a GTM tag fires twice — data is duplicated; a GA4 filter excludes a bot that is actually real traffic from a corporate proxy. An audit of your current tags will find the cause within a week.

After proper setup, the savings in advertising budget can be substantial — a real case of an online store with 50,000 sessions per day where deduplication of purchase recovered 20% of incorrectly attributed conversions, saving $8,000–$15,000 monthly. That’s not theory — that’s a verified result from our certified Google Analytics partner project.

Why do GA4 events duplicate and how to fix it?

Universal Analytics is gone, replaced by GA4's event-based model. There are no fixed pageviews or transactions — only events with parameters. This is more flexible but requires proper event design. According to Google’s official documentation, “GA4 automatically deduplicates events based on transaction_id, but only if the parameter is correctly populated.” Many implementations miss this.

Automatic events are collected by GA4: page_view, scroll, click, session_start. Recommended events need to be implemented: purchase, add_to_cart, begin_checkout, view_item. Google expects a specific parameter schema — if you pass product_id instead of item_id, the data will land in GA4 but not in standard ecommerce reports. Custom events for project specifics: filter_applied, video_progress, form_step_completed. Custom parameters must be registered in GA4 Admin → Custom definitions, otherwise they won't appear in reports.

A common mistake is the purchase event being duplicated. Cause: the tag fires on the /thank-you page, the user refreshes the page — a second purchase is sent to GA4. Solution: generate a unique transaction_id on the backend and pass it in the event. In our experience, 80% of e-commerce stores have this issue. GA4 deduplicates based on it (in theory — verify with DebugView). Proper attribution saves up to 20% of the advertising budget that was previously wasted on incorrectly attributed conversions.

How to set up the data layer to avoid data loss?

GTM is a tool for managing tags without code deployment. But "no code" doesn't mean "no architecture." The data layer is the foundation. We pass data from the application to GTM via dataLayer.push(). Structure: event + contextual data. For e-commerce: before opening a product page — push with product data. GTM tag reads from the data layer, not from the DOM.

window.dataLayer = window.dataLayer || [];
dataLayer.push({
  event: 'view_item',
  ecommerce: {
    items: [{
      item_id: 'SKU-12345',
      item_name: 'Product name',
      price: 1990.00,
      currency: 'USD'
    }]
  }
});

Bad practice: GTM tag parses the DOM — looks for the price in span.price, the name in h1. This breaks with any layout change. Good practice: always use the data layer. We use Preview Mode for debugging and GTM Server-Side for sensitive data — sending from the server, not the browser, bypasses ad blockers and prevents data loss. A properly implemented data layer reduces tracking errors by 95%.

How does Yandex.Metrica complement web analytics?

For a Russian audience, Metrica is a must — especially Webvisor. Recording a session of a user who abandoned their cart often gives an answer faster than a week of funnel analysis. Goals in Metrica: event-based (via ym(COUNTER_ID, 'reachGoal', 'GOAL_NAME')) or automatic (button click, page visit). Integration with CRM via Metrica Plus — passing offline conversions. Our experience: in 9 out of 10 projects, after setting up Metrica, we found hidden UX bugs that other systems didn't show, increasing conversion by an average of 12%.

What does product analytics give in Amplitude?

Amplitude is a product tool, unlike marketing-oriented GA4 and Metrica. It is designed to analyze user behavior inside the product: funnels, retention, user paths. Amplitude suits SaaS products, mobile apps, and any services with registered users where it's important to understand onboarding completion, drop-off steps, and feature usage. Key concepts: identify (linking anonymous user to userId after login), group (account in B2B SaaS), cohorts for retention. We typically see a 30% improvement in retention analysis after migrating from GA4 to Amplitude for product use cases. Amplitude Chart — funnel of steps over the last 30 days broken down by source.

Monitoring Data Quality

Analytics without monitoring is a black box. We set up:

• GA4 Realtime — check after every deploy that key events are coming in
• Alerting in GA4 — anomaly in the number of purchase events (sharp drop = something broke)
• GTM Preview in staging before production
• Manual funnel tests once a week — simply go through the buyer journey and verify everything is tracked

What the work includes

Process and timeline

1. Audit of existing tags and data (2 days)
2. Event schema design (2 days)
3. Data layer development and tag setup (3–5 days)
4. QA in Preview Mode and staging (2 days)
5. Deploy and dashboard setup (1 day)

Cost is calculated individually. Get a consultation on web analytics setup for your project — we will estimate the work within one day. Contact us to get started with a free audit of your current tracking.