GA4 Not Tracking WooCommerce Ecommerce Events

GA4 Not Tracking WooCommerce Ecommerce Events? Fix Add to Cart and Purchase Tracking

by

Google Analytics 4 may successfully record page views and visitors from a WooCommerce website while failing to show ecommerce events such as view_item, add_to_cart, begin_checkout, and purchase.

This often leads website owners to believe that GA4 is connected correctly because Realtime reports show active users. However, basic GA4 page tracking and WooCommerce ecommerce tracking are not the same thing.

Installing a plugin that adds the Google Analytics tag does not necessarily mean that the plugin also sends WooCommerce product, cart, checkout, and transaction data.

This guide explains why GA4 is not tracking WooCommerce ecommerce events and how to restore add-to-cart, checkout, and purchase tracking.

Symptoms of Missing Ecommerce Tracking

You may have an ecommerce tracking problem when:

  • GA4 records page views but no product activity.
  • Product pages do not generate view_item events.
  • Clicking Add to Cart does not generate add_to_cart.
  • Checkout visits appear as page views but not begin_checkout.
  • Completed orders are not appearing as purchase events.
  • Revenue remains at zero in GA4.
  • The Monetization or Ecommerce reports are empty.
  • WooCommerce reports sales correctly, but GA4 does not.
  • Only events such as page_view, session_start, and user_engagement appear.

In most cases, the GA4 base tag is working, but the ecommerce event implementation is missing, disabled, blocked, or misconfigured.

Why GA4 Does Not Track Ecommerce Events Automatically

GA4 automatically collects some general website events after its tag is installed. WooCommerce actions, however, must be sent using GA4’s recommended ecommerce event names and parameters.

Google’s ecommerce specification includes events such as:

  • view_item_list
  • select_item
  • view_item
  • add_to_cart
  • remove_from_cart
  • view_cart
  • begin_checkout
  • add_shipping_info
  • add_payment_info
  • purchase
  • refund

These events should include product information inside an items array. Revenue-related events should also include values such as currency, transaction ID, price, and quantity.

A plugin that only inserts this type of base configuration:

gtag('config', 'G-XXXXXXXXXX');

may track normal visits without sending any WooCommerce ecommerce events.

You therefore need one of the following:

  1. A WooCommerce analytics plugin that explicitly supports GA4 ecommerce tracking.
  2. A Google Tag Manager implementation connected to a WooCommerce data layer.
  3. A custom implementation that sends GA4 ecommerce events programmatically.

Do not use all three methods at the same time unless they have been deliberately configured to avoid duplicate events.

Step 1: Confirm That Basic GA4 Tracking Works

Before troubleshooting ecommerce events, confirm that the correct GA4 property is receiving normal website activity.

In Google Analytics:

  1. Open Admin.
  2. Select Data Streams.
  3. Open the website’s web data stream.
  4. Copy the Measurement ID.

A GA4 Measurement ID begins with:

G-

For example:

G-ABC1234567

Compare this with the ID entered in your WordPress analytics plugin.

When using the official Google Analytics for WooCommerce extension, the Measurement ID is configured under:

WooCommerce > Settings > Integration > Google Analytics

WooCommerce’s documentation confirms that this field requires the GA4 Measurement ID beginning with G-.

Next, open the website in a private browser window and check:

Google Analytics > Reports > Realtime

If your visit appears, the base GA4 tag is probably working.

If it does not appear, fix the main GA4 connection before troubleshooting ecommerce events.

Step 2: Check Whether Your Plugin Supports Ecommerce Tracking

Not every Google Analytics plugin supports WooCommerce ecommerce tracking.

Some plugins only add the GA4 tracking code. Others provide dedicated WooCommerce event tracking for product views, cart actions, checkout steps, and completed orders.

Open the plugin’s settings and look for options such as:

  • Ecommerce tracking
  • Enhanced ecommerce
  • WooCommerce integration
  • Add to Cart tracking
  • Purchase transaction tracking
  • Product impression tracking
  • Checkout tracking
  • GA4 ecommerce events

If none of these settings exist, the plugin may not provide WooCommerce ecommerce tracking.

In that situation, installing the GA4 Measurement ID alone will not generate add_to_cart or purchase events. You will need a WooCommerce-aware analytics integration or a Google Tag Manager implementation.

Step 3: Enable the WooCommerce Tracking Options

When using the official Google Analytics for WooCommerce extension, go to:

