Number of Variants = Product of options per element. For example: 3 headlines x 2 CTAs x 2 layouts = 12 variants. Minimum Sample Size = 12 variants x 2,000 users per variant = 24,000 total users needed. Test Duration = Required Sample / Daily Eligible Users.
Use A/B testing when you have limited traffic (under 50K monthly paywall views), want to test one major change, or are early in your optimization journey. Use multivariate testing when you have high traffic (50K+ monthly views), want to find interactions between elements, and have already optimized individual elements through A/B tests. Start with A/B, graduate to multivariate.
You need enough users per variant to reach statistical significance. With 12 variants, you might need 2,000+ users per variant = 24,000+ total users. This is why multivariate testing requires high-traffic apps. If your monthly paywall traffic is under 20,000, stick with simple A/B tests or use Bayesian methods to get faster results.
The highest-impact elements to test in combination: headline copy, CTA button text, price display format (monthly vs annual anchoring), hero image or illustration, social proof placement, and feature list order. These elements often interact — a headline that works with one CTA might not work with another. Testing them together reveals these synergies.
The number of unique users who engage with the app at least once in a 30-day period. MAU is a top-level engagement metric and often serves as the denominator in conversion rate or retention analysis.
A metric that measures how often users return to the app by comparing Daily Active Users (DAU) to Monthly Active Users (MAU). A higher ratio (closer to 1.0) indicates stronger user stickiness and habitual usage. The usage patterns of your users will change based on the category and type of app. For example, social media and gaming apps expect a much higher MAU/DAU ratio. Apps that only make sense to use once a week or a few times a month shouldn't measure themselves the same as a game.
The party legally responsible for processing payments, managing refunds, and handling tax compliance on behalf of the app. In most mobile apps, Apple or Google act as the merchant of record, while web-based apps often use Paddle, or similar providers.
A third-party tool - like Appsflyer, Branch, or Adjust - that attributes installs, measures campaign performance, and tracks in-app behavior across paid and organic channels. MMPs can be helpful for understanding CAC, LTV, and ROI in a privacy-compliant manner.
The predictable revenue generated from active subscribers on a monthly basis. MRR is a key metric for assessing growth, financial health, and the impact of marketing or retention initiatives in subscription-based apps.
Botsi automatically shows the right price to every user. Stop guessing and start growing.