Hey, we use RevenueCat together with Superwall (using a Purchase Controller). There is no documentation on how to set up pricing experiments in this scenario.
Since you configure products and entitlements in Superwall by tying them directly to an AppStore product identifier, I don’t see a way to use the Revenuecat experiment feature. I think for that to work, Superwall would have to use the RC current offering.
So I think the only way to set this up would be to define a new product / offering in App Store and then in RevenueCat and Superwall, which gives access to the same entitlement, and run the A/B test in Superwall. We could then probably segment a chart in RC by offering to see results there as well.
Or am I missing something?
Question
How to run pricing experiments with Superwall
+1This post has been closed for comments
+6Hi Ole,
Thanks for reaching out. I’m happy to help!
Running pricing experiments in RevenueCat is straightforward once you’ve set up your Offerings. However, adding Superwall into the mix does make things more complicated.
I’ll layout two ways through which you can run price experiments for your application, you can pick whichever suits you best.
1. Use RevenueCat Experiments for running the price test.
Make sure you have at least two Offerings (e.g. “Control” and “Treatment”), each containing the packages/products you want to test (e.g. different price points or trial lengths).
In your project sidebar, click Experiments, then + New to create a brand-new price test. Give your experiment a name, select your Control Offering and your Treatment Offering, choose your audience (e.g. 100% of new customers), and hit Create Experiment.
In your app code, call RevenueCat’s getOfferings to retrieve the current offering for the user. Don’t hardcode an App Store ID always pull the product from RC so experiments can swap in the variant.
Use the offering data to present a custom paywall to the user, you can either create a Paywall UI youself or pass the offering data to Superwall (although I am unsure if their client-side SDK supports this.)
Alternatively, RevenueCat also supports remotely configurable Paywalls which tie seamlessly with our experiments. All you have to do is create these paywalls within RC, attach them to their respective offerings. And then instead of calling getOfferings call presentPaywall it will automatically get the correct offering for the current user, and then display the paywall attached to it.
By doing things this way you get reduced complexity, built-in audience targeting, seamless paywall integration, unified analytics, and a whole host of other benefits.
You can learn more about getting started with RevenueCat Experiments here.
2. Use Superwall A/B Testing for running the price test.
If you’d rather run the A/B test entirely in Superwall, you can indeed create two distinct products in App Store Connect, mirror them in RevenueCat and Superwall, then let Superwall handle the assignment.
You can then segment your RevenueCat charts by product to compare performance. That’s a perfectly valid fallback if you prefer Superwall’s control over experiment rollout.
Hope this helps. Let me know if you have any other questions. I’m happy to help however I can.
Best,
Hussain
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.