GA4 ecommerce setup: Events, Conversions and Data That Actually Drives Growth
Web Analytics & Ecommerce
GA4 for ecommerce: event setup, conversions and the data that matters.
Having GA4 installed does not automatically mean it is configured properly.
For an ecommerce business, data quality depends on precise events, a structured dataLayer, conversions connected to Google Ads and tracking that can withstand privacy restrictions.
In summary
GA4 measures interactions through events and parameters.
For an ecommerce business, this means tracking cannot be treated as a standard configuration: it must be designed around the purchase funnel, the dataLayer, conversion quality and integration with Google Ads.
A GA4 property that is installed but not configured correctly produces numbers that look plausible but lead to wrong decisions on campaigns, budget, products and strategy.
GA4 and ecommerce tracking: the numbers that matter
Causes of data loss in GA4 ecommerce — estimated impact
Sources: Statista 2026 · IAB State of Data 2025 · Stape Case Study Feb. 2026 · SR Analytics 2025 · WebKit/Apple Documentation 2024
All data is updated to 2025–2026 and based on verifiable sources.
The acceptable 5–10% discrepancy between GA4 and CRM assumes Consent Mode v2 is correctly configured, server-side tracking is active and there are no duplicated events. Without these requirements, the typical discrepancy is 30–50%.
GA4 for ecommerce: why configuration makes the difference
GA4 measures everything through events. Every interaction — a product view, an Add to Cart click, a completed purchase — is an event with customisable parameters. This flexibility is the platform’s main strength, but it is also the reason why a superficial setup produces wrong data.
For an ecommerce business, data quality depends on how precisely events, product parameters, economic values and transaction information are sent.
It is not enough for GA4 to work: it must work in the right way, with the correct dataLayer, connected conversions and tracking that can withstand browser restrictions.
In the audit activities we carry out on GA4 ecommerce accounts, the most frequent errors concern missing critical events, incomplete parameters and duplicated purchases. The most common case is the purchase event without a complete items array, which makes it impossible to analyse sales by category, SKU, brand or variant.
Prerequisites: what you need before touching GA4
Before configuring any event, three elements must be in place.
Skipping one of these steps is the most common cause of setups that appear to work but produce incomplete or unreliable data.
1. Google Tag Manager installed correctly
Google Tag Manager is the tool used to manage tracking logic without changing the site code every time.
For an ecommerce business it is essential: it allows GA4 events to be triggered in response to specific user actions, configurations to be tested in preview mode and tracking logic to remain separate from site development.
Check that the GTM container is present both in the page <head> and <body>.
2. Consent Mode v2 configured
With the evolution of privacy regulations and Google policies for the EEA, consent management has become a structural part of tracking.
Consent Mode v2 allows the user’s consent status to be communicated to Google and, where possible, helps preserve measurement quality through aggregated and modelled data.
To explore the topic further, we recommend reading our guide on
Consent Mode v2,
which is the starting point before any advanced GA4 configuration.
“Consent Mode v2 is the difference between having data you can use to make decisions and having numbers that only tell half the story. In Europe, ignoring it means optimising campaigns while wearing a blindfold.”
3. Ecommerce dataLayer on the site
The dataLayer is the communication layer between the website and Google Tag Manager.
For ecommerce tracking, the site must populate the dataLayer with product and transaction information at the right moment:
product view, add to cart, checkout, payment and completed purchase.
If the site uses Shopify, WooCommerce or Magento, there are plugins, apps and extensions that can automatically populate the dataLayer.
If the site is custom-built, this work must be carried out by developers following GA4 specifications.
The essential ecommerce events in GA4
GA4 defines a set of recommended ecommerce events that cover the entire purchase funnel.
Configuring all of them is not mandatory, but the more events are present, the more complete the reading of user behaviour
and performance will be.
This approach is especially important in a zero-click search and AI scenario,
where data quality becomes the real competitive advantage. We also discuss this in the article
Zero-Click Search: AI is eating clicks.
- view_item — product view
- add_to_cart — add to cart
- begin_checkout — checkout start
- purchase — completed purchase
The difference compared to the past is not in the events themselves, but in how precisely they are populated.
In GA4, tracking is not enough: you need to track well.
The dataLayer for the purchase event
The purchase event is the most important one and requires the most precise configuration.
Here is the correct dataLayer structure:
window.dataLayer = window.dataLayer || [];
dataLayer.push({ ecommerce: null });
dataLayer.push({
event: 'purchase',
ecommerce: {
transaction_id: 'T_12345',
value: 129.90,
tax: 23.62,
shipping: 4.90,
currency: 'EUR',
coupon: 'SUMMER10',
items: [{
item_id: 'SKU_001',
item_name: 'Product Name',
item_category: 'Category',
item_brand: 'Brand',
price: 64.95,
quantity: 2
}]
}
});
Always include the currency parameter, even if you sell in only one currency.
GA4 uses it to normalise data in aggregate metrics and for multi-country analyses.
Configuring conversions in GA4: which events to mark and why
In GA4, any event can be marked as a conversion. But this does not mean that every event should be.
Marking too many conversions makes reports confusing and reduces the quality of decision-making.
The right conversions for an ecommerce business:
- purchase — main conversion
- begin_checkout — purchase intent
- add_to_cart — micro-conversion
- sign_up — registered users
- generate_lead — for B2B flows
Connecting GA4 to Google Ads
The connection between GA4 and Google Ads allows conversions to be imported directly into campaigns,
enabling strategies such as Smart Bidding, Target ROAS and Target CPA.
- Configure purchase as a primary conversion in GA4
- Connect GA4 to Google Ads
- Import the purchase conversion
- Set it as primary
- Disable any duplicated conversions
This is a critical point, especially today, with the evolution of automated campaigns as explained in the article
Google AI Max for Shopping and Travel.
If you have both a Google Ads tag and a conversion imported from GA4, you are probably counting every purchase twice.
Enhanced Ecommerce: the advanced parameters that make the difference
GA4 supports a range of additional parameters for ecommerce events that enable much more granular analysis.
Not every site implements them, but these are the parameters that turn GA4 from a counting tool into a business analysis tool.
Advanced parameters help answer operational questions: which product lists generate the most sales?
Which categories attract traffic but do not convert? Which brands have a good add-to-cart rate?
Where does the purchase journey actually break down?
The parameters we use systematically
| Parameter | What it is used for | Why it is useful |
|---|---|---|
item_id |
Identifies the SKU or product ID. | Enables precise product-level analysis and reconciliation with CRM, ERP or product feed data. |
item_name |
Indicates the product name. | Makes reports readable for marketing, ecommerce managers and leadership teams. |
item_brand |
Identifies the product brand. | Useful for multi-brand ecommerce sites or marketplaces with assortment strategies. |
item_category |
Indicates the main product category. | Helps analyse performance, margin and conversions by product area. |
item_category2 |
Indicates a subcategory. | Enables deeper analysis on complex ecommerce taxonomies. |
item_variant |
Indicates variant, size, colour or configuration. | Helps understand which variants generate interest and which ones block the purchase. |
item_list_name |
Indicates the list from which the interaction originated. | Measures the effectiveness of homepages, categories, search results, carousels and editorial sections. |
index |
Indicates the product position within the list. | Helps understand whether placement influences clicks, cart additions and conversions. |
coupon |
Records the promotional code used. | Useful for assessing the real impact of promotions and margin cannibalisation. |
discount |
Records the discount applied to the product. | Helps read revenue not only as sales volume, but as quality of sales. |
This level of detail is also essential when building advanced dashboards.
Without complete ecommerce parameters, tools such as Data Studio (formerly Looker Studio) risk displaying data that is visually clean but weak from a decision-making perspective. We also discuss this in our guide to data visualization for business.
Server-side tracking: why it is essential
Client-side tracking has a structural limitation: it gets blocked.
Ad blockers, privacy-first browsers and cookie restrictions reduce data quality.
Server-side tracking moves data collection from the browser to the server, making tracking more reliable and complete.
This is perfectly aligned with the shift of digital marketing towards AI-driven models, as also explained in the article
Zero-Click Search: AI is eating clicks.
- more complete conversion data
- better signal quality for Google Ads
- greater resilience to privacy restrictions
It is no longer an advanced solution: it is the new baseline for anyone who wants to drive performance.
We covered the complete server-side tracking configuration in a dedicated article, with technical implementation, concrete use cases and measurable results on real ecommerce projects.
We also explain what Stape is.
Data Studio: the 3 ecommerce reports to build
GA4 offers useful native reports, but for an ecommerce business the most important data is easier to read in Data Studio, where it is possible to combine different sources, build custom visualisations and share updated dashboards with marketing, leadership and ecommerce teams.
Report 1 — Purchase funnel performance
The first report should show the full funnel: view_item → add_to_cart → begin_checkout → purchase, with the conversion rate at each step and the variation compared with the previous period.
This report answers the most important question for an ecommerce business:
where are we losing users?
- Main metric: conversion rate by funnel step.
- Segmentation: device, acquisition channel, product category.
- Automatic alert: when the
begin_checkout → purchaserate drops below the threshold.
Report 2 — Category and product analysis
The second report should show product performance: views, add-to-cart rate, generated revenue, refund rate and category trends.
With GA4 Enhanced Ecommerce, these metrics can be read by category, brand, variant, list position and traffic source.
This is the report that helps distinguish a traffic problem from a product, pricing or product-page problem.
- Main metric: revenue, add-to-cart rate and product conversion rate.
- Segmentation: category, brand, variant, device, source/medium.
- Automatic alert: when a high-traffic category has an add-to-cart rate below the site average.
Report 3 — Attribution and conversion channels
The third report should show the contribution of channels to conversions, using GA4’s data-driven attribution model.
This makes it possible to evaluate the real weight of touchpoints in the purchase journey, not just the last click before conversion.
- Main metric: conversions, revenue and attributed value by channel.
- Segmentation: paid search, organic search, paid social, email, direct, referral.
- Automatic alert: when a channel grows in cost but not in attributed value.
Use GA4’s data-driven attribution model instead of last-click only.
Last-click tends to overvalue paid search and undervalue higher-funnel channels such as display, video, social and editorial activities.
This approach is especially useful when an ecommerce business invests in advertising, SEO and content together.
In a context where organic traffic is increasingly influenced by AI Overview and zero-click search, the dashboard must measure not only the last click, but the overall contribution of touchpoints.
On this topic, you can also read the article
Zero-Click Search: AI is eating clicks.
The 6 most common errors in GA4 ecommerce configuration
After analysing numerous ecommerce accounts, these are the errors we encounter most often and the ones with the greatest impact on data quality.
Error 1 — Purchase event triggered multiple times
The purchase tag fires every time the order confirmation page is reloaded.
The result is inflated conversion and revenue numbers.
Use transaction_id for deduplication, or check in GTM that the event is sent only once.
Error 2 — Missing or incorrect currency parameter
Without currency, GA4 cannot normalise values correctly.
In multi-currency environments, this makes revenue metrics unreliable.
Error 3 — dataLayer not reset between events
Failing to reset the dataLayer leads to data contamination between consecutive events, especially when multiple products are added to the cart in sequence.
Error 4 — Internal traffic not excluded
Traffic from the team (marketing, development, office staff) alters metrics,
especially on ecommerce sites with medium-low traffic.
1. Define Internal Traffic (Identify the IP)
Administration > Property > Data Streams > Select web stream >
Configure tag settings > Define internal traffic > Create >
Assign a name (e.g. “Office”), keeping traffic_type as internal >
Enter the IP address to exclude > Create
Click the default Internal Traffic filter >
Select Active under filter state > Save
For teams working remotely, IP exclusion is not always enough.
In these cases, it is possible to use a GTM variable that marks internal traffic based on a verifiable condition, such as the logged-in user’s email domain, an internal technical cookie, a private URL parameter or an account-area rule.
The goal is not to theoretically remove all “non-customer” traffic, but to reduce the impact of sessions generated by marketing, development, customer care and site administrators, especially during tests, launches, promotions and checkout changes.
Error 5 — Bot sessions not filtered
Although GA4 automatically excludes known bots through IAB/ABC lists, many custom crawlers or automated systems are not detected.
In these cases, additional controls are required, for example through Google Tag Manager, IP filters, server-side validations or custom rules.
Error 6 — Inconsistent UTM parameters
With native social cost integration, using utm_source=fb in one campaign and utm_source=facebook in another is no longer just an aesthetic issue: it breaks GA4’s automatic ROAS calculation.
“The most common issue we find in GA4 audits is false confidence.
The account appears to work, the numbers are there, but nobody has ever verified whether those numbers reflect reality.
A purchase counted twice creates inflated ROAS and wrong decisions.”
Not a technical person? Here is what you need to know
This guide is intentionally technical, but not everyone needs to implement it directly.
If you are a marketing manager, entrepreneur or ecommerce manager,
the real value is understanding what to check, not writing code.
What you need to understand, even without touching code
-
GA4 does not work automatically on its own.
It requires active configuration through GTM and dataLayer.
If nobody explicitly configured it, the data you are reading is probably incomplete. -
Data will never match your CRM 100%, but discrepancies should remain under control.
If there are major gaps, there is a configuration problem. -
Google Ads campaigns optimise based on conversion data.
Wrong data means campaigns optimise towards the wrong objective:
wrong data = wasted budget. -
Consent Mode v2 is mandatory in Europe.
If your website does not have it configured, you are collecting data in a non-compliant way.
If this is not clear, it is worth exploring web analytics as a strategic business lever, not just a technical activity.
What should be delegated
GA4 ecommerce configuration requires expertise in:
- Google Tag Manager
- dataLayer
- ecommerce platforms (Shopify, Magento, WooCommerce)
- Google Ads and Social Ads integrations
Without experience, the risk is not that it will fail.
The risk is that it appears to work while generating misleading data.
And this is how many companies do not lose data:
they lose margin, budget and competitiveness.
Do you have doubts about your GA4 setup?
HT&T Consulting is among the agencies certified on Google Marketing Platform, with experience on complex ecommerce projects and integrations between GA4, Google Ads and server-side tracking.
If you want to verify the quality of your data or improve campaign performance, you can request an audit:
Checklist: what to verify before going live
Before considering a GA4 ecommerce setup reliable, verify these points:
- GTM installed on all pages (head + body)
- Consent Mode v2 configured and tested with active CMP
- Ecommerce dataLayer available
- dataLayer reset before every push
- Complete purchase event (transaction_id, value, currency, items)
- Purchase deduplication verified
- Complete funnel events
- Advanced parameters configured
- Purchase set as a conversion
- GA4 → Google Ads connection active
- No duplicated conversions
- Social cost data integration (Meta, TikTok, etc.) active
- Internal traffic excluded
- GTM tested across multiple browsers
- DebugView verified with a real purchase
If even 2–3 of these points are not correct, data quality is compromised.
And without reliable data, no SEO, AEO, GEO, Ads or AI strategy can truly work.
This is why analytics is now central to visibility in AI search engines as well, as explored in our guide SEO, GEO and AI.
Frequently asked questions about GA4 ecommerce
Is GA4 mandatory for an ecommerce business?
Universal Analytics has been discontinued and GA4 is now the reference platform for businesses using Google Analytics.
It is not legally mandatory, but it is the operational standard for ecommerce businesses that want to measure sales,
funnel performance and Google Ads campaigns.
Can I use GA4 without Google Tag Manager?
Yes, but it is not recommended for ecommerce.
Google Tag Manager allows you to manage events, dataLayer, conversions and tests without changing site code every time.
On dynamic catalogues, it is practically essential.
How much historical data migrates from Universal Analytics to GA4?
None automatically.
GA4 and Universal Analytics are separate properties.
Anyone who wanted to preserve historical UA data had to export it before the platform was permanently discontinued.
How do I verify that ecommerce tracking works correctly?
The most reliable method is using GA4 DebugView together with Google Tag Manager Preview mode.
A complete test purchase should be performed, verifying that
transaction_id, value, currency and items
are populated correctly.
Is GA4 compatible with Shopify, WooCommerce and Magento?
Yes, all major ecommerce platforms can integrate GA4 through apps, plugins,
extensions or custom configurations.
However, dataLayer quality varies significantly, and customisation is often required
for advanced parameters such as
item_list_name, coupon or shipping_tier.
When does server-side tracking make sense for GA4?
It makes sense when there are significant discrepancies between real orders and GA4 conversions,
when the site receives relevant traffic from privacy-first browsers,
or when data quality is critical for Google Ads optimisation.
For medium to high-volume ecommerce businesses, server-side tracking is often a strategic choice.
How do you connect GA4 data to Google Ads correctly?
The connection is managed in GA4 through Google product links.
Once connected, GA4 conversions can be imported into Google Ads and used for Smart Bidding.
It is essential to avoid duplication: each action should have only one primary conversion source.
Which GA4 events are essential for ecommerce?
The minimum events are
view_item, add_to_cart,
begin_checkout and purchase.
Additional events such as
view_item_list, select_item,
add_shipping_info and add_payment_info
provide a more complete funnel analysis.
Why can the purchase event appear duplicated in GA4?
This usually happens when the tag fires every time the thank-you page reloads,
or when multiple tracking systems coexist.
To prevent this, use transaction_id,
verify GTM trigger conditions and check that there are no duplicated
Google Ads and GA4 tags for the same conversion.
Can GA4 replace ERP or CRM data?
No.
GA4 is designed to analyse behaviour, channels, funnel performance and attribution,
while CRM and ERP remain the primary source for orders, revenue, margins and customers.
Data will never match 100%, but large discrepancies almost always indicate a configuration issue.
References and useful resources
Technical sources and official documentation used to deepen topics such as
GA4 configuration, ecommerce tracking, Consent Mode, BigQuery and server-side tagging.
Google Developers
Measure ecommerce
Official documentation on GA4 ecommerce events, items arrays,
products, promotions and revenue.
Google Analytics Help
Recommended events
Google’s recommended events for measuring online sales,
ecommerce funnels and purchase interactions.
Google Developers
Set up a purchase event
Official guide to configuring the purchase event
for measuring ecommerce transactions in GA4.
Google Tag Platform
Consent Mode
Official documentation on Consent Mode and the Consent Mode v2 update
for Google tags.
Google Ads Help
Updates to Consent Mode for EEA traffic
Google’s official documentation on Consent Mode updates
for traffic coming from the European Economic Area.
Google Developers
Server-side Tag Manager
Official introduction to server-side tagging with Google Tag Manager:
data quality, performance and privacy controls.
Google Developers
BigQuery Export for Google Analytics
Documentation on exporting raw GA4 events to BigQuery
for advanced analysis and data warehouse integration.
Google Analytics Help
Set up ecommerce events
Google’s guide on collecting ecommerce data through website,
app or Google Tag Manager events.
Continua a leggere
20 minutes of reading
21 minutes of reading
17 minutes of reading
And it consumes less energy.
To return to the page you were visiting, simply click or scroll.