WooCommerce > Settings > Integration > Google Analytics

Confirm that the correct Measurement ID has been added and enable the available ecommerce options.

Depending on the plugin version, these may include:

  • Purchase Transactions
  • Add to Cart Events
  • Remove from Cart Events
  • Product Impressions from Listing Pages
  • Product Clicks from Listing Pages
  • Product Detail Views
  • Checkout Process Initiated

WooCommerce documents these as separate tracking options. They may not all be active merely because the Measurement ID has been entered.

Save the settings and clear all website caches.

Step 4: Avoid Multiple GA4 Implementations

A common WordPress problem is loading the same GA4 property through multiple sources.

For example, GA4 may be added through:

  • A WordPress analytics plugin
  • Google Tag Manager
  • The theme’s header settings
  • A code-snippet plugin
  • A cookie-consent plugin
  • A WooCommerce analytics extension
  • Custom code in header.php
  • A hosting or marketing integration

Multiple tracking implementations can cause duplicate page views, duplicate purchases, inconsistent parameters, or events being overridden. WooCommerce specifically warns that multiple tracking instances can cause analytics problems.

Search the page source for:

G-

You can also open the browser console and run:

document.documentElement.innerHTML.match(/G-[A-Z0-9]+/g);

This may reveal GA4 IDs printed in the page HTML.

For a more reliable test, use Google Tag Assistant and check how many Google tags are loading.

There should normally be one intentional GA4 implementation per property. A single Google Tag Manager container can send data to GA4, but you should not also send the same ecommerce events through another plugin.

Step 5: Test Using Google Tag Assistant

Do not rely only on the standard GA4 reports while troubleshooting. Some reports require processing time before events appear.

Google Tag Assistant can show whether an event is actually sent from the browser.

To test:

  1. Open Google Tag Assistant.
  2. Enter your website URL.
  3. Click Connect.
  4. Accept analytics consent on the website.
  5. Open a product page.
  6. Add the product to the cart.
  7. View the cart.
  8. Start checkout.
  9. Complete a test order.
  10. Review the events detected by Tag Assistant.

WooCommerce recommends simulating actions such as adding products to the cart and beginning checkout, then checking the hits sent through Tag Assistant.

You should see events such as:

view_item
add_to_cart
view_cart
begin_checkout
purchase

If Tag Assistant does not detect them, the problem is on the website or plugin side. Waiting for GA4 reports will not fix it.

Step 6: Use GA4 DebugView

GA4 DebugView displays events generated by a device running in debug mode.

Open:

Google Analytics > Admin > Data Display > DebugView

Depending on the current GA4 interface, DebugView may also be accessible from the property’s data-display or events area.

With Tag Assistant connected, perform the ecommerce actions again.

Look for:

view_item
add_to_cart
begin_checkout
purchase

Click an event to inspect its parameters.

Google recommends enabling debug mode while implementing ecommerce tracking so events can be reviewed during testing.

Step 7: Verify the Add-to-Cart Event

When a customer adds a product, GA4 expects an event named:

add_to_cart

The event should contain product information inside an items array.

A correctly formatted event resembles:

gtag('event', 'add_to_cart', {
    currency: 'USD',
    value: 49.00,
    items: [
        {
            item_id: 'PRODUCT-123',
            item_name: 'Example Product',
            price: 49.00,
            quantity: 1
        }
    ]
});

This is an example only. Do not add it directly to your site without replacing the static values with dynamic WooCommerce product data.

Google’s specification requires the relevant product information to be sent with the add_to_cart event.

When add_to_cart does not fire, check whether:

  • The event-tracking option is enabled.
  • The theme uses a custom Add to Cart button.
  • AJAX Add to Cart has been modified.
  • A quick-view plugin handles the cart action.
  • A page builder replaces the standard WooCommerce button.
  • JavaScript errors stop the tracking listener.
  • The cart action occurs through custom code that the analytics plugin does not recognize.

Temporarily test with a standard WooCommerce product template. If tracking works there but not with the custom product layout, the custom button or AJAX implementation is probably bypassing the plugin’s expected WooCommerce event.

Step 8: Verify the Purchase Event

The GA4 purchase event should be named:

purchase

It should contain at least a unique transaction ID and product information.

A typical structure resembles:

