Users storage with Firebase integration

Badge +2

Hi guys!

I’m about to launch the new version of my app with Revenue Cat. 

I did enable the Firebase integration as I want to store info about my users in it. 

My application also need to store a few additional info about my user (extra metadata like locale or application specific info).

My application communicates with my API (that needs to know the entitlements of my users, so I’m also using the Rest API).

The thing is… I have data about my users dispatched at 3 different places:

  • In RevenueCat (where I have useful information like the last app version, device version, last seen, etc...). 
  • In firebase (where i have entitlements and stuff from RevenueCat but not all the data enumerated above)
  • In my API local MySQL database (where I store the additional data that I need for my user like locale or application specific stuff)

So If I want a complete vision of my users, I need to aggregate all this different sources. 

It’s quite difficult as there is no way to retrieve the full list of users from the Rest API.

Is there a way I could simplify this? Like adding my own metadata in the RevenueCat SDK and store them in RevenueCat and configure the Firebase Extension to store everything in Firestore?




2 replies

Userlevel 4
Badge +8

Hi, our APIv2 has an endpoint to get a list of customers. You can enroll in our beta here to use it:

In regards to simplifying this, I would recommend that you use the Firebase UID as the RevenueCat app user ID when setting the Firebase user identity in RevenueCat, see our docs here for more details on this:

Additionally if you use custom claims then entitlements are synced and updated between RevenueCat and Firebase, see our full docs here for details on setting this up:


Badge +2

Hi Haley,

Thank you for your reply. I though I could solve my problem with the API v2 but it’s not the case. 

The data returned for the customers are too limited. For example we don’t have access to the custom attributes. Is there any plan to update this in a near future?

Also, Firebase is unusable as well as it updates his records only when there is a event related to subscriptions (not when a custom attribute is updated for example).