Detailed GA4 Setup for E-commerce: Events, Funnel, Reconciliation

You launched an online store on React/Next.js with a Redux cart? Products are being added, but Google Analytics shows zero events. Without Enhanced Ecommerce, you can't see at which step users drop off, which promotions work, and your ad budget is spent blindly. Discrepancies between GA4 data and actual sales can reach 15–20% — a blind spot for your business. We help integrate a full funnel from catalog to checkout with data reconciliation accuracy up to 95%. Over the years, we have set up Enhanced Ecommerce for 50+ projects on various stacks — from WordPress to custom Next.js solutions. Each project required a tailored approach: some needed 1C integration, others server-side GTM to bypass ad blockers.

Problems We Solve

Dark funnel. Without events like view_item_list, add_to_cart, begin_checkout, you can't see where you lose customers. Enhanced Ecommerce captures every step.

Data discrepancy. GA4 loses 5–15% of transactions due to ad blockers and cross-device transitions. We reconcile events with your database via BigQuery or Conversions API, minimizing gaps.

Promotions without return. Banners and discounts not performing? view_promotion and select_promotion show real CTR.

Using server-side GTM with Conversions API, we achieve accuracy up to 98% — that's 20-30% higher than standard setup.

Case study: For a fashion retailer with 10,000 SKUs, we implemented server-side GTM and Conversions API, reducing data discrepancy from 15% to 2% and increasing attributed revenue by 20%.

What Enhanced Ecommerce Brings to Your Store

Full sales funnel: from catalog view to order completion. You see where clients drop off, which products are viewed but not bought, and which promotions generate revenue. Refund analytics allow you to adjust financial reports. All this is available in standard GA4 reports without additional tools. Thanks to database reconciliation, GA4 data reflect reality with a margin of error no greater than 5%.

How to Avoid Data Discrepancies Between GA4 and Actual Sales

Use Conversions API together with gtag.js: server-side events are not blocked and provide a more accurate picture. In our projects, GA4 deviation from database data is no more than 5% — versus typical 10-15% with standard setup. We also configure server-side GTM for full control. Server-side event processing eliminates losses from ad blockers and code errors. Server-side GTM with Conversions API delivers 95–98% accuracy, 2-3 times better than plain gtag.js. This reduces ad budget waste through precise attribution — saving up to 30% on ads. ROI on setup is 2–3 months.

Step-by-Step Plan for Enhanced Ecommerce Setup

1. Audit current analytics — check existing tags, DataLayer, tracking errors.
2. Event strategy — choose method (gtag.js or GTM) and define full list of e-commerce events.
3. Implement all funnel events — from view_item_list to purchase, including promotions and refunds.
4. Testing and reconciliation — A/B test events, compare with CRM/database data.
5. Documentation and training — description of each event, team instructions.

This plan eliminates data loss and ensures up to 95% accuracy. Average increase in data reliability after setup: 20%.

E-commerce Event Funnel

view_item_list → view_item → add_to_cart → begin_checkout → purchase
(catalog)       (product)     (cart)         (checkout)       (order)

Why Server-side GTM Is More Accurate

Server-side GTM processes events on the server, bypassing ad blockers and client-side code errors. This ensures data accuracy of 95–98%, 2-3 times better than standard gtag.js. Plus, server-side processing allows sensitive data to be sent without risk of leakage in the browser. We recommend using server-side GTM together with Conversions API for maximum accuracy.

Implementing All Funnel Steps

// 1. View item list (catalog, recommendations)
gtag('event', 'view_item_list', {
    item_list_id:   'category_shoes',
    item_list_name: 'Shoes',
    items: products.map((p, i) => ({
        item_id:       p.id,
        item_name:     p.name,
        item_brand:    p.brand,
        item_category: p.category,
        item_list_name:'Shoes',
        index:         i,
        price:         p.price,
        quantity:      1
    }))
});

// 2. Click on an item in list
gtag('event', 'select_item', {
    item_list_name: 'Shoes',
    items: [{ item_id: product.id, item_name: product.name, index: 3 }]
});

// 3. View product page
gtag('event', 'view_item', {
    currency: 'USD',
    value:    product.price,
    items: [{
        item_id:       product.id,
        item_name:     product.name,
        item_brand:    product.brand,
        item_category: product.category,
        item_variant:  selectedVariant,
        price:         product.price
    }]
});

// 4. Add to cart
gtag('event', 'add_to_cart', {
    currency: 'USD',
    value:    product.price * quantity,
    items: [{ ...productData, quantity }]
});

// 5. Begin checkout
gtag('event', 'begin_checkout', {
    currency: 'USD',
    value:    cart.total,
    coupon:   appliedCoupon,
    items:    cart.items
});

// 6. Add shipping info
gtag('event', 'add_shipping_info', {
    currency:       'USD',
    value:          cart.total,
    shipping_tier:  'Express',
    items:          cart.items
});

// 7. Add payment info
gtag('event', 'add_payment_info', {
    currency:      'USD',
    value:         cart.total,
    payment_type:  'Visa',
    items:         cart.items
});

// 8. Purchase
gtag('event', 'purchase', {
    transaction_id: order.id,
    value:          order.total,
    tax:            order.tax,
    shipping:       order.shippingCost,
    currency:       'USD',
    coupon:         order.coupon,
    items:          order.items
});

According to Google's GA4 documentation, the purchase event must include transaction_id for correct reconciliation.

Promotions and Banners

// Promotion impression (banner, slider)
gtag('event', 'view_promotion', {
    promotions: [{
        promotion_id:   'summer_sale',
        promotion_name: 'Summer Sale',
        creative_name:  'banner_home',
        creative_slot:  'hero_slot'
    }]
});

// Click on promotion
gtag('event', 'select_promotion', { promotions: [...] });

Refunds

gtag('event', 'refund', {
    transaction_id: orderId,
    value:          refundAmount,
    currency:       'USD',
    items: [{ item_id: productId, quantity: 1 }]
});

For more on event structure, see the official GA4 documentation.

Method Comparison Table

Server-side GTM with Conversions API delivers 95–98% accuracy, 2-3 times better than plain gtag.js. This reduces ad budget waste through precise attribution — saving up to 30% on ads. ROI on setup is 2–3 months.

After implementing Enhanced Ecommerce, clients see a 15–25% increase in revenue through optimized ad campaigns.

What Is Included in the Work

Timeline and Pricing

Setup time: 2 to 5 business days, depending on catalog complexity and CMS. Pricing is determined individually after a thorough analysis.

Get a free consultation for your store. Order Enhanced Ecommerce setup and get transparent sales analytics. Contact us for a scope assessment.

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.