WooCommerce Block Checkout Broke Your Tracking — And You Probably Don’t Know It

Does WooCommerce block checkout break conversion tracking plugins?

Yes — most tracking plugins hook into the classic shortcode checkout’s woocommerce_thankyou action, which doesn’t fire on block checkout pages. WooCommerce block Cart and Checkout became the default for new stores from version 8.3 in November 2023 (WordPress.org / WooCommerce), and two years later the majority of tracking plugins still haven’t adapted.

The checkout still works for the customer. Products get added, payments process, orders confirm. But the JavaScript event that tells GA4 “a purchase happened” never fires. The conversion is real. The revenue arrives. Your analytics never see it.

This isn’t a bug in GA4 or a misconfiguration in your tracking plugin. It’s an architectural mismatch: block checkout uses a React-based rendering pipeline that doesn’t trigger the PHP action hooks that classic checkout plugins depend on. The plugin was built for one system. The checkout moved to another. Nobody told the plugin.

WooCommerce block Cart and Checkout became the default for new stores from version 8.3 in November 2023 — most tracking plugins still hook into the classic shortcode checkout that no longer fires their events (WordPress.org / WooCommerce).

Which WooCommerce tracking plugins support block checkout in 2026?

Very few tracking plugins have been updated to support WooCommerce block checkout as of 2026. The vast majority still rely on classic shortcode hooks, including several of the most-installed GA4 and conversion tracking plugins in the WordPress.org repository. 70% of e-commerce stores already have broken or incomplete tracking configurations (Conversios, 2025) — and block checkout incompatibility is adding a new failure mode on top of existing gaps.

The plugin ecosystem’s slow response isn’t laziness. Block checkout is a fundamentally different architecture. Supporting it means rewriting the event-firing mechanism from PHP action hooks to JavaScript-based Store API integration or block-level event listeners. That’s a significant engineering investment, and most free tracking plugins don’t have the development bandwidth.

Server-side tracking solutions bypass the block vs. classic distinction entirely. Because they capture events at the server — after the payment gateway confirms the transaction — they don’t depend on front-end JavaScript hooks to fire. The checkout page type becomes irrelevant.

Related: 52% of Consumers Now Block Ads — And GA4 Is One of the Scripts They Block

How do I tell if my store uses block checkout or classic shortcode checkout?

Open your checkout page in the WordPress block editor — if you see a visual block layout with individual block components, you’re on block checkout, and if you see [woocommerce_checkout] as a shortcode in a classic block, you’re on the classic version. You can also check WooCommerce → Status → System Status for the checkout page type.

The distinction matters more than most store owners realise. A store that migrated to block checkout — or one that was created after November 2023 on WooCommerce 8.3+ — may have tracking that worked perfectly on classic and now silently drops every purchase event. The checkout looks and functions identically to the customer. The difference is entirely under the hood, in how the page renders and which hooks fire.

If you’re unsure, here’s a quick test: place a test order, then check your GA4 Realtime report for a purchase event within 30 seconds. If it doesn’t appear — and you’re running a client-side tracking plugin — block checkout compatibility is the most likely culprit.

What purchase events get lost when a tracking plugin doesn’t support blocks?

The purchase/conversion event — the single most valuable event in e-commerce tracking — is what goes missing. Without it, GA4 shows the session but no transaction, Google Ads can’t attribute the conversion to the click, and Meta CAPI never receives the purchase signal. Standard plugin-based GA4 tracking routinely misses 15–40% of WooCommerce transactions even before block checkout incompatibility enters the picture (mdniamul.com, 2026).

But it’s not just the purchase event. Depending on the plugin’s implementation, add_to_cart, begin_checkout, and add_payment_info events can also fail. These mid-funnel events are what GA4 uses to build your funnel visualisation and what ad platforms use for micro-conversion bidding. Lose them, and your entire conversion funnel looks broken — not because customers aren’t converting, but because the tracking never saw them start.

The downstream effect is silent and compounding. Google Ads and Meta optimise toward the conversions they can see. When 15–40% of conversions are invisible, the algorithms systematically underbid and underallocate budget to the audiences that are actually buying.

Standard plugin-based GA4 tracking routinely misses 15–40% of WooCommerce transactions — and block checkout incompatibility adds a second layer of invisible data loss on top of ad blockers and consent rejection (mdniamul.com, 2026).

Why doesn’t GA4 show an error when block checkout breaks tracking?

GA4 only reports events it receives — when a tracking plugin fails to fire a purchase event because it can’t hook into block checkout, GA4 simply never sees it. There’s no error, no warning, no gap indicator in the dashboard. The platform reports fewer conversions, and most store owners assume business dropped rather than realising their tracking broke.

This is what makes the block checkout tracking failure uniquely dangerous. A broken checkout page generates support tickets. A broken tracking integration generates… silence. Revenue keeps arriving. Orders keep processing. The only symptom is a slow divergence between your actual bank deposits and your GA4 revenue reports — and most people blame seasonality or market conditions before they suspect their measurement stack.

The absence of an error is the error. GA4 was designed to report what it’s told. Nobody told it.

Does the PayPal Payments plugin work with WooCommerce block checkout?

PayPal Payments has confirmed compatibility issues with block checkout, documented in a May 2026 GitHub issue (WooCommerce PayPal Payments GitHub, 2026). The plugin can break the checkout flow entirely or prevent tracking events from firing, depending on the combination of gateway version and block checkout version in use.

PayPal is one of the most-used payment gateways in WooCommerce. When it conflicts with block checkout, the impact ripples through every downstream system: the payment may still process (through fallback rendering), but the tracking hooks that fire on successful payment may not execute. A store owner sees the order in WooCommerce admin and the money in PayPal — but GA4, Google Ads, and Meta never learn the conversion happened.

