70.19% of all shopping carts are abandoned globally — the average across 49 studies (Baymard Institute, 2025). If your store’s GA4 funnel shows a different number than your abandoned cart plugin, both numbers could be technically correct. They’re just measuring completely different things. Neither is your actual cart abandonment rate.
This is one of the most common points of confusion in WooCommerce analytics — and the explanation matters before you make a single checkout optimisation decision based on either number.
Two Systems, Two Populations
GA4 and your WooCommerce abandoned cart plugin are not looking at the same set of visitors. They never were. That’s why they’ll never agree.
What GA4 sees: GA4 builds its funnel from events — specifically add_to_cart events followed or not followed by a purchase event. Both events require JavaScript to execute in the visitor’s browser. No JavaScript, no event. No event, no visibility into that session.
What your plugin sees: WooCommerce stores cart data in its own database the moment a product is added to the cart — server-side, no browser dependency. Your abandoned cart plugin reads those database records directly. Every session is logged: ad-blocker users, consent-declining users, anonymous users who never reach the email-capture step, visitors on slow connections who never finish loading your tracking scripts.
The GA4 number is always a subset of the plugin number. Sometimes a large subset, sometimes a small one — depending on your audience’s ad blocker usage, your consent banner acceptance rate, and how many visitors abandon before reaching the checkout email field.
You may be interested in: WooCommerce Shows 50 Orders, GA4 Shows 12: The Attribution Gap Nobody Explains
The Three Categories GA4 Cannot Count
Understanding exactly who goes missing from GA4’s abandonment calculation explains why the gap can be so large.
Anonymous early-stage abandoners. A visitor adds a product to the cart, skips past checkout login, and leaves before entering an email address. GA4 recorded the add_to_cart event. But the session has no user ID, no email, no persistent identifier. If that visitor returns later on a different device or browser, GA4 has no way to connect the sessions. Your plugin counted an abandoned cart. GA4 counted an add_to_cart that eventually had no matching purchase — but may also attribute a later purchase to a completely separate session.
Ad-blocked sessions. 30-40% of WooCommerce purchase events are already missing from GA4 due to ad blockers, consent rejection, and payment gateway redirects (Seresa, 2025). Cart events suffer the same suppression. A visitor running uBlock Origin adds products to their cart and abandons. Your WooCommerce database has a full record. GA4 has nothing — because the add_to_cart script never executed.
Consent-rejecting users. Depending on your consent banner configuration, visitors who decline non-essential cookies may receive no GA4 tracking at all. Their cart session exists in your WooCommerce database. GA4 never sees them.
The realistic consequence: if your plugin dashboard shows 500 abandoned carts this month and GA4 shows 120 funnel drop-offs, both numbers are accurate within their own measurement system. Your actual abandonment universe is the plugin number. GA4 is a browser-visible slice of it.
The Recovered-Cart Blind Spot
There’s a second problem that sits on top of the measurement gap — and this one affects stores that have invested in recovery email sequences.
When a visitor receives an abandoned cart recovery email, clicks through, and completes their purchase — that transaction appears in GA4 as a standard purchase event. There is no purchase_recovered event type in GA4. There’s no native way to distinguish a recovered-cart conversion from any other conversion.
Cart recovery emails achieve a 50.5% open rate and 3.33% conversion rate on average (Klaviyo / WooCommerce, 2025). More than 300,000 WooCommerce stores actively use cart abandonment recovery plugins (WordPress.org, 2025). These are significant commercial programs generating real revenue — and their ROI is effectively invisible inside GA4 unless you’ve built custom event tracking around them.
The practical consequence: your recovery email program is producing conversions that GA4 attributes to whatever channel last touched the recovered customer — often direct or email traffic. The causal relationship between the recovery email and the purchase is in your plugin dashboard. It’s nowhere in GA4.
You may be interested in: Your WooCommerce GA4 Shows 50% Direct Traffic
What a Correct Measurement Looks Like
The right measurement system for cart abandonment doesn’t choose between GA4 and your plugin — it bridges them.
WooCommerce has a native hook, woocommerce_cart_updated, that fires server-side whenever a cart is modified. A separate process can monitor session records and detect when a cart session expires without a corresponding order — the server-side definition of abandonment. At that point, a cart_abandoned event can be pushed directly to GA4 via Measurement Protocol, along with the cart value, product list, and session context.
The result: GA4 receives an abandonment event generated from the same population your plugin tracks — every session, not just the JavaScript-executing subset. Your GA4 funnel numbers and your plugin numbers start to converge.
For recovered carts, a custom parameter on the purchase event — recovery_source: email — allows GA4 to distinguish recovered purchases from standard ones, making your recovery program’s contribution visible inside the same platform where you’re measuring ROAS and channel performance.
Transmute Engine™ is a first-party Node.js server running on your own subdomain (e.g., data.yourstore.com). The inPIPE WordPress plugin monitors WooCommerce session state server-side and routes cart_abandoned events to GA4 Measurement Protocol when a session expires without an order — giving your GA4 funnel visibility into the real abandonment population, not just the browser-visible fraction.
Key Takeaways
- GA4 and your WooCommerce plugin will never agree — they’re measuring different populations. GA4 sees browser-executing sessions. Your plugin sees all WooCommerce database sessions.
- The three invisible abandoner groups are anonymous early-stage leavers, ad-blocker users, and consent-declining visitors — all logged by your plugin, none visible to GA4.
- Recovered-cart purchases have no special event type in GA4 — they appear as standard purchases, making recovery email ROI invisible without custom event parameters.
- The global abandonment rate is 70.19% (Baymard Institute, 2025) — your store’s real rate is closer to your plugin’s number than GA4’s.
- Server-side cart abandonment events via Measurement Protocol close the gap — pushing abandonment signals to GA4 from WooCommerce session data rather than browser JavaScript.
Your abandoned cart plugin reads WooCommerce database sessions directly — logging every cart regardless of browser state or JavaScript execution. GA4 only records abandonment from sessions where its tracking script fired successfully. Users with ad blockers, users who decline consent, and anonymous users who leave before entering an email address are counted by your plugin but completely absent from GA4’s funnel. The plugin number is closer to reality.
Use your WooCommerce plugin number as your actual abandonment rate — it measures the complete population of sessions with an unpurchased cart. GA4’s number is useful for funnel analysis within the browser-tracked population, but it systematically undercounts abandonment by excluding users whose sessions were never visible to browser-side scripts. The gap between the two numbers is itself useful data: it tells you the size of the audience your GA4 funnel cannot see.
GA4 has no native recovered-cart purchase event. When a visitor completes a purchase via a recovery email link, GA4 records a standard purchase event — indistinguishable from any other conversion. To track recovery ROI in GA4, you need a custom parameter added to the purchase event (e.g., recovery_source: email) when the purchase session originated from a recovery link. This requires server-side event enrichment or a custom dataLayer push tied to your recovery link UTM parameters.
The global average is 70.19% across 49 studies (Baymard Institute, 2025). WooCommerce-specific rates typically fall in the 65-80% range depending on product type, checkout flow complexity, and required account creation. Stores measuring their abandonment rate only in GA4 will see a lower number — not because their rate is better, but because GA4 is missing a portion of the abandoning audience entirely.
Your plugin knows how many carts were abandoned. GA4 knows what happened in the browser. Seresa connects the two — pushing server-side abandonment events to GA4 so your funnel reflects what actually happened in your store, not just what JavaScript could see.