On April 30, 2026, the WooCommerce engineering team shipped the Subscriptions Health Check tool — a free diagnostic that surfaces, for the first time, exactly how many subscriptions on your store are silently failing to renew. The tool is genuinely useful. It is also, by accident, the cleanest measurement of a problem nobody at Woo was trying to solve: every row in the “Missing renewals” view is also a row that Meta CAPI, GA4 and Google Ads have never seen.

What the Health Check Actually Shows

The tool lives at WooCommerce → Status → Subscriptions and surfaces two distinct diagnostic views. According to the official Woo Developer Blog post by Darren Ethier, Director of Engineering at Automattic:

“While we already had this tool on our roadmap, we accelerated work on it after a public report of four bugs that could have put subscriptions into an unexpected non-renewal state.”

The first view, “Supports auto-renewal,” lists subscriptions currently flagged for manual renewal where the customer has a saved payment token on a gateway capable of automatic billing. The infrastructure for auto-renewal exists; the subscription just is not using it. These are candidates for conversion to auto-renewing.

The second view, “Missing renewals,” is the one that quantifies the measurement gap. It lists active or on-hold subscriptions that are not set to expire after the current cycle and have either an empty next-payment date, or a next-payment date in the past with no matching renewal order in the ±24-hour window.

In plain terms: subscriptions that should have renewed by now and did not.

The Four-Bug Backstory

The accelerated release was triggered by the public disclosure of four bugs that could put subscriptions into an unexpected non-renewal state. Three were fixed in earlier releases — one in March 2024, two in late 2023. The fourth, a same-gateway switch recovery gap, shipped in Subscriptions 8.6.1 on April 23, 2026.

Bug 2, narrowest in scope but instructive, corrupted renewal timing for subscriptions migrated during an August–December 2023 window. Stores affected may never have noticed — the subscription appeared healthy in the admin, while the WP-Cron renewal job quietly went sideways.

Ethier’s framing is the operator-respectful one:

“But while we were scoping the detection work, we realized that a subscription stuck in this state is a problem regardless of what caused it.”

That is the right call. The diagnostic doesn’t care which bug, which release, or which migration caused a given missing renewal. It surfaces the symptom, end of story.

For broader context on why subscription revenue routinely fails to reconcile across measurement layers, our companion piece on why Smart Bidding can’t see your subscription renewals walks through the upstream algorithmic argument — Google’s algorithm is optimizing against a renewal signal it has never had access to.

Why Renewals Don’t Fire Ad Pixels — Even When They Work

To understand why the health check inadvertently quantifies an ad-platform measurement gap, you have to understand how renewals actually fire on a WooCommerce store. It is not how the merchant intuitively pictures it.

A first purchase looks like this:

1. Customer clicks an ad, lands on the product page.
2. Browser session is active. Meta Pixel, GA4, Google Ads tags are loaded.
3. Customer completes checkout. Thank-you page loads.
4. Pixel fires the Purchase event. CAPI fires server-side. GA4 records the conversion. Google Ads sees the click-to-purchase chain.

A renewal looks like this:

1. WP-Cron fires the woocommerce_subscription_renewal_payment_complete hook on the server, at the scheduled renewal time.
2. The payment gateway charges the saved card or token.
3. The order is created. Revenue lands in WooCommerce.
4. No browser session exists. No thank-you page loads. The Meta Pixel, GA4, and Google Ads tags are all browser-side libraries — they cannot fire if no browser is open.

The pixel layer was never going to capture renewals. This is not a bug, a misconfiguration, or a plugin oversight. It is structural. Browser tracking can only see events that happen in a browser. WP-Cron renewals do not happen in a browser.

Connect the Dots: Every Row Is Also Missing From Your Ad Platforms

The merchant who opens the health check tool and sees 87 entries in “Missing renewals” reads it as a renewal-health problem. It is also, in exactly the same row count, a conversion-signal problem.

Three categories of rows the health check surfaces, all invisible to ad platforms:

