Add paywalls at app open, after scans, and on cancel before testing designs

Joseph Choibut you're saying that you can offer it after each scan or after each like certain user action. What's the best practice on that? Are you just supposed to put it like basically everywhere?

Vahe BaghdasaryanThere are like a few very important placements. Uh I mean, transaction abandonment itself is a placement. But then there are some other things that like are very important and high impact. The one is on session start, like showing a paywall on every session start, at least like once per day. If users use your app to do some sort of action, like take notes, scan products, you can show them once every X times they do an action. If you have a freemium version of the app and you give away like let's say five scans for free, you can remind them, "Hey, you are almost out of your scans." On your paywall, "Hey, subscribe to keep unlimited scans."

Joseph ChoiWhat are some of like quick wins that people can get um if they've just launched and they're getting traction and they just want to do a couple of first experiments?

Vahe BaghdasaryanDefinitely A/B tests around like multi-step paywalls, that's kind of a very good kind of leverage you could have. If you don't have transaction abandonment paywall in placed, put it there. If you don't have a session start paywall, put a session start paywall. You don't need to experiment, you just need to build your foundation that you can experiment later. Make sure you cover every possible placement, you don't leave any kind of a money in the table by not having some sort of like a placements. You cover all of this, and then think about experimentation.

Joseph ChoiGreat. This this was really educational. I I learned a ton about paywalls. Um is there anything else that you wanted to cover here?