Google Analytics 4 Gives eCommerce Stores Event-Level Data That Universal Analytics Never Could
Google Analytics 4 (GA4) replaced Universal Analytics as Google's default measurement platform in July 2023. For eCommerce store owners, that shift matters because GA4 tracks every customer interaction as a discrete event, not a session-based pageview. That means you can measure add_to_cart, begin_checkout, and purchase as individual data points, then build funnels around them without writing custom SQL or buying a separate analytics tool.
This guide walks through the exact steps to install GA4, configure eCommerce tracking, and pull reports that actually inform decisions. No filler. Just the mechanics.
Step 1: Create Your GA4 Property and Install the Base Tag
Log into Google Analytics, open the Admin panel, and click Create Property. Name it after your store, set the correct time zone and currency, and select your industry category. Google uses the industry setting to populate benchmark data in your reports, so pick the closest match rather than leaving it as "Other."
Once the property exists, you need the Measurement ID (formatted as G-XXXXXXXXXX). There are two clean ways to get it onto your site:
- Google Tag Manager (GTM): Create a GA4 Configuration tag in GTM, paste your Measurement ID, and set the trigger to "All Pages." This is the recommended approach because it keeps your tag logic in one place and lets you add new events without touching your theme code.
- Native platform integrations: Shopify's Online Store 2.0, BigCommerce's native analytics settings, and WooCommerce via the Site Kit plugin all support direct GA4 Measurement ID entry. These integrations handle the base tag automatically, but they give you less control over custom event parameters.
After installation, use the GA4 DebugView (Admin > DebugView) to confirm the tag fires on page load before moving to purchase tracking. DebugView shows every event in real time, which makes it far easier to catch misfires than waiting 24 hours for processed data.
Step 2: Enable Enhanced eCommerce Event Tracking
GA4's eCommerce model is built on a standardized set of events. The ones that matter most for a retail store are listed below in the order a customer encounters them:
| GA4 Event Name | What It Tracks | Required Parameters |
|---|---|---|
| view_item | Product detail page viewed | item_id, item_name, price, currency |
| add_to_cart | Item added to cart | item_id, item_name, quantity, price, currency |
| begin_checkout | Checkout page opened | value, currency, items array |
| add_payment_info | Payment method entered | payment_type, value, currency |
| purchase | Transaction completed | transaction_id, value, tax, shipping, currency, items array |
On Shopify, install the Google & YouTube channel app. It pushes these events through the Shopify pixel automatically, though you should verify that the transaction_id passes correctly and is not duplicated by a secondary GTM tag. Running two tags simultaneously is the most common cause of inflated GA4 revenue data.
On WooCommerce, the free WooCommerce Google Analytics Integration plugin handles the data layer pushes. Pair it with GTM for the cleanest setup. Confirm the purchase event fires on the order confirmation page, not on the payment gateway redirect, or you will lose conversions that bounce back slowly.
On BigCommerce, use the built-in Google Analytics 4 connection under Store Setup > Analytics. It maps standard eCommerce events automatically. For stores with custom checkout flows, you will need GTM and a custom data layer to capture events that happen outside the native checkout.
Step 3: Configure Conversions and Custom Dimensions
GA4 does not mark any event as a conversion by default, including purchase. Navigate to Admin > Conversions, click New Conversion Event, and type the exact event name: purchase. Capitalization matters. Then add begin_checkout as a second conversion so you can measure checkout abandonment rate as the gap between the two.
Custom dimensions let you attach store-specific data to sessions and events that GA4 does not capture natively. Useful examples for eCommerce include:
- Product category: Pass the top-level category (e.g., "Running Shoes") as an event-scoped custom dimension on view_item and add_to_cart. This lets you filter your funnel reports by category, which reveals whether checkout abandonment is a site-wide problem or isolated to a specific product line.
- Customer type: Tag sessions as "new" or "returning" based on a first-party cookie or your CRM data. GA4 has a built-in new/returning dimension, but a custom one tied to your own login data is more accurate for stores with account systems.
- Discount code applied: Capture whether a coupon was used during checkout. This helps you measure whether promotions are acquiring new customers or just discounting purchases that would have happened anyway.
Custom dimensions are configured under Admin > Custom Definitions. Event-scoped dimensions are the most flexible for eCommerce; user-scoped dimensions persist across sessions and work well for lifetime value segmentation.
Step 4: Build Reports That Drive Decisions
GA4's default reports give you traffic and revenue summaries, but the real value comes from the Explore section, which lets you build custom funnels and segment reports without exporting to a spreadsheet.
Start with a Funnel Exploration using these five steps: session start, view_item, add_to_cart, begin_checkout, purchase. GA4 shows the drop-off percentage between each step. A drop-off above 70% between add_to_cart and begin_checkout typically points to a cart page problem: unexpected shipping costs, a required account creation, or a slow-loading cart drawer. A drop-off above 60% between begin_checkout and purchase usually signals a payment friction issue.
Next, build a Segment Overlap report to compare organic search users, paid search users, and email users across the same funnel. This shows not just which channel drives the most traffic, but which drives the highest-converting traffic. Many small stores discover that email converts at 3x the rate of paid search, which argues for investing in list growth rather than increasing ad spend.
Connect GA4 to Google Search Console via the Link settings in Admin. Once linked, the Search Console reports inside GA4 show which organic queries led to sessions that converted, letting you identify commercial-intent keywords worth targeting in your SEO foundation content strategy.
Step 5: Avoid the Three Most Damaging GA4 Mistakes
Setup errors corrupt your data and lead to wrong decisions. These are the three that appear most often in eCommerce accounts:
- Not filtering internal traffic: If you or your team browse and test the store regularly, those sessions inflate your data and suppress your conversion rate. Create an Internal Traffic definition under Admin > Data Streams > Configure Tag Settings, add your office and home IP addresses, and then create a Data Filter to exclude them from reports.
- Duplicate purchase events: As noted above, Shopify stores that use both the Google channel app and a GTM-based GA4 tag often fire purchase twice per transaction. Check your DebugView after a test purchase and confirm only one purchase event fires. If you see two, disable one of the tags entirely.
- Ignoring data retention settings: GA4 defaults to 2-month event data retention for exploration reports. Change it to 14 months under Admin > Data Settings > Data Retention. The change is not retroactive, so set it on day one. Without this adjustment, year-over-year comparisons in Explore will be incomplete.
Google Analytics 4 eCommerce FAQ
Does GA4 track revenue accurately out of the box on Shopify?
Not always. The Google & YouTube Shopify channel passes revenue data automatically, but it uses the order total including taxes by default. GA4's purchase event expects the value parameter to reflect revenue excluding tax. Confirm which your setup sends by comparing GA4 reported revenue against your Shopify order totals. If they match exactly, taxes are likely included and your revenue metric is overstated.
Can I use GA4 without Google Tag Manager?
Yes. Native integrations on Shopify, BigCommerce, and WooCommerce install the base tag and standard eCommerce events without GTM. GTM becomes necessary when you need custom event parameters, discount code tracking, or third-party tag management. For simple stores with no custom tracking requirements, the native integration is sufficient.
How long does it take for GA4 data to appear after setup?
Standard reports update with a 24–48 hour delay. Real-time reports and DebugView show data within seconds. For the first week after setup, use DebugView to confirm your events are firing correctly before trusting the standard reports.
What is the difference between GA4 sessions and events?
A session is a group of interactions a user takes within a given time frame, starting with a session_start event and ending after 30 minutes of inactivity by default. Events are every individual interaction within that session: page views, clicks, scrolls, and eCommerce actions. GA4's event-based model means you can analyze individual interactions without session boundaries distorting your funnel data, which was a significant limitation in Universal Analytics.
Should I connect GA4 to Google Ads?
Yes, and do it before you run any paid campaigns. Linking GA4 to Google Ads under Admin > Google Ads Links imports GA4 conversions into Ads and enables audience sharing. This lets Google's bidding algorithms optimize toward actual purchases rather than just landing page visits, which typically improves return on ad spend for eCommerce campaigns running Target ROAS or Maximize Conversion Value bid strategies.
