How to Get More App Store Reviews (And Why Promo Codes Won't Do It)

Search for advice on getting App Store reviews and you will find the same playbook everywhere: generate a batch of promo codes, give them away, then email everyone who claimed one and ask for an honest review.

That playbook does not work. Not "works poorly" — it cannot work at all.

We sell a promo code distribution tool. It would be convenient for us if it did.

---

The thing almost nobody mentions

From Apple's own App Store Connect documentation on promo codes:

"However, customers can't rate or review the app."

Someone who installs your app with a promo code is not a normal customer as far as the App Store is concerned. The rating control is not there for them. There is no clever email sequence, no perfect timing, no follow-up that unlocks it.

So every guide describing a "15-25% review conversion rate from code claimers" is describing something that does not happen. If you have run this play and got nothing, you did not execute it badly. It was never available.

Promo codes and Offer Codes are different things, and this is worth being precise about:

• Promo codes are the free-download codes you request per app version — 100 per version, per platform, expiring four weeks after generation. Redeemers cannot rate or review.
• Offer Codes apply a subscription offer. The person who redeems one becomes an actual paying-track subscriber, so they are a normal customer with normal customer abilities.

Most "promo code" advice sloppily conflates the two. If a guide does not distinguish them, it was not written by someone who has done it.

---

The second problem: the ask itself

Even where a review is technically possible, the reciprocity framing that these guides recommend — give them something free, then ask — is the exact pattern Apple's guidelines prohibit.

Apple treats attempts to manipulate reviews as grounds for action up to removal from the Developer Program, and incentivised reviews count even when you do not specify that the review must be positive. "Review gating" — asking only the users you think are happy — is prohibited too.

The safe line is narrow and worth stating plainly: you may ask everyone for an honest review. You may not trade anything for one, and you may not filter who gets asked.

---

So what are promo codes actually good for?

They are good for the thing they are actually good at, which is not nothing:

• First users. A brand-new app's hardest problem is that nobody has opened it. Codes solve that directly.
• Testers and feedback. People who wanted your app enough to claim a code will tell you what is broken, if you ask them.
• An email list. This is the underrated one. Run a giveaway, let the codes run out, and keep capturing addresses from everyone who arrives late. Those addresses are yours, they work for your next launch, and no platform can take them away.
• Word of mouth, which is slower and less measurable than a review count, and matters more.

What you are buying with a giveaway is distribution and a list. Judge it on that.

---

What actually generates reviews

1. The in-app prompt, timed properly

This is the real lever, and most apps get it wrong by firing it at the worst possible moment.

Apple's SKStoreReviewController (or requestReview in SwiftUI) shows the native rating sheet without leaving your app. Apple throttles it to a few prompts per year per user, which means each trigger is scarce and you should not waste one.

Bad moments to ask:

• On first launch, before the user has experienced anything
• Immediately after a crash, an error, or a failed action
• In the middle of a task you just interrupted

Good moments to ask:

• After the user completes your core action for the third or fourth time — repetition is the clearest signal they are getting value
• Right after a visible success: the export finished, the file synced, the streak hit a week
• After a moment of relief, not a moment of effort

The implementation is trivial; the discipline is in the trigger. Count meaningful actions, and only prompt once the count proves engagement:

func didCompleteExport() {
    let key = "completedExports"
    let count = UserDefaults.standard.integer(forKey: key) + 1
    UserDefaults.standard.set(count, forKey: key)

    // Only ask once they've clearly got value out of it.
    if count == 3, let scene = UIApplication.shared.connectedScenes
        .first(where: { $0.activationState == .foregroundActive })
        as? UIWindowScene {
        SKStoreReviewController.requestReview(in: scene)
    }
}

Note what this does not do: it does not check whether the user seems happy first. That would be review gating.

2. Fix the thing your reviews already complain about

Your existing negative reviews are a free, unusually honest bug report. Read the last twenty. There is almost always one complaint that recurs.

Fixing that one thing does more for your rating than any campaign, because it stops the inflow of one-star reviews at the source. Ratings are an average — you improve it faster by not earning bad ones than by chasing good ones.

3. Respond to reviews

The lowest-effort item on this list, and the most neglected.

You can respond to any review in App Store Connect. Potential users read those responses, and a developer who answers a one-star review thoughtfully reads as more trustworthy than one with a wall of five stars and total silence.

For negative reviews: acknowledge the problem without getting defensive, say what you have changed or will change, and offer a direct line — "email me and I'll sort it out." People sometimes update their review afterwards. That is worth more than a new review, because it moves a one-star to a four-star.

For positive reviews: reference a specific detail so it is obvious a human read it.

4. Ask in the places where reviews are allowed

Your email list, your in-app messaging, your Discord, your update notes. Ask everyone, ask for honesty, and link straight to the review sheet with the ?action=write-review parameter on your App Store URL.

---

A realistic expectation

Unprompted reviews are rare — the large majority of users will never leave one, which is why a well-timed prompt matters so much more than volume of downloads.

The honest sequence is: get users, make the app good enough that a prompt is welcome, prompt at the right moment, and fix what people complain about. There is no shortcut where free codes convert into ratings, because the platform does not permit it.

---

The 20-minute audit

1. Find the one complaint that recurs across your recent negative reviews.
2. Respond to every unanswered review from the last month.
3. Check where your in-app prompt fires. If it is on launch, move it behind a success event.
4. Add a review link to whatever you already send your users.
5. Stop budgeting for review-generation tactics that trade something for a rating.

---

If what you actually need is first users and an email list, that is what a code giveaway is for. Promo Code Queue hands out your codes from one link — one per person, bots blocked — and keeps the email address of everyone who shows up, including the people who arrive after the codes are gone. It will not get you reviews, and neither will anything else that gives codes away.