Let people skip the first paywall, then show another when they hit submit

JosephSo, this is one experiment. Is this like the winning one?

Dillion VermaSo far, the weekly's been really good for us, so we've been just running with weekly. We have tested some yearly in the past. We went away from that, but we'll also test that again. But our standard go-to so far has has been weekly and yearly. I think also this is another example. This is just trial cancel paywall, but it's like a different use case. But, yeah, to be honest, like that that's like the the main overall. So, weekly, yearly. I have a bunch of other paywalls for different different cases or scenarios like production abandon or if they cancel the trial. We also have an interesting setup where we have two paywalls for our onboarding, and the combined two paywalls actually have a higher conversion rate from what we've seen from our testing. So, if we go over here, this is an example of what that looks like.

Dillion VermaThe the non-gated and gated paywall, both have 16.5% conversion rate. But what's happening here is we present users with a paywall during onboarding, but they're allowed to skip it. They can close it and skip it and move on and get into the application, and they can go into the application, they can like look around for a bit and like do whatever they want, but then once they want to take an action in the application, the second paywall comes up, which is the gated paywall, this one over here. Both of these paywalls combined have a higher conversion rate than just having one alone, and we've seen this like multiple times.

JosephThat's very interesting. So, essentially, it is a hard paywall because you can't access the core functionality of the app unless you pay, but that for you has outperformed just putting one hard paywall and not allowing the user to like poke around. Do you have any theories for why this is happening?