Three or more plugins commonly compete to hook into the same WooCommerce checkout action in a typical store (Wbcom Designs, 2026). Add PayPal’s block checkout issues to the mix, and you have a stack where payment, analytics, and checkout rendering are all competing for the same execution space — and the tracking plugin usually loses.

Related: Your WordPress Site Loads 12 Tracking Scripts — Here’s the Real Cost

How many WooCommerce plugins conflict with each other on the checkout page?

Three or more plugins commonly compete to hook into the same WooCommerce checkout action in a typical store (Wbcom Designs, 2026). Each adds its own JavaScript listeners, PHP hooks, and sometimes inline scripts that fire on the same page events. When multiple plugins target the same action, they can overwrite each other’s event listeners or prevent events from firing at all.

The checkout page is the most contested real estate in a WooCommerce store. Payment gateways, analytics plugins, marketing pixels, upsell tools, and checkout customisers all need to execute code at the same moment — when the customer clicks “Place Order.” On classic checkout, this congestion caused intermittent failures. On block checkout, where the rendering pipeline is different and the hook system is newer, the conflict surface is larger and less predictable.

The practical result: a plugin that works perfectly in isolation breaks when installed alongside two others. The store owner tests checkout with a single order, sees it work, and assumes everything is fine. The intermittent failures — the 15–40% of transactions where timing or load order causes a hook to not fire — only show up in aggregate, weeks later, when someone notices GA4 and the bank account don’t agree.

What percentage of WooCommerce transactions does plugin-based tracking miss?

Standard plugin-based GA4 tracking routinely misses 15–40% of WooCommerce transactions (mdniamul.com, 2026). The losses compound from three sources: ad blockers blocking the tracking script before it loads, consent rejection preventing it from executing, and checkout hook failures where the purchase event never fires — a problem significantly amplified by block checkout incompatibility.

For a store processing 1,000 orders a month, that’s 150 to 400 invisible conversions. At an average order value of $75, the invisible revenue is $11,250 to $30,000 monthly — real money from real customers that your analytics, your ad platforms, and every AI-driven optimisation tool built on top of them will never account for.

The question isn’t whether you’re losing data. It’s how much. And with WooCommerce moving steadily toward block checkout as the only supported path, the stores that haven’t updated their tracking architecture aren’t facing a future problem — they’re accumulating invisible losses today.

Is WooCommerce deprecating the classic shortcode checkout?

WooCommerce has been moving toward full block checkout as the standard since version 8.3 in November 2023, and the classic shortcode checkout now receives fewer updates and improvements. The autumn WooCommerce 9.4 release is expected to push more stores toward migration, making block checkout compatibility a requirement rather than an option for every plugin in the stack.

The deprecation isn’t a single switch-off date. It’s a slow squeeze: new features land in blocks first, bug fixes for classic get lower priority, and eventually the shortcode path becomes unsupported. Stores that haven’t migrated yet are running on borrowed time — and every month they wait, their tracking gap grows as more of the WooCommerce ecosystem assumes blocks.

For store owners planning a migration, the tracking layer should be the first thing tested. A checkout that processes orders correctly but drops every conversion event is worse than a broken checkout — because a broken checkout gets fixed immediately, while silent tracking loss accumulates for months before anyone notices.

How does server-side tracking avoid the block checkout compatibility problem?

Server-side tracking captures events at the server when the transaction is processed — after the payment gateway confirms the purchase but before the browser renders the thank-you page. This means it doesn’t depend on JavaScript hooks, checkout page type, or front-end plugin compatibility. The event fires regardless of whether the store uses block or classic checkout.

The architectural difference is fundamental. Client-side tracking asks the browser to report what happened. Server-side tracking asks the server to report what happened. The browser can be blocked, the JavaScript can fail to load, the checkout hook can not fire. The server always knows when a payment processed, because the server is the one that processed it.

This is why the block checkout migration is accelerating the shift toward server-side tracking. It’s not just about recovering the 15–40% lost to ad blockers and consent — it’s about building a measurement foundation that doesn’t break every time WooCommerce updates its front-end architecture.

Key Takeaways

• Block checkout became WooCommerce’s default in November 2023: Most tracking plugins still hook into the classic shortcode checkout that no longer fires their events.
• 70% of stores already have broken tracking: Block checkout incompatibility adds a second layer of invisible data loss on top of existing gaps.
• GA4 shows no error when tracking breaks: The platform reports fewer conversions silently — most store owners blame the market, not the measurement.
• 15–40% of transactions go missing with plugin-based tracking: Ad blockers, consent rejection, and checkout hook failures compound into a significant blind spot.
• PayPal Payments has confirmed block checkout issues: One of WooCommerce’s most-used gateways can prevent tracking events from firing (May 2026 GitHub issue).
• Server-side tracking bypasses the problem entirely: Events captured at the server don’t depend on checkout page type, JavaScript hooks, or front-end plugin compatibility.

References

1. WordPress.org / WooCommerce (2023). WooCommerce 8.3 Block Checkout Default. Source
2. Conversios (2025). E-commerce Tracking Configuration Study. Source
3. mdniamul.com (2026). GA4 WooCommerce Tracking: Fix Missing Purchases. Source
4. WooCommerce PayPal Payments GitHub (2026). Block Checkout Compatibility Issue. Source
5. Wbcom Designs (2026). WooCommerce Plugin Bloat 2026. Source
6. Harbor Checkout Fields for WooCommerce (2026). WordPress.org Plugin. Source
7. CashFlowCanary (2026). Broken Checkout Guide. Source