Skip to main content

Sudden Drop in Subscriber Count

If your paying subscriber count falls sharply, Benecaster emails you about it rather than letting it pass as ordinary churn. That email is the whole of the feature — it is a heads-up, not a protection. Nothing is paused, nothing is flagged in your dashboard, and nothing about your plan or your billing changes because of it.

Do not treat the alert as a hold on your account. If the drop is real and your count stays low, your plan follows the same rules it always does — the alert neither delays nor triggers a change. It exists so that a bridge that has quietly stopped working reaches you within a day instead of at your next invoice.

When it sends. Your paying subscriber count has to fall below either 20% of its highest recorded value or 5, and that high-water mark has to have been above 10 at some point — both rules carry that precondition. A brand-new account with a handful of subscribers will not trigger it, deliberately: at those numbers real churn and a broken integration look identical.

It sends once. Detection resets the high-water mark to the current count, so a genuinely collapsed count will not email you again tomorrow. The practical consequence is that an alert you ignore does not come back — if you are not sure yet whether the drop was real, work through this page rather than waiting for a reminder.

Staging sites are excluded from both the alert and the high-water mark, so a staging copy reporting near-zero subscribers will not set your figures off.

This doc helps you find out why the count dropped.


Check Your Subscriber List First

Go to Benecaster → Subscribers and look at the subscriber list. Sort by status or last-active date to see if a group of subscribers changed to inactive or were removed around the same time. The timestamp tells you when the change happened, which narrows down the cause.


Common Causes

Your subscription plugin had a billing or status event

If you use an external membership plugin (Restrict Content Pro, Paid Memberships Pro, MemberPress, WooCommerce Subscriptions), a mass status change in that plugin is the most common cause of a sudden drop. Payment gateway outages, plugin updates, or a misconfigured expiry rule can cancel or expire memberships in bulk. Check your membership plugin’s member list for recent status changes and compare the timing to the drop.

Your bridge connection stopped working

If Benecaster loses its connection to your subscription plugin, it can no longer read membership status — which may cause subscribers to appear inactive. Go to Benecaster → Settings → Subscription and verify that your bridge is active and the tier mapping looks correct. If the bridge shows a connection error, see Membership Plugin Not Connecting.

You (or a plugin update) reset or cleared subscriber data

Check whether a plugin update ran around the same time as the drop. Also check whether any tools — database cleanup plugins, migration scripts, or staging site sync operations — may have touched Benecaster’s subscriber or token data. A staging-to-production database push is a common culprit: it overwrites your production subscriber data with staging data.

Your Stripe account had a payment failure event

If you’re using the built-in Stripe integration, a problem with your Stripe account — expired card on file, rate limit, or account flagged — can trigger mass payment failures and subscription cancellations. Log in to your Stripe dashboard and check the Events log for recent failures around the time of the drop.

You have a staging site connected to the same show

Staging sites are excluded from subscriber counts, but if a staging site was recently connected, disconnected, or had its own subscriber data cleared, it can create confusing changes in what you see. If you run a staging environment, check that it’s configured as a staging connection in Benecaster → Settings → Account, not a production connection.

Subscribers were manually removed

If you or someone with admin access manually revoked subscriber tokens or deleted subscriber records, that shows as a sudden drop. Check your WordPress admin user activity log if you have one installed, or check with anyone else who has access to the site.

A MemberPress or WooCommerce Subscriptions membership had already lapsed before your bridge started reporting expirations

If you connect through MemberPress or WooCommerce Subscriptions, Benecaster runs a one-time background check the first time it starts reporting expirations for that bridge. It revokes access for members whose membership had already run out before that point — their feed had already stopped serving paid episodes, so nothing changes for them, but your Subscribers list and paying count drop as the check works through your subscriber tokens, which can take anywhere from a few minutes to a few hours on a large list. No subscription-ended email goes out for these; the membership already ended, so a batch of after-the-fact notices would only confuse people. If someone in this group resubscribes, they get the same feed URL back. This does not touch Restrict Content Pro, Paid Memberships Pro, built-in membership, followers, or comped access, and it skips any show whose membership plugin is deactivated while the check runs.


If Your Subscriber Count Recovers

Nothing has to be cleared or reset — there is no flag holding anything open. Once the underlying cause is fixed and your subscribers report normally again, your count is simply your count, and your plan is evaluated on it as usual.

You will not get an all-clear email. The alert is one-directional. The way to confirm recovery is Benecaster → Subscribers, not your inbox.


If You Can’t Find the Cause

If none of the above applies and you can’t identify what changed, contact support with your site URL and the approximate date and time you noticed the drop. Include a screenshot of your subscriber list if possible. The support team can review the event log and help trace what happened.


What Happens Next If the Count Stays Low

Nothing happens because of the alert — it does not start a clock or feed into any plan decision. A lower count is treated as a lower count.

What that means for your plan is the ordinary rule, and it is worth knowing it works in your favour here: moving down a plan is something you do, not something done to you. Eligibility to downgrade is decided by a 30-day window on your benecaster.com account, so a count that drops today does not move you anywhere today. See Licensing and plans for how plan changes are decided, and License status for what your current state is.

See Also

Need this built rather than just documented? See our services →