Solved

Adding our App User IDs to already existing anonymous subscribers

  • 26 October 2021
  • 1 reply
  • 207 views
A
Badge +4

We launched our app using Anonymous App User IDs. Now as we have some subscribers we would like to use our own App User IDs for all our users (paying and non-paying). 

 

To implement own App User IDs the documentation suggests either providing our own App User ID in configure/setup or in logIn. However it’s not clear form the docs if this will cause the paying user loosing their entitlements for the current app session or until they restore purchases. For us this would be a very bad user experience. We would really like to avoid it.

 

How to properly migrate our subscribers to our own App User IDs without affecting or loosing subscribers entitlement details?

icon

Best answer by tina 27 October 2021, 22:55

View original

1 reply

tina
Rank
Userlevel 5
Badge +10

Hi @Anton B 

This will not cause paying customers to lose their entitlement access. When they logIn and you provide the app user ID (usually from associating the app user ID with a user authentication), this will alias the app user IDs together, acting as the same customer going forward. From the docs:

When going from an Anonymous ID to a Provided ID RevenueCat will decide whether the identities should be merged (aliased) into the same PurchaserInfo object or not depending on the state of the Provided ID and if it already has an anonymous alias.

Reply


Terms & ConditionsCookie settings