Key takeawayGoogle Play's in-app review API shows a rating card inside your app without sending users to the store. Trigger it from a success moment (order delivered, booking confirmed, fifth visit) — your website can signal the app through a bridge or a special URL. Google limits how often the card appears and may not show it at all, so never put it behind a button or ask “do you like us?” first.
- API
- Google Play In-App Review
- Trigger
- After success moments
- Quota
- Limited by Google
- Don't
- Gate or bribe ratings
How it works
The app calls Play's review flow; Play decides whether to show a small card with stars and an optional comment. The user never leaves the app, and the rating goes straight to your listing.
Good moments
- After an order is delivered or a booking completed.
- After the user's third or fifth session.
- After completing a course module or a level.
Bad moments
- On first launch.
- Right after an error or a failed payment.
- In the middle of checkout.
Rules
- Don't ask “Do you love the app?” and only show the prompt to people who say yes — that's review gating and against policy.
- Don't offer rewards for ratings.
- Don't put the prompt behind a button; Play may not show it, and the button then does nothing. Use a normal link to your Play listing for “Rate us” buttons.
Triggering it from your website
Converted apps that support the API usually expose it through a JavaScript bridge or a special URL your site can open after a success event. Check your converter's docs.
Frequently asked
Why doesn't the review card appear when I test?
Play applies quotas and won't show it every time — especially to the same account repeatedly. Use internal app sharing or a test track to see it.