Skip to main content

Changing the format of RevenueCat IDs for non-subscription purchases


Jens
RevenueCat Staff
Forum|alt.badge.img+7
  • RevenueCat Staff
  • 187 replies

In approximately one week, on April 9, 2025, we will make a small change to the RevenueCat-calculated IDs for any new non-subscription purchases happening after that date. We will increase the length of the IDs to 25 characters to avoid collisions between different purchases. This ID is exposed via our SDK, Web API, and webhooks. Subscriptions and purchases that happened before the change will not be affected.

This will likely not have any impact on the vast majority of developers – the ID was a string and remains a string, only longer (25 characters) and with more potential characters (A-Z, a-z, 0-9, -, =, and _). If you are ingesting this string in a database on your side, please make sure that the database schema accepts strings of that length.

If you have any questions about this change, please feel free to ask them below.

 

2 replies

Forum|alt.badge.img+5
  • New Member
  • 1 reply
  • April 1, 2025

Thanks for the heads up. Just to be clear, will the IDs continue to be prefixed with “$RCAnonymousID:”?


Jens
RevenueCat Staff
Forum|alt.badge.img+7
  • Author
  • RevenueCat Staff
  • 187 replies
  • April 1, 2025

Hi ​@Frederik , this change will not impact App User IDs, they will continue to have the same format you mentioned. It will only impact the RevenueCat-provided unique transaction IDs for one time purchases (for example, exposed on the `NonSubscriptionTransaction` object in the iOS SDK as the field `transactionIdentifier`).


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings