Background / use case: Some time ago we changed auth providers from AWS/Cognito to Firebase/Auth. We use a RC webhook to integrate with a 3rd party CRM (Customer.io). We still get RC webhook events with the legacy Cognito app_user_id’s when the legacy subscribers auto renew (for instance) even though these legacy subscribers have new Firebase ID’s that are associated with the legacy COgnito ID’s via RC aliases.
Question: Is it possible to update the Cognito app_user_id’s with the newer Firebase ID’s? I.E. can we swap alias ID with app_user_id?
Most likely the easiest way to go about this would be to use `.login` to identify these legacy users with the new Firebase ID. If the users are already identified with the Cognito ID, this means that upon log in, going from one custom ID to another will cause the user’s customerInfo to transfer from the Cognito ID to the Firebase ID, with no aliases created: https://www.revenuecat.com/docs/customers/user-ids#login-method-alias-behavior
Does this seem like it will work for your use case, or are you hoping to have that Cognito ID still attached as an alias?
Most likely the easiest way to go about this would be to use `.login` to identify these legacy users with the new Firebase ID. If the users are already identified with the Cognito ID, this means that upon log in, going from one custom ID to another will cause the user’s customerInfo to transfer from the Cognito ID to the Firebase ID, with no aliases created: https://www.revenuecat.com/docs/customers/user-ids#login-method-alias-behavior
Does this seem like it will work for your use case, or are you hoping to have that Cognito ID still attached as an alias?
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
