Skip to main content
Question

What does "other" mean in Experiments?

  • February 3, 2026
  • 1 reply
  • 13 views

Forum|alt.badge.img+5

So we’ve been running an experiment for about a week now, and discovered a row called “other”.

 

We’re guessing that it is counted as “other” when a user changes the product, say from Monthly subscription to Annual subscription in the device settings or app store. (*not* within the app or RevenueCat paywall)

 

The question is, if our understanding is correct, how does this affect the actual offerings rows? 

For example, If a user changed from monthly subscription to annual subscription, then is monthly subscription counted -1 and annual subscription counted +1 in the Experiments report table? Or do the numbers not change once they’re counted?

 

Thanks!

1 reply

erik-macinnis
RevenueCat Staff
  • RevenueCat Staff
  • February 3, 2026

Hi there,

I'm Erik, happy to help clear this up.

The other row appears when a customer who is enrolled in the experiment purchases a product that isn't included in any of the experiment's offerings.

How does this happen:

  1. Customers are enrolled in the experiment (assigned to a variant)
  2. Once enrolled, all their purchases are attributed to their variant
  3. If a customer later purchases a product outside the experiment’s offerings (for example, via App Store subscription settings or a special offering), the purchase will still be attributed to their assigned variant, but it will appear as other.

You can read more about the other category in our documentation: https://www.revenuecat.com/docs/tools/experiments-v1/experiments-results-v1#:~:text=customers%20enrolled%20in%20your%20experiment

Regarding how this affects your offerings rows:
The numbers don’t change once their counted. If a user purchases a product included in the experiment and later switches to a product outside the experiment, the original purchase count remains unchanged, and the new purchase is counted under other.

Let me know if you have any other questions!

Cheers,
Erik - Developer Support Engineer