Comprehensive Conversion Funnel Analysis Using GA4 and BigQuery

Our company is engaged in the development, support and maintenance of sites of any complexity. From simple one-page sites to large-scale cluster systems built on micro services. Experience of developers is confirmed by certificates from vendors.

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Showing 1 of 1All 2062 services
Comprehensive Conversion Funnel Analysis Using GA4 and BigQuery
Medium
~2-3 days
Frequently Asked Questions

Our competencies:

Development stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1358
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1251
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    957
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1188
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    929
  • image_bitrix-bitrix-24-1c_fixper_448_0.webp
    Website development for FIXPER company
    947

Imagine an e-commerce site losing 60% of users between adding a product to cart and starting checkout. Without a detailed conversion funnel analysis, pinpointing the cause is impossible. For example, one client — an electronics store — was losing 70% of traffic at the delivery selection stage. After analysis using a purchase funnel and Hotjar recordings, we discovered the form required an address before showing delivery cost. Changing the sequence increased checkout initiation conversion by 25%, saving the client $5,000 monthly in lost revenue.

We conduct comprehensive conversion funnel analysis: set up events in Google Analytics 4, export data to Google BigQuery, segment by device and channel, identify bottlenecks. Within 3–5 business days, you get a report with specific recommendations — from form fixes to retargeting logic changes. Ad budget savings through precise targeting can reach 15%.

Our approach is based on experience with projects of various scales — from small online stores to large marketplaces, with over 200 projects analyzed. Every report includes not just numbers but also behavioral analysis: why users drop off at that particular step.

How to Perform a Conversion Funnel Analysis

  1. Audit existing event tracking – Verify data correctness in GA4.
  2. Set up missing events – Add custom events (e.g., "form fill started") via gtag or GTM.
  3. Create funnel in GA4 – Use Explore → Funnel exploration with steps and breakdowns.
  4. Analyze with BigQuery – Write custom SQL for cohort segmentation and deeper insights. BigQuery provides 5x more granular segmentation than GA4 alone.
  5. Review session recordings – Use Hotjar/Clarity to see user behavior at drop-off points. Session recordings give 2x better understanding of user behavior compared to numbers alone.
  6. Deliver report – Prioritize bottlenecks and propose changes.

Which funnel stages do we analyze?

For an e-commerce store, typical stages: product view → add to cart → checkout start → payment info entry → purchase. For SaaS — registration → activation → key feature usage → payment. We adapt the funnel to your business model. Below is an example of typical conversions by device:

Device View → Cart Cart → Checkout Checkout → Purchase
Desktop 12% 45% 70%
Mobile 8% 30% 50%

Common reasons for checkout abandonment

The most frequent issues — long forms, unexpected costs (shipping, taxes), or lack of convenient payment methods. Using session recordings (Hotjar) and heat maps, we see the exact moment of frustration. For example, a client abandons the form right at the "phone number" field — meaning verification raises doubts. In such cases, simplifying the form or adding autofill helps. In one project, we reduced checkout abandonment by 35% by removing a mandatory account creation step. Another SaaS client reduced sign-up drop-off by 40% after implementing our recommendations.

Setting up tracking in GA4

First, we check event tagging at each stage. If none exists, we implement custom events via gtag or GTM:

// Event tagging for funnel steps

// Step 1: Product page view
gtag('event', 'view_item', {
  items: [{ item_id: product.id, item_name: product.name, price: product.price }]
});

// Step 2: Add to cart
gtag('event', 'add_to_cart', {
  currency: 'RUB',
  value: product.price,
  items: [{ item_id: product.id, quantity: 1 }]
});

// Step 3: Begin checkout
gtag('event', 'begin_checkout', {
  currency: 'RUB',
  value: cartTotal,
  items: cartItems
});

// Step 4: Add payment info
gtag('event', 'add_payment_info', {
  payment_type: 'card',
  value: cartTotal
});

// Step 5: Purchase
gtag('event', 'purchase', {
  transaction_id: order.id,
  value: order.total,
  currency: 'RUB'
});

After setup, we create a funnel in GA4: Explore → New exploration → Funnel exploration. Add steps, include breakdown by device and source/medium.

Analysis using BigQuery

For deeper segmentation, we use Google BigQuery — it provides 5x more detailed segmentation than GA4 alone. Queries allow calculating conversion at each transition and comparing across cohorts:

