Skip to main content
Question

Huge flaw in revenucat experiments with placements?

  • April 9, 2026
  • 1 reply
  • 18 views

Forum|alt.badge.img+3

Well, this is something annoying...


Suppose you are using placements to show different paywalls throughout your app. In our case we have around 20 different placements. For all sorts of various products and different intent triggers.

Now, if you want to run an a/b test (experiment) for ONLY one of these placements, like “onboarding” paywall. You end up in a world of shit…

1. First you must create your experiment with all the placements, or paywalls would start getting wrong offerings.
2. Then, your data will be polluted by ALL purchases done from every placement in the app.

So, its virtually impossible to get any reliable data for your “onboarding” placement test.

You would like to create an experiment for ONE particular placement ONLY.

As it is now, as your app grows and you get more than a single paywall, the experiments are getting worthless.

Is there going to be a better RevenueCat experiment update for this in the near future? Or do we need to start looking for other ways to a/b test monetization? I mean with “near future” something like in a couple of weeks.

1 reply

erik-macinnis
RevenueCat Staff
Forum|alt.badge.img+1
  • RevenueCat Staff
  • April 13, 2026

Hi Emil,

I’m Erik, happy to help!

At the moment, there isn’t a way to run experiments on a single placement only. You are correct that experiments apply across placements, which can make it difficult to isolate experiment results for an individual placement.

Charts V3 does provide the ability to filter and segment by placement across many charts, which can help you analyze performance for each placement.

In terms of roadmap, I’m not aware of support for placement specific experiments in the near term. We do have plans to improve placement level segmentation when analyzing experiment results, but nothing expected in the next couple of weeks.

Thank you for the valuable feedback, I’ll pass it along to the team.

Let me know if you have any questions.

Warm regards,
Erik - Developer Support Engineer