App Store conversion rate calculator.
Calculate a store rate from matched counts, then compare percentage points with relative change. Choose the metric first: a download, a listing click and a first session describe different actions.
Your calculation
Enter matched counts to calculate a rate. Add both earlier counts only when you want an arithmetic comparison.
What goes into an App Store conversion rate?
Apple’s current metric definition uses eligible downloads and pre-orders divided by unique device impressions. A pre-order is counted when placed and is not counted again on download. Use the console’s matched scope rather than adding incompatible exports. Product page views are a separate measure, so replacing unique impressions with page views changes the question.
Google Play conversion rate and CTR in 2026
Google’s current listing performance reports emphasize visitors, clicks and click-through rate. A click indicates intent to install, open or pre-register; it does not establish that an acquisition completed. Completed acquisitions remain available in other reporting areas. Copy the exact metric and scope from your console, and avoid combining counters that may contain the same users.
Percentage points are different from percentage change
In a fictional comparison, an original listing has 100 outcomes from 1,000 opportunities: 10%. A later version has 120 from 1,000: 12%. The absolute difference is 2 percentage points. Relative to the earlier 10% rate, the difference is 20%. Both describe the same arithmetic; neither establishes that the design caused the change.
If the earlier rate is zero, relative change is undefined. A change from zero to a positive rate can still be expressed in percentage points. If a ratio exceeds 100%, the calculator preserves the entered arithmetic and asks you to review event counts, uniqueness and scope. It does not silently replace the denominator or force the result into a 0–100 range.
Separate a before-and-after observation from a store experiment
A different campaign can bring visitors who already know the brand. A new country mix can change the aggregate rate even when each country’s rate stays the same. An app release may repair an install or activation problem during the same period as a screenshot edit. Record these changes before choosing a cause. Preserve the original report alongside its period and filters so another teammate can reproduce the calculation.
This calculator does not test statistical significance, estimate a required sample size, or reproduce Apple or Google’s experiment confidence. Use the platform’s experiment result for the tested comparison. A report asking for more data stays inconclusive; a positive arithmetic difference does not override it. Private screenshot comprehension feedback can explain a misunderstanding, but it answers a different question from an experiment’s measured response.
Build a small reporting record before changing the listing
- Save the report name, metric definition, counts, period, source, country and language.
- Record the current assets and one specific hypothesis for the proposed change.
- Compare matched segments before aggregating different audiences.
- Check the store experiment’s own result separately from the arithmetic here.
- Review first-session completion, support and retention before deciding the change helped your product.
A fictional shared-expense app might find that fresh readers mistake a settlement screen for bank transfers. A private comprehension test can identify that mismatch. The owner can revise the screenshot using a real supported screen, then evaluate the listing response in its own console. No conversion percentage is promised by that feedback task.
Investigate the expectation behind the number.
List a focused task on RateMyApp to collect private feedback about what the listing promises and whether the app delivers it. Public store ratings remain independent and voluntary.
List your app for feedbackDefinitions checked October 5, 2026: Apple metric definitions · Google Play listing performance definitions.