gtag('event', 'purchase', {
    transaction_id: 'ORDER-1001',
    value: 99.00,
    tax: 0,
    shipping: 5.00,
    currency: 'USD',
    items: [
        {
            item_id: 'PRODUCT-123',
            item_name: 'Example Product',
            price: 94.00,
            quantity: 1
        }
    ]
});

Google’s ecommerce documentation shows that a purchase event normally includes transaction_id, value, currency, and an items array.

The transaction ID is particularly important because it helps GA4 identify the order.

Why Purchase Tracking Commonly Fails

Many WooCommerce integrations trigger the purchase event on the order-received or thank-you page.

That means the customer must return to a URL similar to:

/checkout/order-received/

If an external payment gateway completes the payment but does not return the customer to the order-received page, the browser-based purchase event may never fire.

WooCommerce notes that purchase tracking requires a payment gateway that redirects the customer to the thank-you or order-received page after payment.

Complete a test order and confirm:

  • Payment succeeds.
  • The order is created in WooCommerce.
  • The customer returns to the WooCommerce order-received page.
  • Tag Assistant detects purchase.
  • The event includes the correct transaction ID.
  • The purchase fires only once.

Refreshing the order-received page should not generate repeated purchases. A reliable integration should prevent the same transaction from being counted multiple times.

Step 9: Check Cookie Consent

A cookie-consent plugin may prevent analytics events from firing until the visitor accepts analytics cookies.

This is especially important for visitors in the European Economic Area, the United Kingdom, and Switzerland.

WooCommerce explains that analytics data may not be captured until the visitor grants consent. Its Google Analytics extension integrates with the WordPress Consent API but does not itself provide the visible cookie banner.

During testing:

  1. Open an incognito window.
  2. Accept the analytics category in the cookie banner.
  3. Open Tag Assistant.
  4. Perform the ecommerce actions.
  5. Check whether the consent state changes from denied to granted.

Common consent-related problems include:

  • The banner never updates Google Consent Mode.
  • Analytics remains denied after clicking Accept.
  • Only marketing consent is granted, not analytics consent.
  • The consent plugin blocks the ecommerce script completely.
  • Cached consent settings are outdated.
  • The plugin is not compatible with the WordPress Consent API.

Test once with consent granted. Do not permanently disable legal consent controls merely to make analytics work.

Step 10: Test While Logged Out

Some analytics plugins intentionally exclude logged-in administrators to avoid contaminating reporting data.

Testing while logged in may therefore produce no page-view or ecommerce events.

WooCommerce advises testing while logged out and notes that page views may not be tracked for logged-in administrators.

Use:

  • An incognito browser window
  • A separate browser
  • A non-administrator test account
  • A mobile device without a WordPress login session

Also temporarily disable browser extensions that block analytics.

Step 11: Check for JavaScript Errors

Ecommerce tracking usually depends on JavaScript.

Open the website in Chrome, press F12, and select the Console tab.

Look for errors such as:

Uncaught ReferenceError: gtag is not defined
Uncaught TypeError
Failed to load resource
Refused to execute script

Any JavaScript error occurring before the ecommerce tracking code may prevent the event from firing.

WooCommerce identifies JavaScript errors and browser ad blockers as possible causes of missing analytics data.

Temporarily disable:

  • JavaScript delay
  • Script defer settings
  • Combine JavaScript
  • Aggressive minification
  • Google Analytics script delay
  • Consent-script optimization
  • Rocket Loader
  • Third-party tag blocking

Clear every cache layer and test again.

When tracking begins working after optimization is disabled, exclude the analytics and ecommerce scripts from that optimization feature rather than leaving all optimization disabled.

Step 12: Check AJAX and Custom WooCommerce Templates

Custom themes and page builders may replace standard WooCommerce elements.

An analytics plugin may listen for standard WooCommerce JavaScript events. If the custom Add to Cart button does not trigger those events, analytics will not know that an item was added.

Potential sources include:

  • Elementor custom product templates
  • Custom AJAX cart buttons
  • Quick-view plugins
  • Side-cart plugins
  • Product bundle plugins
  • Subscription plugins
  • Headless WooCommerce frontends
  • Custom checkout plugins
  • One-page checkout systems
  • Buy Now buttons that skip the cart

Test a basic WooCommerce product with the standard theme template.

If the standard product tracks successfully, the issue is likely a compatibility problem between the analytics integration and the customized product or checkout flow.

Step 13: Check the Network Request

Open Chrome Developer Tools and select Network.

Filter the requests using:

