GA4 for e-commerce: the direct answer
Configuring GA4 for e-commerce means implementing structured events that capture the full customer journey, from product views to purchase, ensuring revenue, conversions and funnel performance are measured accurately.
Without a correct setup, marketing, performance and growth decisions are made using incomplete or incorrect data.
Why tracking is critical in e-commerce
In an e-commerce project, data is infrastructure. It is as important as the platform, ERP integration or logistics.
If you do not measure correctly, you do not know:
Direct impact of incorrect tracking
- Inflated or underestimated ROAS.
- Campaigns optimised for the wrong events.
- A funnel with invisible drop-offs.
- Stock decisions based on inaccurate data.
- Difficulty scaling internationally.
Tracking is not a technical detail. It is a strategic foundation.
What should be measured in e-commerce
GA4 uses an event-based model. For e-commerce, there is a recommended set of events that structure the funnel.
Essential e-commerce events
- view_item
- view_item_list
- add_to_cart
- begin_checkout
- add_shipping_info
- add_payment_info
- purchase
Each event should include critical parameters such as item_id, item_name, price, quantity, currency and value.
Without these parameters, revenue and performance analysis is compromised.
Step 1: Create and configure the GA4 property
The first step is to create a GA4 property in Google Analytics and set up a web data stream.
Mandatory initial settings
- Enable Enhanced Measurement.
- Set the correct default currency.
- Configure the business time zone.
- Enable Google Signals if applicable.
Mistakes at this stage affect every future report.
Step 2: Implementation via Google Tag Manager
While it is possible to install GA4 directly in the code, the recommended approach is to use Google Tag Manager.
This provides flexibility, version control and scalability.
Benefits of GTM
- Centralised script management.
- Easier testing and debugging.
- Integration with advertising pixels.
- Consent management.
In a Shopify environment, this approach is especially relevant when there are advanced integrations, such as ERP integration and API integration, where data consistency is critical.
Step 3: Implement e-commerce events correctly
The most common mistake is relying only on the platform’s native integration without validating the parameters being sent.
Technical best practices
- Ensure item_id matches the real SKU.
- Send the total purchase value without duplicate tax inclusion.
- Ensure currency consistency.
- Avoid duplication of the purchase event.
Event duplication is one of the biggest problems in e-commerce, especially when additional scripts or external integrations are present.
Step 4: Validate in DebugView
After implementation, never assume it is correct. Validate it.
Validation checklist
- Verify the correct event sequence across the funnel.
- Confirm values and currency.
- Test a real purchase in a controlled environment.
- Check for duplicated events.
GA4 DebugView is the core tool at this stage.
Conversion funnel in GA4
With the right events, you can build custom funnels that show where users drop off.
Example of a basic funnel
- view_item
- add_to_cart
- begin_checkout
- purchase
This funnel helps identify UX, performance or trust issues.
Teams investing in E-commerce UX and UI use this data to optimise conversion.
Integration with Google Ads and performance
GA4 is not only reporting. It is the optimisation foundation for campaigns.
Critical settings
- Import conversions correctly into Google Ads.
- Set purchase as the primary conversion.
- Ensure consistency between GA4 and Ads.
Without this connection, Google Ads for e-commerce campaigns can optimise against incorrect data.
Server-side tracking: when it makes sense
With cookie blockers and privacy restrictions, client-side tracking can lose data.
Server-side tracking reduces event loss and improves data quality.
When to consider server-side
- High volume of paid traffic.
- Strong dependency on performance marketing.
- Markets with stricter privacy requirements.
This approach requires solid technical infrastructure, often supported by high-performance cloud solutions.
Common mistakes in GA4 configuration
Most issues come from rushed, undocumented implementations.
Frequent errors
- Purchase firing twice.
- Events missing required parameters.
- Mixed currencies in the same property.
- No internal traffic filtering.
- Payment gateways not excluded as referrals.
Essential metrics for analysis
With correct tracking, these metrics become reliable.
Critical indicators
- Revenue by channel.
- Conversion rate.
- Average order value.
- Checkout abandonment.
- Estimated lifetime value.
The analysis of these metrics should align with a growth and ROI strategy, not isolated reporting.
GA4, AEO and data-driven decisions
In a context of Answer Engine Optimization and AI-based engines, structured and consistent data is essential.
Companies that structure tracking properly can identify patterns, automate decisions and feed performance dashboards with confidence.
Conclusion: tracking is infrastructure, not configuration
Configuring GA4 for e-commerce is not adding a script. It is designing a data architecture that supports marketing, operations and growth.
When implemented well, GA4 becomes a strategic tool. When configured poorly, it becomes a source of noise.
In e-commerce, the right decisions start with the right data.