Skip to main content
Question

RevenueCat webhooks only return anonymous app_user_id even after logIn() with custom user ID

  • September 17, 2025
  • 1 reply
  • 32 views

Forum|alt.badge.img

In our iOS app we call:

Purchases.logIn("ourCustomUserId")

RevenueCat returns our custom user ID correctly, and in the dashboard we see the customer under that ID. ✅

But when a purchase happens, the webhook event only sends back:

"app_user_id": "SRCAnonymousID:xxxx"

There is no original_app_user_id or aliases in the webhook payload.

 

This makes it impossible to match purchases to the correct user in our backend.

Question:

  • Why are webhooks still sending the anonymous ID instead of the logged-in custom ID?
  • Shouldn’t webhook V2 include original_app_user_id and aliases so we can map it properly?
  • How can we fix this so webhook events always include our real app user ID?

 

This post has been closed for comments

1 reply

wes_clark
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • September 19, 2025

Hi! I took a look at your app and am seeing that you currently have the option enabled to have server notifications be used in order to track new purchases. Because of how we handle tracking the app user ID in this case (documentation on the topic), that could potentially lead to a transaction being detected first through the server notifications, rather than being sent from your app itself, which would mean that it could be applied to an anonymous app user ID. I would be happy to confirm this theory if you share the specific app user ID where you saw this issue, so that I can examine the data on our end. If you would rather not share that information publicly, you can also create a private support ticket