Skip to main content
Question

RCAnonymousId webhooks

  • October 14, 2025
  • 1 reply
  • 40 views
T
Forum|alt.badge.img

My app requires login, so when i call 

Purchases.configure(new PurchasesConfiguration.Builder(mActivity, apiKey).appUserID(customUserId).build());

i always pass a  customUserId, that i expect to receive on the webhooks to track user purchases on my backend.

I also never call logout.

 

On RC backend i have these options activated:

  • Tracking new purchases from server to server notifications.

I understand that the server to server event might sometimes arrive before the SDK one, thus an anonymousUserId is created and the corresponding webhook does not provide usefull user information (customUserId). My question is once the SDK updated information arrives to RC backend, is a new webhook created with the updated info? Or do i need to listen for a diferent kind of webhook when the alias with my customUserId is created on a later time? I don’t want to be polling RC backend to detect these changes.

I could disable server-to-server event, and probably will, but i worry that i might will lose tracking of all purchaces unless RC makes sure that i will receive 100% the correspoding webhook, even with some delay, with the correct customUserId. Is that the case?

 

 

 

This post has been closed for comments

1 reply

jeffrey_bunn
RevenueCat Staff
Forum|alt.badge.img+6
  • jeffrey_bunn
  • RevenueCat Staff
  • October 16, 2025

Hi ​@teo! Firstly, we recommend not using server purchase tracking with the Keep with original App User ID transfer option. More information on the various considerations with this feature can be found here: https://www.revenuecat.com/docs/projects/restore-behavior#considerations-for-enabling-track-new-purchases-from-server-to-server-notifications

If you have a Google Play app, I’d especially suggest not using this option (combined with your transfer setting). We have a flowchart on which option to choose here that you may find helpful: https://www.revenuecat.com/docs/projects/restore-behavior#considerations-for-enabling-track-new-purchases-from-server-to-server-notifications

For iOS apps, you can use this option combined with your transfer setting, but you must ensure that your custom user IDs are valid UUID v4 IDs. More information on Apple-specific considerations can be found here: https://www.revenuecat.com/docs/platform-resources/server-notifications/apple-server-notifications#tracking-new-purchases-using-apple-app-store-server-notifications

My question is once the SDK updated information arrives to RC backend, is a new webhook created with the updated info? Or do i need to listen for a diferent kind of webhook when the alias with my customUserId is created on a later time? I don’t want to be polling RC backend to detect these changes.

Once we receive a purchase, we will not create an additional webhook with the same purchase. Additionally, we do not send `alias` event webhooks (only `transfer` webhooks), so you won’t be notified when users are aliased together.

I couldn’t locate your project, so I can’t see which stores your app is available on, but based on the above, I’d suggest turning this setting off, particularly if you want to keep your current transfer setting.

Please let me know if you have additional questions!

Terms & ConditionsCookie settingsAccessibility statement