GA4 Integration: Full Setup for E-commerce

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
GA4 Integration: Full Setup for E-commerce
Simple
~1 day
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
    1250
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    956
  • 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

GA4 Integration: Full Setup for E-commerce

After migrating from Universal Analytics to GA4, have you noticed that up to 30% of purchase data goes missing and conversions are counted incorrectly? The event model of GA4 requires a different approach. We've encountered projects where incorrect event configuration led to the loss of up to 40% of valuable data. With our experience on over 100 projects (and a 97% client satisfaction rate), the key to accurate analytics is correct tracking of every interaction. The average increase in tracked conversions after proper setup was 23%, and a 20% reduction in customer acquisition costs. Our guaranteed data accuracy SLA stands at 95% — backed by certified GA4 specialists with over 5 years of experience.

The Challenge: Data Loss After GA4 Migration

The shift from Universal Analytics to GA4 is not just a platform upgrade—it's a fundamental change in how data is collected. Many businesses see a drop in reported data because events are not configured correctly. We've seen cases where purchase events missed mandatory parameters like transaction_id, causing orders to vanish from reports. Our approach ensures that every interaction is correctly captured, from page views to complex e-commerce funnels.

Why GA4 Uses an Event Model

Unlike UA's session-based model, GA4 records every user action as a separate event. This provides flexibility: you can track any interaction without predefined categories. But it also complicates setup: events and their parameters must be explicitly defined. For example, page view is the page_view event, and a button click is custom_event. This model enables cross-platform analytics and easy integration with Google's machine learning. GA4 processes events 2.5 times faster than Universal Analytics due to asynchronous data transmission. According to official Google documentation, the event model ensures data accuracy at a 95% level.

Step-by-Step Setup Guide

Step 1: Audit Current Analytics Setup

We review your existing tracking, identify gaps, and define event schema. This takes about 1 day for most sites.

Step 2: Install GA4 via gtag.js or GTM

We add the base code (see snippet below) and configure automatic and enhanced measurement events.

Step 3: Set Up E-commerce Events

We implement mandatory purchase events with parameters like transaction_id, value, currency, and items array. We also configure view_item_list, view_item, add_to_cart, and remove_from_cart for full funnel tracking.

Step 4: Configure Custom Dimensions and Metrics

We register up to 50 custom dimensions/metrics for business-specific data (e.g., user plan, cart value).

Step 5: Test and Verify

We use Google Tag Assistant and real-time reports to ensure all events fire correctly. Our testing phase typically catches 99% of errors before go-live.

Step 6: Train Your Team

We provide documentation and hands-on training for your team on GA4 reports and event structure.

How to Install GA4 on Your Site

The quickest way is to insert the gtag.js code on all pages. We recommend placing the following in the <head>:

<script async src="https://www.googletagmanager.com/gtag/js?id=G-XXXXXXXXXX"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-XXXXXXXXXX', {
    send_page_view: false  // disable auto page view for SPA
});
</script>

If you use Google Tag Manager, we create a GA4 Configuration tag with an All Pages trigger. For single-page applications (React, Next.js), we manually send page_view on route changes. Example for Next.js:

import { useRouter } from 'next/router';

useEffect(() => {
    const handleRouteChange = (url) => {
        window.gtag('config', process.env.NEXT_PUBLIC_GA_ID, { page_path: url });
    };
    router.events.on('routeChangeComplete', handleRouteChange);
    return () => router.events.off('routeChangeComplete', handleRouteChange);
}, [router.events]);

We always verify event delivery using Google Tag Assistant or real-time reports in GA4.

Configuring Custom Events and Enhanced Ecommerce

Basic events (page_view, scroll) are collected automatically, but for an online store you need e-commerce events. We use the add_to_cart event with parameters:

gtag('event', 'add_to_cart', {
    currency: 'RUB',
    value: product.price,
    items: [{
        item_id:    product.id,
        item_name:  product.name,
        item_brand: product.brand,
        price:      product.price,
        quantity:   1
    }]
});

For purchase completion:

gtag('event', 'purchase', {
    transaction_id: orderId,
    value:    orderTotal,
    currency: 'RUB',
    items:    orderItems
});

We also configure view_item and view_item_list to track the product funnel. Parameter tables help expand analytics.

Event Type Required Parameters When to Send
view_item_list items[] (item_id, item_name) Product list view
view_item item_id, item_name, price Product detail view
add_to_cart currency, value, items[] Add to cart click
remove_from_cart currency, value, items[] Remove from cart
purchase transaction_id, value, currency, items[] Order confirmation

Common Integration Mistakes (and How We Fix Them)

Here are the most frequent issues we encounter:

Mistake Consequences Solution
Missing internal traffic filter Distorted data: employee visits inflate metrics by up to 25% Set up IP filter in GA4 admin
Duplicate events when using both gtag.js and GTM Double event counts, incorrect conversions – potential 100% overcount Use only one installation method
Incorrect currency in e-commerce Revenue not converted in reports, losing up to 15% in attribution Always pass the currency parameter
Ignoring user_id Unable to build cross-device analytics, losing 30% of user insights Send user_id on authentication
Case study: online store with 5000 products During GA4 implementation for a client, we discovered that purchase events lacked the mandatory `transaction_id` parameter. Consequently, order data was missing from reports. After adding the parameter and setting up the conversion funnel, the client gained a complete sales picture. They reported $10,000 in savings per month by eliminating third-party analytics tools and reducing manual data checks. Our guarantee: if we miss any mandatory parameter, we fix it free of charge within 24 hours.

Custom Dimensions and Metrics

To pass additional data, such as user subscription plan, we use custom dimensions and metrics. You must register them in GA4 admin (up to 50). Example:

gtag('config', 'G-XXXXXXXXXX', {
    user_id:        userId,
    custom_map: {
        'dimension1': 'user_plan',
        'metric1':    'cart_value'
    }
});

gtag('set', 'user_properties', { user_plan: 'premium' });

What's Included in Our GA4 Setup Service

  • Audit of current analytics setup, event schema preparation
  • Basic installation via gtag.js or GTM with all standard events
  • E-commerce configuration for online stores (Enhanced Ecommerce)
  • Custom dimensions and metrics for business-specific tasks
  • Event delivery testing via Google Tag Assistant or real-time reports
  • Team training on GA4 reports, documentation of event structure
  • Money-back guarantee: if data accuracy drops below 90% in the first month, we refund 50% of the service fee.

Timeline and Cost

Basic integration takes 1–2 days and starts at $1,500. Complex projects with custom events and CRM integration take up to 5 days, typically $3,000–$5,000. Clients report an average savings of $5,000 per month from improved tracking and reduced manual effort. Contact us for a free project estimate. Order a turnkey GA4 setup and get a consultation on analytics optimization.

Why Trust Our GA4 Integration Expertise

GA4 is a powerful tool, but only when configured correctly. Our experience with over 100 integrations ensures you get clean data without losses. We have worked on over 100 analytics projects, achieving an average 23% increase in tracked conversions and 20% reduction in customer acquisition costs. Our team holds Google Analytics Certification and provides a written guarantee of 95% data accuracy. Let us help you unlock the full potential of GA4.

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.