PromptSurge

Rating conversion rate

Raise your rating conversion rate, so more prompted users actually rate

Apple shows its rating sheet at most three times a year per device, and Google applies a quota it does not publish. A native prompt that appears with no context, at a bad moment, spends one of those few chances. PromptSurge puts a short, clear ask in front of it, so the native sheet opens right after someone has agreed to leave a review.

Free plan · no credit card · iOS, Android and Unity

1 · Your pre-prompt

Your header image

A quick favor

We worked hard on offline sync. A short review helps other people discover the app.

Not nowLeave a review

2 · The native rating sheet

App Store or Google Play

Apple's or Google's own sheet, shown unchanged

Not now closes the dialog and shows nothing else.

How PromptSurge turns more prompts into ratings

The native sheet opens after a yes

When the user taps the confirm button, PromptSurge requests the native sheet at once. When they tap Not now, it requests nothing, so a moment the user turned down does not use one of Apple's three yearly displays or Google's quota. The device can be asked again after the 90-day cooldown.

Context before the stars

The native sheet only asks for a rating. The pre-prompt says why it matters, in one sentence and in the user's own language, so the sheet that follows is expected rather than a surprise.

Test the ask, keep the best one

Run several messages per language: each session gets one at random and every event records which one it was. Tap-through per language and per keyword shows which wording people say yes to.

Honest numbers at every step

The dashboard follows the funnel for both groups: devices that reached your moment, pre-prompts shown, taps through, native sheets requested. The last step, whether the user rated, is something neither store reports to any app, so PromptSurge shows your store rating count by day instead of guessing.

On the phone

What your user sees, in three steps

Same users, same moment. The difference is that they are asked first, in words about your app.

  1. Trip saved

    Available offline

    requestReview()

    Step 1

    Your code picks the moment

    Call requestReview() right after something went well, such as a saved trip or a finished level.

  2. A quick favor

    We put a lot of work into offline maps. A short review helps other travelers find this app.

    Not nowSure

    Step 2

    The pre-prompt asks in your words

    A short message that names what your app does. Not now closes it and nothing else happens.

  3. Rate this app

    Tap a star to rate

    A review that names the feature

    Offline maps saved my trip. Works without a signal.

    Step 3

    The store's own rating sheet

    A yes opens the store's sheet, unchanged. The message they just read gives them something specific to write about.

What it is built for

  1. More reviews from the same users

    People are asked at a moment you chose, with a reason to answer.

  2. More written reviews

    A message about a feature invites words, not only stars.

  3. Your keywords in their words

    Reviews that name what your app does tell the next visitor who it is for.

  4. A signal the stores read

    Apple and Google both say ratings and reviews play a part in how apps rank in search.

Your dashboard shows what changed for your app: written reviews per day, stars and keyword mentions, before the pre-prompt and with it.

Sources: Apple: App Store search · Google Play: app discovery and ranking

How it works

  1. Add the SDK

    Install the iOS, Android or Unity package and call initialize() once at launch. Then call requestReview() at a moment you choose, such as a finished level, a saved project or a completed order.

  2. Make the pre-prompt yours

    In the dashboard, write the title, message and two button labels, or let the built-in AI draft them from your own reviews. Pick a theme, add a header image on Startup and above, and accept: the copy is translated into 10 languages and reaches devices without an app update.

  3. Compare against the control group

    10% of devices never see the pre-prompt and get the native sheet directly at the same moments. The dashboard puts both groups side by side and records your store rating and rating count every day.

Measured against a control group, not assumed

Every app gets a control group. 10% of devices are assigned to it for their lifetime and never see the pre-prompt: when they reach the moment you chose, the native sheet fires directly, as it would without PromptSurge. A new app also starts with a warm-up of 50 devices on the native sheet alone, so a baseline exists before the first pre-prompt is shown.

The dashboard compares the two groups over every device that reached your review moment: how many saw the pre-prompt, how many tapped through, how many native sheets were requested. It holds back a verdict until each side has at least 50 devices.

One honest limit: Apple and Google never tell an app whether a user rated or what they wrote. So next to the funnel, PromptSurge records your store rating and rating count once a day and shows the change. It is a store total, not credited to any single prompt, and the dashboard says so.

10% control group

Assigned per device, for life. The native sheet fires directly at the same moments.

50-device warm-up

A new app starts on the native sheet alone, so the baseline comes first.

Daily store snapshot

Your average rating and rating count from each store, once a day, for apps with a store link.

Frequently asked questions

What is a rating conversion rate?

The share of users you ask who go on to leave a rating. Neither Apple nor Google tells an app whether a specific user rated, so no tool can measure it per user. What can be measured is everything up to the native sheet, in the pre-prompt group and the control group, plus the store's own rating count over time. PromptSurge shows all three.

Why not call the native API directly?

You can, and the 10% control group does exactly that, which is how you see the difference. The native sheet arrives unannounced and both stores limit how often it can appear; the pre-prompt explains the ask first and leaves the native request for a moment the user agreed to.

Does Not now cost me a native prompt?

No. Not now requests no native sheet, so nothing counts against Apple's or Google's limits. It does mean PromptSurge will not ask on that device again for 90 days.

What does Google's quota allow?

Google does not publish it. Its documentation says that calling the review flow more than once in a short period, for example under a month, might not show the card. PromptSurge's 90-day cooldown keeps each device's requests far apart.

Does a tap always show the native sheet?

Not always. Apple and Google decide whether their sheet appears, and either can show nothing, for example to someone who has already rated. That is outside any app's control, PromptSurge included. Current SDK versions skip the pre-prompt on devices where the store's limit has probably been reached, which makes an unanswered tap less likely, not impossible.

Spend every native prompt on a moment that was agreed to

Free plan, no credit card. See the full funnel, both groups, from the first day of traffic.

Create your free account →

Already have an account? Log in