Google's in-app review API lets users rate without leaving your app. Request it after a success moment, expect quotas that limit display, do not rely on it as a button response, and measure results with Play Console review and rating data.
How the flow works
Your app requests a review flow and then launches it, and the system decides whether to display it based on quotas. The app is not told whether a review was left, to protect privacy.
Check current developer documentation for implementation details.
Choose the moment
Use the same principles as other platforms: ask after a positive experience, not during an error or interruption. Avoid asking immediately after install.
Do not prompt every session.
Understand quotas and testing
Quotas limit how often the dialog appears, so do not design flows that depend on seeing it. Use testing tools provided by Google to verify integration.
Provide a separate way for users to open your Play page if they want to review.
Measure and respond
Track ratings and review volume in Play Console, and compare periods before and after enabling the prompt. Reply to reviews, especially negative ones, with useful help.
Combine with release notes to highlight fixes.
Common mistakes with Google Play in-app review API
Expecting a dialog every time ignores quotas. Another mistake is asking after a negative event. Teams also sometimes try to detect whether the user reviewed, which the API does not allow.
Forgetting to test the flow in a supported test setup leads to surprises in production.
Google Play in-app review API: a worked example
A budgeting app requests the flow after a user reaches a monthly goal. It tests with Google's tools, measures review volume changes in Play Console, and replies to new reviews.
A permanent link in settings offers a direct route to the Play page.
How to do it, step by step
- Pick the momentChoose a success event.
- Request the flowCall the API to request and then launch the review flow.
- Do not depend on displayExpect quotas.
- TestUse Google's test tools.
- Measure and replyCheck Play Console reviews and reply.
Before and after examples
Illustrative examples written for a generic app in this category, not client results. Swap in your own product, audience, and data.
At app start
After reaching a monthly goal
Why it works: A positive moment increases willingness.
Try to detect if the user reviewed
Track overall review volume in Play Console
Why it works: The API does not tell you.
None
A permanent link to your Play listing in settings
Why it works: Users can still review on demand.
Action plan
- Request after success moments
- Avoid prompting every session
- Expect quotas
- Test with provided tools
- Offer a separate review link
- Reply to reviews
Metrics to monitor
- Review volume change
- Average rating
- Review reply rate
- Prompt-attributed trend
Record the baseline, release date, audience, markets, and external changes before interpreting movement. Rankings and conversion are useful signals, but a decision is stronger when activation, retention, and business value confirm that the page attracted the right users.
Frequently asked questions
Will the dialog always appear?
No. Quotas and system decisions apply.
Can I know if a user left a review?
No; the API does not tell you, for privacy.
Can I offer rewards for reviews?
No; incentivized reviews violate policy.
Keep reading
More in Ratings and Reviews
Browse all 13 Ratings and Reviews guides
