Why RevenueCat + FeaturePulse
RevenueCat handles subscription management for thousands of iOS apps. It knows exactly what each user pays. FeaturePulse handles feature requests and knows exactly what each user wants. Connecting the two gives you MRR-weighted prioritization — the ability to sort your feature board by revenue impact.
Integration Setup
The integration requires passing two pieces of data to FeaturePulse when identifying a user: their RevenueCat customer ID and their current subscription amount. Check the MRR integration guide for the exact code snippet and API reference.
- Fetch the active subscription amount from RevenueCat's SDK
- Pass the customer ID and amount to FeaturePulse's identify method
- FeaturePulse associates every vote with the user's MRR
- Feature requests display aggregate revenue from all voters
What You See in Your Dashboard
Once connected, each feature request on your board displays three additional data points: total MRR from all voters, average MRR per voter, and a breakdown by subscription tier. This lets you answer questions like "Is this feature requested mostly by Pro or Enterprise users?" — which shapes how you prioritize by revenue.
RevenueCat's customer ID is the simplest way to connect revenue data. If you use a different subscription provider, FeaturePulse's REST API accepts any revenue amount you pass.
Advanced: Segment by Subscription Tier
Beyond aggregate MRR, you can filter your feature board by subscription tier to see what each segment wants. Free users might request basic features, while Pro users want advanced workflows. This is a practical application of user segmentation that becomes effortless when RevenueCat data flows into FeaturePulse automatically.