Understanding RevenueCat Integration

Learn how FunnelFox communicates purchases with RevenueCat side

It is best to understand how FunnelFox communicates with RevenueCat, so that you can avoid any misunderstanding before release.

All communications can be divided into 3 actions:

  1. Creating RevenueCat customers
  2. Granting entitlement to existing profile
  3. Revoking entitlement from existing profile

1. Creating RevenueCat customers

FunnelFox creates a new RevenueCat profile, when user buys a subscription on your onboarding. Buying a consumable product will not create a new account.

So, as soon as user completes a checkout, new RevenueCat profile is created.

By default, this RevenueCat profile will be given a App User ID equal to their email. This will later allow you to identify this user in your application.

If you'd like to, you can change App User ID to any value by adding custom code on the second screen. To do that, please use the Raw HTML component and add this script:

<script>const id = "{{user.id}}"; fox.inputs.set("_USERID_", id); </script>

FunnelFox uses RevenueCat internal user ID to notify about changes to profile.

2. Granting entitlement to existing profile

FunnelFox grants access level to an existing user, when user has completed a transaction associated with this subscription (initial subscription payment, successful recurrent payment, etc.)

Access level expiration date is defined by subscription period end.

By default, FunnelFox tries to grant premium access level. You can provide custom access level in your checkout element.

3. Revoking access level from existing profile

FunnelFox revokes access from an existing user, when user has cancelled or paused their subscription.

If payment is overdue, RevenueCat will expire access itself without any FunnelFox updates.