-- Conversion at each funnel step
WITH funnel AS (
  SELECT
    user_pseudo_id,
    MAX(CASE WHEN event_name = 'view_item' THEN 1 ELSE 0 END) AS viewed,
    MAX(CASE WHEN event_name = 'add_to_cart' THEN 1 ELSE 0 END) AS added,
    MAX(CASE WHEN event_name = 'begin_checkout' THEN 1 ELSE 0 END) AS checkout,
    MAX(CASE WHEN event_name = 'purchase' THEN 1 ELSE 0 END) AS purchased
  FROM `project.analytics.events_*`
  WHERE _TABLE_SUFFIX BETWEEN '20240301' AND '20240331'
  GROUP BY user_pseudo_id
)
SELECT
  COUNT(*) AS total_users,
  SUM(viewed) AS viewed,
  SUM(added) AS added_to_cart,
  SUM(checkout) AS started_checkout,
  SUM(purchased) AS purchased,
  ROUND(SUM(added) * 100.0 / SUM(viewed), 1) AS view_to_cart_rate,
  ROUND(SUM(checkout) * 100.0 / SUM(added), 1) AS cart_to_checkout_rate,
  ROUND(SUM(purchased) * 100.0 / SUM(checkout), 1) AS checkout_to_purchase_rate,
  ROUND(SUM(purchased) * 100.0 / SUM(viewed), 2) AS overall_cvr
FROM funnel;

Segmentation and tools

Device breakdown shows mobile conversion is 30% lower — form adaptation is needed. We also use queries for segmentation:

-- Funnel by device
SELECT
  device_category,
  COUNT(DISTINCT CASE WHEN step >= 1 THEN user_id END) AS step1_users,
  COUNT(DISTINCT CASE WHEN step >= 2 THEN user_id END) AS step2_users,
  COUNT(DISTINCT CASE WHEN step >= 3 THEN user_id END) AS step3_users,
  ROUND(COUNT(DISTINCT CASE WHEN step >= 3 THEN user_id END) * 100.0 /
        NULLIF(COUNT(DISTINCT CASE WHEN step >= 1 THEN user_id END), 0), 1) AS cvr
FROM funnel_data
GROUP BY device_category;

To identify drop-off points, we use not only numbers but also behavioral tools:

  • Hotjar/Clarity: session recordings of users who stopped at a problematic step
  • Heat maps: where they click and scroll
  • Form Analytics: fields where they abandon
// Tracking abandonment on checkout form
document.querySelectorAll('#checkout-form input').forEach(field => {
  field.addEventListener('blur', () => {
    gtag('event', 'checkout_field_blur', {
      field_name: field.name,
      has_value: field.value.length > 0
    });
  });
});

// Tracking page exit without form submission
window.addEventListener('beforeunload', () => {
  if (document.querySelector('#checkout-form') && !formSubmitted) {
    gtag('event', 'checkout_abandonment', {
      last_field: lastFocusedField
    });
  }
});

Comparison of analysis methods

Method Data Depth Speed Cost Complexity
GA4 Funnel Exploration Medium Instant Free Low
BigQuery custom queries High Depends on volume Pay per query High
Hotjar/Clarity sessions Qualitative Real-time Free tier available Low

GA4 is best for quick snapshots, BigQuery for complex attribution (5x more powerful), and Hotjar for qualitative understanding. Average analysis time is 3-5 days, allowing fast implementation of improvements and CVR increase of 15-30%. Basic analysis costs from $500 to $1,500 depending on complexity.

Scope of work

  • Audit of current event tagging — check data correctness in GA4.
  • Setup of missing events — add custom events (e.g., "form fill started").
  • Funnel creation in GA4 and BigQuery — with segmentation by device, channel, cohort.
  • Abandonment analysis — review session recordings and heat maps at problematic steps.
  • Report with recommendations — list of bottlenecks, priorities, and specific changes (without implementation).
  • Consultation — call or correspondence to explain results.

Common mistakes in funnel setup: incorrect event structure (e.g., currency mismatch), lack of user ID for cross-device analytics, wrong step order (inflated drop-off), ignoring channel segmentation. Without segmentation, you won't see that 50% of losses come from paid traffic.

Timeline and cost

Basic analysis (setup + report) takes 3–5 business days. If implementation is required, timeline extends to 10 days. Cost is calculated individually based on funnel complexity and number of stages. Get a free project estimate — contact us, and we'll prepare a commercial proposal.

With over 10 years of experience and 200+ projects, we guarantee actionable insights. Get a consultation on conversion funnel analysis — we'll identify bottlenecks and propose solutions that increase CVR by 15–30%. Contact us to get started.

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 we check after each deploy
  • All recommended events present in DebugView
  • No duplicates (count purchase per 100 sessions)
  • Data layer structure unchanged after frontend update

What the work includes

Component Description
Audit of existing tags Check current GTM tags, data layer, duplicates, and errors
Event schema design Documentation: event list, parameters, triggers
GA4 + GTM setup Create configuration, tags, custom definitions
Yandex.Metrica Install counter, create goals, set up Webvisor
Amplitude (optional) Set up client and server SDK, cohorts
QA and monitoring Testing in Preview Mode, alerting
Training and handover Access, instructions for adding new events, console

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)
Scenario Timeline
Basic GA4 + GTM setup 1 week
Full e-commerce tracking + Metrica 2–3 weeks
Server-side GTM + Amplitude 3–5 weeks

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.