We are considering using Revenuecat for cross-platform support, but our service, is designed so that the same user can have multiple accounts, and the system does not keep track of which users have which accounts. We are told that cross-platform support requires the use of a custom App User ID to track users across platforms, but if our app's user_id is set to a custom App User ID, they will be treated as different users, and we will not be able to track users if the platform changes. How can we achieve cross-platform support while preventing duplicate purchases of the same subscription plan when the same user currently has multiple accounts? Would we need to build a separate system to have users decide on a parent user_id and integrate them even if they have multiple accounts, so that Revenuecat sees a one-to-one relationship?
Question
Regarding cross-platform support and control of duplicate purchases of the same plan for multiple accounts
This post has been closed for comments
+9Hi
There are two ways to do this:
- You can use the parent ID technique you mentioned. You would provide the parent ID as the app user ID to RevenueCat and keep track of which accounts are connected to the parent ID on your end.
- You can also alias app user IDs together in RevenueCat, so several app user IDs can all point to the same user record and set of purchases in RevenueCat. This is a rather dangerous API endpoint so we don’t tend to share it publicly, if you’re interested I can DM it to you.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.