Integration · Subscriptions
RevenueCat
RevenueCat normalises App Store, Play Store, and web subscription receipts into a single event stream. Metapolicy uses RevenueCat webhooks as the canonical reward signal for mobile-first subscription apps where the App Store / Play Store handles the actual billing.
The contract
What flows in
- RC webhooks: INITIAL_PURCHASE, RENEWAL, CANCELLATION, EXPIRATION, BILLING_ISSUE
- App User ID mapping → user_id for cross-surface attribution
- Product identifier → reward_spec key (so we know which paywall variant earned the conversion)
What flows out
- Lift readouts attributed back to the RC user → product → policy_snapshot chain
- Outcome-priced billing computed against RC-confirmed LTV (handles store refunds / chargebacks automatically)
Setup
- 01In RevenueCat Dashboard → Integrations → Webhooks, add the Metapolicy endpoint
- 02Map RC App User ID to your internal user_id (typically already in place via your auth bridge)
- 03Connect product identifiers to Metapolicy experiment + variant naming
- 04Replay 30 days of historical RC events to seed the lift readout baseline
- 05Outcome-priced billing flips on once the 90-day replay matches your reported MRR within ±2%
Why RC over direct App Store / Play Store
RevenueCat handles the cross-store normalisation, refund propagation, and grace-period semantics that App Store Server Notifications and Play Real-time Developer Notifications make painful to handle directly. For a mobile-first subscription app, your reward signal is one webhook away.
The DR + ESS readout treats RC's confirmed LTV as the outcome of record — matching what your finance team reconciles against the App Store reports each month.
Wire RevenueCat in a 30-minute call.
We pair with your engineer, ship the integration live, and run the first decision on your stack.