Hi RevenueCat Community,
I hope you're all doing well. I'm reaching out to seek assistance with some challenges we're facing while integrating RevenueCat into our mobile app. We would greatly appreciate any guidance or insights from the community. Here's a summary of the issues we're encountering:
User Identifier Update: We have successfully implemented webhook integrations for subscription actions, but the user identifiers provided by RevenueCat are anonymous IDs. We need to associate these actions with specific users in our app. Is there any way to update the existing anonymous IDs of our current users to our preferred user IDs? This would help us maintain accurate correlations between subscription actions and user profiles.
Subscription Cancellation Identification: Due to the anonymous IDs provided by RevenueCat, it's challenging for us to identify which user has cancelled their subscription when we receive webhook data on our server. Are there alternative methods or additional information you can share to help us identify the user behind a subscription cancellation? Any insights or suggestions would be highly appreciated.
User Migration: We're considering creating new users within RevenueCat using our preferred user IDs and then migrating their existing subscriptions to these new user profiles. This approach would allow new users to have our designated IDs while archiving or deleting the old anonymous user data accordingly. Is this possible, and if so, what would be the recommended process for user migration?
Thank you all in advance for your attention and support in addressing these challenges. We highly value the expertise of the RevenueCat community and eagerly await your responses. If you need any additional information or clarification, please feel free to reach out.
Great, but there is a problem we are facing while setting subscriber attribute, as if more than one person is using the same device for our app, it’s replacing the the attribute with previous one, it’s not identifying that other user is a different one.
How can we handle that?