Skip to main content
Question

Alias array

  • December 10, 2025
  • 1 reply
  • 20 views
V
Forum|alt.badge.img+5

I want to confirm: in RevenueCat webhook events, is app_user_id guaranteed to be included in the aliases array? Same question for original_app_user_id.

For this scenario:

  1. Fresh install, new $RCAnonymousID:123 created, app_user_id = $RCAnonymousID:123
  2. User taps restore (no logIn() call in this session)
  3. RevenueCat merges a previously known ID with this new anonymous ID. The previous ID could be either $RCAnonymousID:567 or john123 (set via logIn() in a prior session on another device).

At the time the webhook event fires:

  • Is app_user_id the previous ID ($RCAnonymousID:567 or john123)?
  • Does aliases contain both the previous ID and the new $RCAnonymousID:123?

I'm pretty sure, but want 100% confirmation.

1 reply

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • jeffrey_bunn
  • RevenueCat Staff
  • December 12, 2025

Hi ​@victoria-park-dbb064! Do you have a real app user ID (or several) where you tried this? I’d like to dig in to understand the exact behavior in your app. I ask because the flow you’re describing implies that your usual flow is:

  1. Configure (with no ID provided), which creates an anonymous ID
  2. logIn is called with a custom ID, which aliases/merges the IDs together
  3. A purchase is made

However, in the flow you described, john123 already has $RCAnonymousID:567 aliased to them, which means that $RCAnonymousID:123 will not be aliased as per our alias behavior (and thus not included in webhooks).

If you can share IDs where you tried this flow (or if I’m misunderstood your typical identity flow), please let me know. Thanks!

Terms & ConditionsCookie settingsAccessibility statement