Skip to main content

Hello,

I was wondering if you could provide additional guidance on handling anonymous IDs. We are following the recommendations for enforcing Custom App User IDs (as described here: RevenueCat Docs). However, we still frequently receive webhooks containing anonymous IDs.

We determined that most of these cases occur from users resubscribing through the App Store/Play Store. Additionally, during the recent RevenueCat API outage, we noticed webhooks with anonymous IDs. From the RevenueCat dashboard, we observed that the Custom App User IDs were not associated with the anonymous IDs until several hours after the outage was resolved.

I have a few questions regarding this:

  1. Backend Association – What is a reliable way for our backend to associate an anonymous user ID with our custom user ID?
  2. Client Access – Is there a way for the client to retrieve the anonymous ID assigned to a user?
  3. Ensuring Custom IDs – Do you have any additional best practices or guidance on preventing anonymous IDs from being assigned to users?

Any insights would be greatly appreciated. Thanks in advance for your help!

Hi! I am sorry to hear that you are having difficulty managing this. 

In terms of your first question, using the Scheduled Data Exports is a good option, which I can see that you are already using. If you would like, we have another option that you may find useful. Can you create a private support ticket so that we can speak about it further? 

 

In terms of your second question, we do share the original app user ID within the CustomerInfo object.

 

In terms of your third question, our best practices are outlined in the documentation, most important being not calling configure without a custom app user ID or calling the logout method. We would also be happy to investigate where these anonymous app user IDs are coming from more deeply in your private support ticket so that we can take a look at your code.

Reply


Terms & ConditionsCookie settings