collect

Perform an Add to Cart action.

GA4 browser events are normally sent through requests involving a Google Analytics collection endpoint. Open the request and inspect its query string or payload.

Look for an event name such as:

en=add_to_cart

For a completed order, look for:

en=purchase

The exact request structure can change, but this test helps establish whether the browser attempted to send the event.

The results mean:

  • No request: The website did not generate the event.
  • Request blocked: A consent tool, browser extension, firewall, or security policy blocked it.
  • Wrong Measurement ID: The event was sent to another GA4 property.
  • Request sent successfully: Check DebugView and allow time for standard reports to process it.

Step 14: Clear All Cache Layers

After changing analytics settings, clear:

  • The WordPress cache
  • The server cache
  • Varnish
  • Redis object cache when relevant
  • Cloudflare or another CDN
  • Browser cache
  • Minified JavaScript files
  • Consent-plugin cache

Old cached JavaScript may continue loading the previous analytics configuration after the settings have been corrected.

Test again in a fresh incognito session.

Step 15: Check the Correct GA4 Reports

Do not search only for an “Add to Cart” report immediately after testing.

Start with:

Reports > Realtime

Then check:

Admin > DebugView

After processing, ecommerce data should appear in reports related to monetization, purchases, products, or events.

The GA4 event names use underscores:

add_to_cart
begin_checkout
purchase

They will not necessarily appear as:

Add to Cart
Checkout Started
Order Completed

Standard reports can take longer to populate than Realtime and DebugView. WooCommerce recommends using realtime reports during testing and allowing additional time for regular analytics reporting.

Recommended Troubleshooting Order

Use this order to avoid unnecessary changes:

  1. Confirm that the GA4 Measurement ID is correct.
  2. Verify normal page views in Realtime.
  3. Confirm that the plugin supports WooCommerce ecommerce tracking.
  4. Enable the plugin’s ecommerce options.
  5. Remove duplicate GA4 implementations.
  6. Accept analytics consent.
  7. Test while logged out.
  8. Connect Google Tag Assistant.
  9. Test view_item and add_to_cart.
  10. Complete a test purchase.
  11. Confirm the return to the order-received page.
  12. Inspect GA4 DebugView.
  13. Check browser console errors.
  14. Disable script optimization temporarily.
  15. Test with a standard WooCommerce template.
  16. Clear every cache layer.

When the Plugin Does Not Support Ecommerce Events

If the current plugin only installs the Google tag, you have three practical choices.

Use a WooCommerce-Specific GA4 Integration

Choose an integration that explicitly supports WooCommerce and sends GA4-recommended ecommerce events.

Before installing it, remove or disable any overlapping ecommerce tracking from the previous solution.

Use Google Tag Manager

A Google Tag Manager implementation normally requires:

  • A WooCommerce data layer
  • GA4 event tags
  • Triggers for product and checkout actions
  • Ecommerce variable mapping
  • Transaction deduplication
  • Consent Mode configuration
  • Testing through Tag Assistant

This provides greater control but requires careful configuration.

Build a Custom Integration

A custom solution can send events using WooCommerce hooks and frontend JavaScript.

This may be necessary for:

  • Custom checkouts
  • Headless websites
  • Nonstandard cart systems
  • Bespoke product builders
  • Payment flows that do not return to WooCommerce
  • Server-side purchase tracking

Custom tracking should follow Google’s recommended event names and parameter structure.

Final Recommendation

When GA4 tracks website visitors but does not show add_to_cart or purchase, the base Google Analytics tag is usually installed but the WooCommerce ecommerce implementation is incomplete.

First, confirm that your analytics plugin explicitly supports WooCommerce ecommerce events. Enter the correct GA4 Measurement ID, enable all required product, cart, checkout, and purchase options, and remove duplicate tracking installations.

Test the implementation using Google Tag Assistant and GA4 DebugView rather than waiting for standard reports. Perform the test while logged out, after accepting analytics consent, and with browser blockers disabled.

For missing purchase events, confirm that the payment gateway returns the customer to the WooCommerce order-received page. For missing add-to-cart events, test whether custom AJAX buttons, page-builder templates, or JavaScript errors are preventing the integration from detecting the cart action.

Once Tag Assistant shows correctly formatted add_to_cart, begin_checkout, and purchase events being sent to the intended GA4 property, the ecommerce reports should begin populating after Google processes the data.

Leave a Comment