• Renewals that failed silently due to one of the four bugs. Revenue lost. Also: zero events to Meta CAPI, GA4, Google Ads.
• Renewals that retried and eventually succeeded. WooCommerce Subscriptions retries failed payments up to 5 times. The successful retry creates a real order. Revenue captured. Also: zero events fired to any ad platform, because every retry runs through WP-Cron without a browser session.
• Renewals that fire successfully on the first attempt. Not in the health check view — the system thinks everything is fine. Also: still zero events to any ad platform, for the same WP-Cron reason. The health check makes the visible problem visible; the invisible problem stays invisible.

Smart Bidding is the downstream casualty. Google Ads needs up to 50 conversion events or 3 full conversion cycles to calibrate a campaign properly. Every silently failed renewal — and every silently succeeded one — is a missing training signal the algorithm has been optimizing around for months. The CPA you are paying is calibrated on incomplete data the algorithm is unaware is incomplete.

73% of GA4 implementations have silent misconfigurations causing 30-40% data loss (SR Analytics, 2025). On a subscription store, that gap is concentrated almost entirely in renewals. The health check turns a previously theoretical signal-quality gap into an auditable one. Open the tool. Count the rows. That is your gap.

The same architectural failure mode shows up on other WooCommerce surfaces too — our analysis of order bumps that are accepted but never reach GA4 documents the parallel pattern: events that exist in WooCommerce but never make it to the measurement layer, for structural reasons no plugin can fix.

What to Actually Do — Server-Side Renewal Event Capture

The fix is not a plugin update. The structural mismatch — WP-Cron events fired without a browser, browser-side pixels that can only fire in a browser — does not get resolved by another browser-side tag. It gets resolved by capturing the renewal event on the server, where it actually happens, and routing it to the ad platforms through APIs they have always supported but most WordPress sites have never wired up.

The architectural pattern looks like this:

1. Hook into the server-side renewal event. The woocommerce_subscription_renewal_payment_complete action fires reliably whether a browser is open or not.
2. Capture the conversion data at the server. Order ID, value, currency, customer email and phone, gateway, renewal number, original click identifiers (fbc/fbp for Meta, gclid for Google) that were stamped at the original purchase.
3. Hash PII to platform specifications and send via Conversions API. Meta CAPI, Google Ads Enhanced Conversions, GA4 Measurement Protocol — all accept server-side events. None of them require a browser session.
4. Deduplicate where the platform expects it. Renewals are unlikely to also fire from a browser, so deduplication is rarely the issue here — the issue is making the event happen at all.

Here’s How You Actually Do This on WordPress

Transmute Engine™ is Seresa’s dedicated Node.js server that runs first-party on your subdomain (for example, data.yourstore.com). The inPIPE WordPress plugin listens for the woocommerce_subscription_renewal_payment_complete hook and batches renewal events via API to your Transmute Engine server, which formats, enhances, and routes them to Meta CAPI, GA4, Google Ads, and BigQuery simultaneously — from your own domain, with no browser session required. The same pipe that handles initial Purchase events also handles renewals. They land in the same conversion ledger across every platform.

Key Takeaways

• The Subscriptions Health Check shipped April 30, 2026. Run it today: WooCommerce → Status → Subscriptions.
• Every row in “Missing renewals” is a row Meta CAPI, GA4 and Google Ads never saw. The tool quantifies the gap.
• WP-Cron renewals cannot fire browser-side pixels. Not a bug — structural. No browser session, no pixel.
• Even successful renewals are invisible to ad platforms by default. The health check shows the visible failures; the invisible successes still need server-side capture.
• Smart Bidding optimization is calibrated on incomplete data. CPAs are computed against a conversion volume that excludes renewals — the algorithm has no idea.
• The fix lives on the server, not in the browser. Capture the WP-Cron event, hash PII, send via Conversions APIs.

Frequently Asked Questions

Run the health check today. Count the rows. Then capture the renewal event where it actually happens — on your server. Start at seresa.io.