Automated Pushwoosh Stale Subscriber Alerts
Every Monday, WebRun opens Pushwoosh, checks the subscriber base for devices that have gone inactive or stopped receiving pushes over the past 60 days, posts a Slack alert with the inactive count and share of the base, and escalates to Telegram if the inactive share has grown large enough to affect delivery reporting.
How do I track inactive Pushwoosh subscribers before they skew my reporting?
Every Monday, WebRun checks the Pushwoosh subscriber base for devices with no delivered push in the past 60 days, posts a Slack alert with the inactive count and share, and escalates to Telegram if that share has grown noticeably from the prior week. A quietly growing stale subscriber base gets caught before it skews delivery reporting.
- Inactive subscriber growth gets caught the week it starts
- Delivery reporting stays meaningful instead of quietly skewed
- A weekly health check runs without anyone remembering to pull it
Built for mobile app growth teams · push notification managers · product marketing · app engagement teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.pushwoosh.comin a real browser with your saved login - no setup, no API keys. -
1
Pushwoosh - check subscriber activity
pushwoosh.com
WebRun opens Pushwoosh to check subscriber activity. - Open Pushwoosh and review the subscriber base
- Find devices with no delivered push in the past 60 days
- Calculate the inactive count and its share of the total base
Done when The inactive subscriber count and share of the base are captured.
-
2
Slack - post the stale subscriber alert
slack.com
WebRun opens Slack to post the stale subscriber alert. - Post a Slack alert with this week's inactive subscriber count and share
- Compare it against last week's figure
- Post it even on a stable week, since this is a routine health check
Done when The team has this week's stale subscriber alert in Slack.
-
3
Telegram - escalate a large inactive share
telegram.org
WebRun opens Telegram to escalate a large inactive share. - Escalate to the growth Telegram channel only if the inactive share has grown noticeably from last week
- Include the new share and how much it has grown
- Skip the escalation on a stable week
Done when Telegram is used only when the inactive share has grown noticeably.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it remove the inactive subscribers?
No. WebRun only measures and reports the inactive share. Removing or re-engaging those subscribers stays a decision for your team.
What counts as inactive?
A device with no delivered push notification in the past 60 days, a window you can adjust to match your own engagement pattern.
Why does this matter for delivery reporting?
A large inactive share can quietly drag down your overall delivery numbers, so catching the trend early keeps reporting meaningful.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.