Skip to main content

If a user is first identified with an anon ID, then logs in to my app and is signed in to revenuecat with a custom ID, does that custom ID always override as the app_user_id?

The documentation explains how aliases are merged, but doesn’t say which ID is set as the main app_user_id (e.g. for webhook data). https://www.revenuecat.com/docs/user-ids#login-method-alias-behavior

 

I’m using the Firebase RevenueCat extension, and I want to be sure that the app_user_id will always be my custom ID if one is set, because the extension syncs data to firestore via that id. If it uses the anon id, then the data will not be correctly synced.

 

During testing it seems like this is the case, but I want to be sure. Will the custom ID always become the app_user_id?

Actually I’m noticing that for transfer events, the app_user_id used is consistently the anonymous $RC ID (for both sender and recipient). So the firebase extension is syncing data to phantom uids in my database. Is there a reason that these events would be different? And Is there any way to prevent it without forking my own version of the firebase extension?

 

This issue was resolved within a support ticket. Just to summarize:

The Firebase RevenueCat extension currently reports the most recent App User ID within events. This was not ideal for @bene since the goal was to sync the known App User IDs if they were available instead of anonymous IDs. @bene found a workaround within Firebase, and we have reported this as a feature request / product feedback to the team working in the area.

 

 

@Yousef @bene What was the workaround you came up with?

Reply


Terms & ConditionsCookie settings