PingBell
payments
Direct webhook

RevenueCat × PingBell

Every in-app purchase and subscription renewal from your iOS or Android app, broadcast to every screen. Connects via RevenueCat webhooks — no code required.

Common use cases

  • Live IAP counter on your monitor while you ship
  • New subscriber bell for your mobile app
  • Renewal and churn tracking for subscription apps
  • Cross-platform iOS + Android revenue in one counter

What RevenueCat + PingBell does together

RevenueCat sits between your app and the App Store / Google Play, normalising every purchase event into a consistent webhook. Point one of those webhooks at PingBell and every INITIAL_PURCHASE, RENEWAL, PRODUCT_CHANGE, or CANCELLATION becomes a counter update, a push notification on every team device, and a graph point — without writing a single line of backend code.

Use cases

  • Indie developers who want to hear the bell when someone buys their app — even at 3 am
  • Mobile teams tracking subscription MRR across iOS and Android in one counter
  • Founders and PMs with a live new-subscriber counter on the office TV
  • Growth teams monitoring trial-to-paid conversion in real time

Setup

  1. In PingBell, create a counter and copy its webhook URL.
  2. In RevenueCat: open your project, go to Project Settings → Integrations → Webhooks.
  3. Click Add webhook, paste your PingBell webhook URL, and save.
  4. Choose which events to forward. For a “new revenue” counter, enable at minimum INITIAL_PURCHASE and RENEWAL. Add CANCELLATION if you want a separate churn counter.
  5. Send a test event from RevenueCat to confirm the counter increments.
  6. Install the PingBell TV and mobile apps. Scan the QR on the TV to pair.

Why PingBell for RevenueCat users

RevenueCat already handles the hard parts — receipt validation, cross-platform normalisation, entitlement management. PingBell adds the ambient visibility layer: a live number on the wall, a sound on every team phone, and a push notification the moment someone pays. No server to run, no dashboard to check.

FAQ

Which RevenueCat plan supports webhooks?

Webhooks are available on all RevenueCat plans including the free tier.

Which events should I send to PingBell?

For a “revenue” counter: INITIAL_PURCHASE and RENEWAL. For a “churn” counter: CANCELLATION and EXPIRATION. PRODUCT_CHANGE is useful if you want to track upgrades separately.

Does it work for both iOS (App Store) and Android (Google Play)?

Yes. RevenueCat normalises purchase events across both stores before the webhook fires, so your counter reflects all platforms automatically.

What if I want separate iOS and Android counters?

RevenueCat’s webhook payload includes a store field (APP_STORE or PLAY_STORE). You can route events to separate PingBell webhook URLs using RevenueCat’s webhook filtering, or use a lightweight tool like Make or Zapier to split on store before forwarding.

Can I track trials separately from paid conversions?

Yes. Use INITIAL_PURCHASE with is_trial_conversion: true for paid conversions and a separate TRIAL_STARTED event for the top of the funnel.

Related: SaaS MRR counter solution

Connect RevenueCat in minutes.

Start the trial, connect RevenueCat, and the next event from it will ring a bell.