Skip to main content
Question

how to dynamically configure when the paywall is shown?


Forum|alt.badge.img+3

I want to experiment when I show the paywall to users. For example, I want to start with 3 experiments - show it immediately after they sign up, or one week later, or one month later. Making the game free completly without a trial period or subscription until that moment.

 

I already setup 6 offerings with different price points and presentations of price options. I suppose I can create 18 offerings which are the same 6 offerings but on the 3 different time delays, but that seems like a lot. Is there a simpler way to experiment with when to show the user the paywall?

This post has been closed for comments

4 replies

joan-cardona
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 187 replies
  • October 4, 2024

Hi @DoughBoy,

If I understood it correctly, you want to experiment only when to show the paywall - not changing the pricing on the paywall. In that case you don’t need to create different offerings, just change the logic on when to show it. 

It can probably help you to use Targeting placement which can take care of a big chunk of the logic.

Let me know if this works!


Forum|alt.badge.img+3
  • Author
  • New Member
  • 4 replies
  • October 4, 2024

hey @joan-cardona , thanks for the reply.

Thanks, I didn’t realize I can configure placements like this.

But I’m still not 100% srue this solves my issuue. I was already able to dynamically decide when to show the paywall pretty easily using a remote config. It looks like I can use Placements for this now instead.

But how can I run experiments to help me test the best placement?

For example, I want some customers to see paywall at the end of onboarding, and some to see it after using the app for one full week. And maybe a third test of seeing it after 1 month.

How can I run side by side testing to see which one of these converts better, similar to how we can do experiments on price? I want to do experiments on placement.

 

thanks!


kaitlin
RevenueCat Staff
Forum|alt.badge.img+6
  • RevenueCat Staff
  • 328 replies
  • October 10, 2024

Hey @DoughBoy,

That makes sense! You can definitely do so. We have some documentation here on using placements in Experiments: https://www.revenuecat.com/docs/tools/experiments-v1/configuring-experiments-v1#using-placements-in-experiments

You can set up your variants to see different paywalls at different times in their flow. If you do end up running multiple experiments simultaneously, you’ll just want to make sure that you’re setting up your audiences as either totally unique or totally identical. In that same doc I linked above, we have some examples of how to run experiments side by side. 

Hope this helps! Let us know if you have other questions!


Forum|alt.badge.img+3
  • Author
  • New Member
  • 4 replies
  • October 10, 2024

hey @kaitlin ,

 

thanks for sharing. It seems like I can setup experiments with placements, and I will have to call the API for getting placements multiple times, once for each placement.

The alternative design is that we bake the placement info into the metadata of the offerring, by creating an attribute called ‘placement’. Then, I make new offerrings for each placement I want to test.

I’m just wondering if there’s some negative to doing the solution like this, using the metadata for the placement info. Would I be missing out on any features or analytics? the downside is that it requires creating more offerrings, but the benefit is that its simpler from the client side to make just one API call to revenuecat to get both placement and pricing info.

 

thanks!

 


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