Conversion Analysis & Funnel Setup in GA4 and Yandex.Metrica

Imagine: your site brings 1000 visitors a day, but revenue isn't growing. Managers complain about traffic, marketers about conversion, and developers shrug. Without a configured sales funnel, you're flying blind. Standard GA4 and Yandex.Metrica reports show overall conversion but don't pinpoint drop-off points. We know how to fix this: we set up turnkey funnels using segmentation, cohort analysis, and end-to-end analytics. We identify at which step — product view, add to cart, checkout — customers are lost and increase conversion at each stage. We'll evaluate your project in 1 day — contact us!

Problems We Solve

Blurred user path. Standard reports don't show where clients drop off. A funnel with traffic source segmentation and cohort analysis gives a clear picture. For example, the "add to cart" step converts at 5% — the issue is UX or pricing. Conversion optimization based on funnel reports reduces losses.

Losses from ad blockers. GA4 loses up to 30% of events on mobile. The solution is to duplicate sending to your own backend. This provides a control sample and improves funnel report accuracy. One client after implementing this scheme increased data accuracy by 22%.

Normal Conversion Rates for E-commerce

Differences in GA4 and Yandex.Metrica Data

The reason is different collection architectures. GA4 uses events with processing delays of up to a day, Metrica uses streaming. If both counters are run in parallel without unifying event logic, you'll get discrepancies. We configure identical events and metrics in both systems, and for critical projects we write our own funnel in PostgreSQL. This ensures end-to-end analytics and a single source of truth. GA4 processes events up to 24 hours, while Metrica up to an hour, making it 24 times faster for operational reports.

How We Do It

Stack: PostgreSQL for event storage, Laravel 11 for collection backend, Redis for caching. Example of funnel configuration in GA4:

Funnel Exploration → Steps:
1. view_item (URL contains /product)
2. add_to_cart
3. begin_checkout
4. add_payment_info
5. purchase

In Yandex.Metrica by URL and goals:

Step 1: URL contains /catalog
Step 2: URL contains /product
Step 3: Goal "add_to_cart"
Step 4: Goal "order_placed"

For high-load we use ClickHouse — SQL query response time up to 100 ms on billions of rows.

How Segmentation Improves Funnel Analysis?

Segmentation by traffic source, device, or geography reveals hidden problems. For example, organic may convert at 3%, while ads at 0.5%. Without segmentation you average the data and miss growth points. We configure segmented funnels and cohort analysis for each channel.

What is Cohort Analysis in a Funnel?

Cohort analysis groups users by time of first visit or action. This helps track how different groups behave. For instance, a cohort from an ad campaign may have higher checkout conversion but lower add-to-cart rate. Such analysis reveals channel effectiveness and seasonal trends.

Process

1. Analytics — audit of goals and events, interviews with marketers.
2. Design — agreement on funnel schema, tool selection.
3. Implementation — event setup, exploration, SQL queries.
4. Testing — verification on test sessions.
5. Deployment — rollout to production, dashboards, documentation.

What's Included

• Documentation describing funnel steps and segments.
• Ready-made explorations in GA4 and reports in Metrica.
• Team training (1 hour online).
• 2 weeks support after launch.

Why Trust Us?

5+ years experience in web analytics, over 50 projects for e-commerce and B2B. We guarantee transparency: we provide SQL scripts and documentation. Order funnel setup — get a funnel that actually helps you earn. Savings on ineffective advertising can be up to 30% after funnel optimization.

Estimated Timelines

Basic setup (GA4 + Metrica) — from 2 to 4 days. Extended (with custom DB and segmentation) — from 5 to 8 days. Cost calculated individually, depends on complexity.

Typical Mistakes in Funnel Setup

• Incorrect step order (e.g., purchase before begin_checkout) — zero conversions.
• Ignoring segmentation — one funnel for all sources hides problems.
• No protection against ad blockers — loss of up to one third of data.

Comparison Table: GA4 vs Yandex.Metrica

Source: official documentation sales funnel

We manage the full cycle of online store analytics installation: from goal setup to end-to-end analytics. Get a consultation — we'll help you choose the tool and set everything up turnkey.

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.