Revenue
Connect RevenueCat
RevenueCat sends new purchase events to a webhook. Your plan must include webhooks.
Set up the webhook
Open Settings → Integrations → RevenueCat
Choose Set up RevenueCat.
Copy the webhook URL and authorization header
The header is shown once. Save it before leaving the page.
Add a webhook in RevenueCat
In your RevenueCat project, open Integrations → Webhooks and add a configuration. Paste both values, including the
Bearerprefix in the authorization header.Choose events and apps
Select production purchases and the apps you want included.
Send a test event
MetricRaven should show Connected and a Last event timestamp. A test event does not add revenue.
Link app purchases to visitors
Use the same canonical user ID in RevenueCat and MetricRaven's Identify API. Example with RevenueCat's React Native SDK:
// In your app after authentication, use your canonical user ID.
// Example: RevenueCat React Native SDK (react-native-purchases).
await Purchases.logIn(authenticatedUser.id);
// Optional: if your web-to-app flow carried the MetricRaven visitor ID safely:
if (visitorId) {
await Purchases.setAttributes({ metricraven_visitor_id: visitorId });
}Verify it works
A real purchase appears in Revenue in its original currency. A test webhook only verifies delivery and authentication.
Details
- Production purchase and renewal events add revenue. Refund events reduce it; an ordinary subscription cancellation is not a refund. Sandbox purchases are ignored.
- This connection receives new events. It does not import your RevenueCat history.
- For a website-to-app journey, your own sign-in or deep-link flow must carry the user or visitor identity across. The web tracker alone does not track mobile app screens.
- If Stripe is also connected, RevenueCat events for the Stripe store are skipped to avoid counting the same payment twice. Don't also forward the same purchases through the Payments API.
- Generating a replacement authorization header invalidates the old one; update RevenueCat immediately.