Sudden Drop in Subscriber Count
If your subscriber count drops sharply and unexpectedly, Benecaster flags it as a suspicious drop rather than treating it as normal churn. While the flag is active, all automatic tier change logic is paused — you won’t be downgraded during this window. You’ll receive an email alert and an admin notice in your WordPress dashboard.
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 Subscription 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 the benecaster_subscribers or benecaster_tokens tables. 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.
If Your Subscriber Count Recovers
If the count returns to normal within one billing period, the suspicious drop flag clears automatically. Benecaster sends an all-clear notice and resets the downgrade timer. No plan change happens.
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
If the low count persists for one full billing period without recovering, Benecaster resumes normal downgrade evaluation — starting the standard two-period warning sequence. You’ll receive advance notice before any plan change occurs. See My subscriber count dropped suddenly — will I be auto-downgraded? for the full downgrade flow.