RevenueCat

Introduction

With RevenueCat, you can allow your app users to purchase subscriptions, ensure that users pay to access specific pages, and more.

MoEngage <> RevenueCat

The integration between RevenueCat and MoEngage ensures a seamless synchronization of your customers' purchase and subscription lifecycle events across various platforms. This integration enables you to construct campaigns catering to your customers' subscription lifecycle stages, such as pushing notifications to customers nearing their subscription expiry or addressing those whose transactions have repeatedly failed. With this integration, you can:

Send RevenueCat Events to MoEngage

Integration

Step 1: Set MoEngage Customer ID

For the user mapping to happen correctly on MoEngage, you need to ensure that your users' app_user_id is the same as their ID in MoEngage.

Step 2: Get your MoEngage endpoint

Please contact your MoEngage Customer Success Manager for help setting up a dedicated endpoint in RevenueCat.

Step 3: Set up Webhooks in RevenueCat

Register the Webhook in RevenueCat. Navigate to your project in the RevenueCat dashboard and find the Integrations card in the left menu. Select + New
Choose 'Webhooks' from the Integrations menu.
Give a name to your Webhook.
Enter the MoEngage endpoint we gave you.
For the Authorization header value:

Get your Basic Token by using any online Basic Auth Header Generator tool. Enter your Workspace ID as username and Data API Key as password (MoEngage Dashboard >> Settings >> APIs). Your final token should look like this:

Basic Qk5CR1NNNUR4eHh4eHhWQ1hSRFJEWTdSOlFsWHVoTHVaeHh4eHh4QWQrQnBYUEotNw==

Paste this as the header value.

Select whether to send events for production purchases, sandbox purchases, or both.
Select if the webhook events should be sent only for one app or all project apps.
(Optional) Filter the kinds of events that should be sent to the webhook URL.
You can test your Webhook by clicking on "Send test Webhook":

Step 4: Send targeted campaigns on MoEngage

Your users and events should start showing up in MoEngage:

You can now run event-triggered campaigns to your users.

Events Supported

Event name	Description
INITIAL_PURCHASE	A new subscription has been purchased.
RENEWAL	An existing subscription has been renewed or a lapsed user has resubscribed.
CANCELLATION	A subscription or non-renewing purchase has been cancelled or refunded.
UNCANCELLATION	A non-expired cancelled subscription has been re-enabled.
NON_RENEWING_PURCHASE	A customer has made a purchase that will not auto-renew.
SUBSCRIPTION_PAUSED	The subscription has set to be paused at the end of the period.
EXPIRATION	A subscription has expired and access should be removed.
BILLING_ISSUE	There has been a problem trying to charge the subscriber.
PRODUCT_CHANGE	A subscriber has changed the product of their subscription.
TRANSFER	A transfer of transactions and entitlements was initiated between one App User ID(s) to another.
SUBSCRIPTION_EXTENDED	An existing subscription has been extended (the expiration date of the current subscription period has been pushed back to the future).
TEMPORARY_ENTITLEMENT_GRANT	RevenueCat was temporarily unable to validate a purchase with the respective store and has granted a short-term entitlement to the customer.

Click here for an updated list of events being sent from RevenueCat to MoEngage.