On April 30, 2026, WooCommerce shipped a Subscriptions Health Check tool that surfaces every active subscription that should be auto-renewing but isn’t. Every one of those silently-manual subscriptions has also been silently missing from your Meta CAPI, Google Ads, GA4, and BigQuery renewal stream — in some affected stores, for as long as 18 months.

The tool fixes the visibility problem. It does not fix the attribution problem, and the attribution problem is what’s been quietly understating your LTV reporting and starving Smart Bidding of signal.

What the Health Check Tool Actually Surfaces#

The Health Check tool lives under WooCommerce > Status > Subscriptions. It runs two checks against your live database.

The first one — Supports auto-renewal — lists every active subscription where five conditions are simultaneously true: status is active, on-hold, or pending-cancel; the _requires_manual_renewal flag is set; a payment method is on file; the gateway supports automatic recurring payments; and the customer has a saved payment token on that gateway. When all five line up, the subscription has every architectural reason to auto-renew — and isn’t.

The second check — Missing renewals — surfaces active subscriptions with missing next-payment dates, or past-due next-payment dates that have no matching renewal order. Either way, the renewal cycle has quietly broken.

WooCommerce shipped this tool because four bugs in WC Subscriptions could silently flip a subscription to manual renewal at checkout, with the concentrated exposure window running from October 2023 through May 2024 in HPOS-enabled stores. High Performance Order Storage became the default in WooCommerce 8.2 on October 10, 2023, and the relevant patches landed in WCS 6.3.0 in May 2024. A fourth, related issue — payment method changes silently flipping manual subs back to automatic, overriding subscriber intent — was patched on April 23, 2026 in WCS 8.6.1.

The Health Check tool deliberately doesn’t pre-filter legitimate manual-renewal subscriptions, and it deliberately doesn’t auto-fix anything. WooCommerce’s reasoning is sound: the merchant has too much store-specific context to be guessed at. The tool surfaces and tags. You decide.

Why the Subscriber Never Complained#

Here’s the part that explains why this went undetected for so long. The Customer Renewal Invoice email is enabled by default on roughly 91.8% of stores, based on WooCommerce’s opt-in tracking data.

That means a silently-manual subscriber kept getting a polite “pay this invoice” email every billing cycle. Most paid it. Some assumed that was just how the subscription worked. The merchant, meanwhile, saw the order land in the admin as a paid renewal — same revenue, same customer record — and never had a reason to look closer.

Translation: the customer-facing experience looked fine, the revenue looked fine, and the admin looked fine. What didn’t look fine was the renewal event stream feeding your ad platforms — because there was no renewal event firing.

You may be interested in: The One WooCommerce Fix That Tells You What to Stock Next

The LTV and Smart Bidding Gap Nobody Is Talking About#

Health Check is an admin-visibility surface. It is not an attribution surface.

Every silently-manual subscription it now lists has been missing from the renewal-event stream that flows into GA4, Meta CAPI, Google Ads Enhanced Conversions, and BigQuery for as long as 18 months. The downstream cost compounds in three specific places.

Customer LTV reporting is understated. Affected subscribers look like one-time buyers in your platform analytics, not recurring revenue. Cohort retention curves drop further than they should. Lifetime value averages skew low.

Smart Bidding has been trained on incomplete signal. Google Ads and Meta’s value-based bidding algorithms learn from the conversion events you send them. Missing 18 months of renewal events from a subset of high-value subscribers tells the bidder those customer profiles are worth less than they actually are. The model adjusts targeting accordingly.

Lookalike and Customer Match audiences are missing the highest-LTV signal. The customers who would have anchored your retention-based lookalikes are the ones whose recurring value never reached the platform.

Fixing the subscription in the Health Check tool corrects the admin status going forward. It does not retroactively fire the renewal events that never happened.

The Architectural Fix the Tool Stops Short Of#

Two things need to happen, and neither one is a job for an admin tool.

First: prospective capture. Every subscription state transition needs to be observed at the WooCommerce action hook layer — woocommerce_subscription_renewal_payment_complete, woocommerce_subscription_status_updated, payment failures, switches, cancellations. Capture each one as it fires, enrich it with customer LTV context, and route it to GA4 (Measurement Protocol), Meta CAPI, Google Ads Enhanced Conversions, and BigQuery in the same call. A subscription that gets silently flipped to manual still fires a status transition the hook can see, even if the renewal never happens.

Second: retrospective backfill. Once Health Check surfaces the affected population, the renewal orders that did happen — the ones where the customer paid the manual invoice — are sitting in your WooCommerce orders table with full dates, amounts, and customer IDs. They can be replayed to ad platforms via the Measurement Protocol and Conversions API as offline conversions, with timestamps preserved. Backfilling 18 months of high-LTV renewal events recalibrates Smart Bidding far faster than waiting for the next 18 months of organic signal.

You may be interested in: WordPress to BigQuery Without a Developer

How Seresa Does This#

Transmute Engine™ is a first-party Node.js server that runs on your subdomain (e.g., data.yourstore.com). The inPIPE WordPress plugin listens to WooCommerce action hooks — including the full subscription state-transition surface — and batches events via authenticated API to your Transmute Engine server, which formats and routes them simultaneously to GA4, Meta CAPI, Google Ads, BigQuery, and Klaviyo. Because BigQuery is one of the destinations, the same pipeline supports replaying historical renewal orders for backfill once Health Check surfaces the affected subscriptions.

Key Takeaways#

• Run the Health Check tool today. WooCommerce > Status > Subscriptions. It’s free, it’s instant, and it’s the only reliable way to know whether your store was affected.
• HPOS stores between October 2023 and May 2024 are the exposure window. Bug impact at scale is contested — don’t catastrophize — but don’t skip the check either.
• Health Check surfaces. It does not auto-fix and it does not backfill ad-platform events. Both are merchant responsibilities.
• The real cost is downstream: understated LTV, miscalibrated Smart Bidding, and weakened lookalike audiences across as many as 18 months.
• Server-side hook capture is the architectural fix — both prospectively (every renewal as it fires) and retrospectively (backfill from historical orders into Meta CAPI, Google Ads, GA4, and BigQuery).

FAQ#

Run the Health Check tool. Then come to seresa.io to close the renewal-event gap it leaves behind.