What Recurly + PingBell does together
Recurly’s webhooks fire on every subscription lifecycle and billing event (new_subscription_notification, updated_subscription_notification, canceled_subscription_notification, successful_payment_notification). PingBell subscribes to the ones that matter for your KPIs and turns each into a counter, a push, and a graph point.
Use cases
- Subscription SaaS on Recurly tracking live MRR
- Digital media and publishing businesses using Recurly for paywall subscriptions
- B2B SaaS on Recurly running multi-plan mix analysis
- Streaming and content subscription businesses
- Churn reduction teams watching cancellations in real time
Setup
- In Recurly, go to Integrations → Webhooks → Add endpoint.
- Paste the PingBell webhook URL.
- Subscribe to subscription notifications (and optionally
updated_subscription_notificationfor mid-term changes). - Save.
- In PingBell, drop a counter block on a board and pick the source — revenue or count, live.
Why PingBell beats the alternatives for Recurly
Recurly’s Analytics module is strong for reporting but doesn’t broadcast to team screens. PingBell adds the real-time visibility layer across Apple TV, Fire TV, team phones, and browser embeds. For publishing and media businesses particularly, a live “paid subscribers today” counter on the newsroom TV is a morale feature.
FAQ
Can I track different subscription events separately?
Yes — create a source per notification type. New subscriptions ring one counter, payments another, cancellations a third if you want to hear churn the moment it happens.
Does it support Recurly’s hosted payment pages?
Yes. HPP checkouts fire the same subscription-notification webhooks.
What about gift subscriptions?
Gift subscriptions fire the same events. You can filter on the gift flag in the payload if you want to exclude them from MRR.
Can I run a live “churn this week” counter?
Yes. Subscribe to canceled_subscription_notification on a separate PingBell counter.