• App Store
  • Reviews
  • AI
  • Alerts
  • Mobile apps

App Store review summaries: how to read and improve yours

App Store review summaries explained for developers: how Apple writes them, how to read yours through the API, why fixed bugs linger and what you can change.

Author
Extenify Team
Published
Reading time
13 min read
A pad of peach sticky notes with a black pen lying across it on a silver laptop keyboard

App Store review summaries are the short, AI-written paragraph that sits above the reviews on an App Store product page. For many people it is the only part of your reviews they read, which makes it one of the most visible pieces of text about your app that you did not write. It can also be out of date: a bug you fixed two releases ago can still be the second sentence.

This guide is for iOS developers and the people who watch an app's reputation. It covers how Apple generates the summary and what that means in practice, where you can read yours in App Store Connect, how to pull it through the App Store Connect API and get told when it changes, why fixed problems linger, and the honest levers you have to change what it says.

Key takeaways

  • Review summaries are generated by large language models from user reviews and are "regularly refreshed on an ongoing basis." Apple shows them in the US and eight more English-language storefronts, only for apps with enough reviews.
  • Apple's pipeline picks topics mainly by how often they come up, with extra weight for balance, helpfulness and freshness. A complaint many people wrote about stays a candidate until newer reviews outnumber it.
  • You can read your summary for each storefront with GET /v1/apps/{id}/customerReviewSummarizations in the App Store Connect API, so you can save it daily and alert on changes.
  • If a summary is wrong, report it from Ratings and Reviews > Review Summaries in App Store Connect. Resetting your summary rating does not remove old written reviews.
  • The lasting fix is new reviews from people who used the fixed version, which means fixing the issue, then prompting at the right moment within Apple's three-prompts-a-year limit.

What App Store review summaries are

Apple added review summaries to the App Store with iOS 18.4 in 2025. Apple's ratings and reviews guide describes them this way: "Generated using large language models (LLMs), each summary compiles highlights and key information from individual user reviews into a short paragraph." The same page says summaries "are regularly refreshed on an ongoing basis" and that, as part of a phased rollout, they are available in eight storefronts in addition to the United States: English summaries in Australia, Canada, India, Ireland, New Zealand, Singapore, South Africa and the United Kingdom.

Three practical consequences follow:

  • Not every app has one. A summary needs enough reviews to summarize. Small apps and new listings may not get one at all.
  • It is per storefront. Your US summary and your UK summary are separate texts built from separate reviews, the same way the App Store rating differs by country.
  • It is short. Apple's machine learning team says the output is "an informative paragraph between 100 - 300 characters in length." That is room for two or three themes, so whatever makes the cut gets a lot of attention.

How Apple generates the summary

Apple published the design in An LLM-Based Approach to Review Summarization on the App Store. Each step tells you something about what ends up in your summary.

Step in Apple's pipeline What it does What it means for you
Filtering Removes reviews with spam, profanity or fraud Abusive one-liners usually do not make it in. Detailed complaints do.
Insight extraction Splits each review into "atomic" insights, each with one topic and one sentiment A long review that praises sync and complains about the paywall feeds two topics.
Topic modeling Groups insights into topics per app, without a fixed list, and marks topics as "App Experience" or "Out-of-App Experience" Comments about features, performance and design outrank opinions about things outside the app, such as the food in a delivery app's reviews, which Apple deprioritizes.
Topic selection Chooses topics mainly by popularity, with criteria for balance, relevance, helpfulness and freshness, and checks that the selection matches the app's overall rating The most common themes win. A rating mostly in the high fours should not get an all-negative summary.
Generation A fine-tuned model writes the paragraph, refined with human preference data Wording changes between refreshes even when the themes do not.

Apple also describes the evaluation: human raters scored summaries for safety, groundedness, composition and helpfulness. Nothing in the published description says that developer responses are an input. The pipeline starts from user reviews.

Where to find your review summary in App Store Connect

In App Store Connect, open your app, click Ratings and Reviews in the sidebar and choose the iOS platform at the top right. The summary appears under Review Summaries. According to Apple's help page, the Account Holder, Admin, App Manager, Customer Support, Developer and Marketing roles can view this area.

That works for a one-off look. It does not tell you when the text changes, which is what you want to know after a release.

Read your summary with the App Store Connect API

App Store Connect API 4.0 added an endpoint for exactly this. The 4.0 release notes say: "You can now read the customer review summary for your apps by using Read Customer Review Summarizations." Apple's reference describes each result as "An AI-generated summary of customer reviews for an app in a specific App Store territory."

GET https://api.appstoreconnect.apple.com/v1/apps/{id}/customerReviewSummarizations
Parameter Required Values
filter[platform] Yes IOS, MAC_OS, TV_OS, VISION_OS
filter[territory] No Territory IDs such as USA or GBR
include No territory
limit No Up to 200
fields[customerReviewSummarizations] No createdDate, locale, platform, text, territory

The {id} is your app's Apple ID, the number in its App Store URL. Each result carries text, locale, platform and createdDate, plus a relationship to the territory it belongs to.

You need an App Store Connect API key and a signed JWT, the same setup as for reviews. Create a team key under Users and Access > Integrations with the narrowest role that can see ratings and reviews, and see our App Store Connect analytics API guide for the key and token details, including the 401 NOT_AUTHORIZED causes.

A script that saves the summary and reports changes

This Node.js 22 script reads every iOS summary for your app, compares it with the previous run, and prints what changed per storefront. It uses the jose package for the JWT.

// review-summary-watch.mjs: save each App Store review summary and report when it changes.
// Env: ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY (contents of the .p8), ASC_APP_ID
import { readFile, writeFile } from 'node:fs/promises';
import { SignJWT, importPKCS8 } from 'jose';

const HISTORY = './review-summaries.json';
const { ASC_KEY_ID, ASC_ISSUER_ID, ASC_PRIVATE_KEY, ASC_APP_ID } = process.env;

async function token() {
  const key = await importPKCS8(ASC_PRIVATE_KEY, 'ES256');
  return new SignJWT({})
    .setProtectedHeader({ alg: 'ES256', kid: ASC_KEY_ID, typ: 'JWT' })
    .setIssuer(ASC_ISSUER_ID)
    .setIssuedAt()
    .setExpirationTime('15m')
    .setAudience('appstoreconnect-v1')
    .sign(key);
}

export async function fetchSummaries(appId, platform = 'IOS') {
  const url = new URL(`https://api.appstoreconnect.apple.com/v1/apps/${appId}/customerReviewSummarizations`);
  url.searchParams.set('filter[platform]', platform); // required
  url.searchParams.set('include', 'territory');
  url.searchParams.set('limit', '200');
  const res = await fetch(url, { headers: { Authorization: `Bearer ${await token()}` } });
  if (!res.ok) throw new Error(`App Store Connect returned HTTP ${res.status}: ${await res.text()}`);
  const { data } = await res.json();
  return data.map((s) => ({
    territory: s.relationships?.territory?.data?.id ?? 'unknown',
    locale: s.attributes.locale,
    createdDate: s.attributes.createdDate,
    text: s.attributes.text,
  }));
}

export function diffSummaries(previous, current) {
  const before = new Map(previous.map((s) => [s.territory, s]));
  const changes = [];
  for (const s of current) {
    const old = before.get(s.territory);
    if (!old) changes.push({ type: 'new', ...s });
    else if (old.text !== s.text) changes.push({ type: 'changed', before: old.text, ...s });
    before.delete(s.territory);
  }
  for (const gone of before.values()) changes.push({ type: 'removed', ...gone });
  return changes;
}

if (import.meta.url === `file://${process.argv[1]}`) {
  const previous = JSON.parse(await readFile(HISTORY, 'utf8').catch(() => '[]'));
  const current = await fetchSummaries(ASC_APP_ID);
  for (const c of diffSummaries(previous, current)) {
    console.log(`[${c.territory}] summary ${c.type} (${c.createdDate ?? 'n/a'})`);
    if (c.before) console.log(`  before: ${c.before}`);
    console.log(`  now:    ${c.text}`);
  }
  await writeFile(HISTORY, JSON.stringify(current, null, 2));
}

We tested the request building and the diff against a mocked response in Apple's documented shape; run it once by hand against your own account before you schedule it. Run it once a day, and again in the days after a release; App Store Connect webhooks can tell you the moment a version goes live. A summary that appears, disappears or changes its text is worth a message to the team, and our guides to the Slack webhook in Node.js and Node.js cron jobs cover the alert and the schedule. Keep the history file: a dated record of what the summary said is what lets you connect a change in wording to a release.

Why your summary still mentions a bug you fixed

The most common complaint about review summaries is that they describe an older version of the app. The pipeline explains why. Topics are selected mainly by popularity, and the reviews that made a topic popular do not go away when you ship a fix. Most users who left a one-star review about a crash never come back to edit it.

Inventiv, a vendor that sells in-app feedback tools, calls this the "Stale Complaint Loop" in a March 2026 article, and puts it bluntly: "Users almost never update their reviews after a bug is fixed." You do not need to buy anything to act on the point. What moves a topic out of the summary is volume: enough newer reviews about other things that the old complaint is no longer among the most common themes. Apple lists freshness among its selection criteria, which helps, but freshness works on new reviews, and those have to come from somewhere.

Two things do not help as much as teams expect:

  • Resetting the summary rating. Apple lets you reset your star rating per storefront when you release a version, but warns that "resetting your summary rating won't reset your app's written reviews" and that "past reviews will continue to display on the product page." The written reviews that feed the summary stay.
  • Replying to every old review. Replies are good practice and can lead a user to update a review, but Apple's published pipeline is built from user reviews, not developer responses. A reply on its own is not new input to the summary.

How to change what your review summary says

There is no setting that edits the summary, and no honest shortcut. These are the levers that work, in order of impact.

  1. Fix what the summary is about. Read the summary as a list of the two or three most common themes in your recent reviews. If one of them is a real problem, it is your top bug, whatever your crash dashboard says.
  2. Get reviews from people who used the fix. Prompt for ratings after a moment of success, not at launch or after an error. Apple's guide allows prompting "up to three times in a 365-day period," and the system decides whether to show the prompt, so spend those prompts on users who have just used the part you fixed.
  3. Follow the storefronts that have summaries. The US and the eight English-language storefronts listed above are where the summary text matters today. If most of your reviews come from elsewhere, an English summary can lag simply because few reviews arrive in those markets.
  4. Report a summary that is wrong. If the text misstates your app, report it (steps below). Reports are for inaccuracy, not for themes you would rather not see.
  5. Do not try to game it. Apple's App Review Guidelines warn that if you "manipulate reviews, inflate your chart rankings with paid, incentivized, filtered, or fake feedback," Apple may expel you from the Apple Developer Program. Bought praise also tends to be generic, so it does little to dilute a specific complaint anyway.

Read the summary next to your own numbers, especially the share of one-star ratings, which our iOS vs Android app ratings data shows is where most rating differences come from. If the summary says users complain about sync while your one-star share is falling, it may simply be lagging. If your one-star share is rising on the same theme, the summary is early, not wrong. Our guide to reading review and rating trends shows how to read those signals together.

Report a concern about a review summary

Apple's help page gives these steps:

  1. In Apps, select the app.
  2. In the sidebar, click Ratings and Reviews.
  3. At the top right, select the iOS platform.
  4. Click the ellipsis (...) next to the summary under Review Summaries and choose Report a Concern.
  5. Choose a concern from the pop-up menu, describe the problem and click Submit.

Users can also tap and hold the summary on the App Store to report it. Apple does not publish a response time, so keep a copy of the summary text and the date you reported it, which the script above gives you for free.

Watch the reviews that feed the summary

The summary is a lagging view of your written reviews, so the leading indicator is the reviews themselves, per storefront. The customer reviews endpoint accepts filter[territory] and sort=-createdDate, which is enough to check what recent US reviews are about:

// Count how often your watch-list terms appear in the latest 200 US reviews.
const TERMS = ['crash', 'login', 'sync', 'subscription', 'paywall'];

export async function recentThemes(appId, territory = 'USA', authHeader) {
  const url = new URL(`https://api.appstoreconnect.apple.com/v1/apps/${appId}/customerReviews`);
  url.searchParams.set('filter[territory]', territory);
  url.searchParams.set('sort', '-createdDate');
  url.searchParams.set('limit', '200');
  const { data } = await (await fetch(url, { headers: { Authorization: authHeader } })).json();
  const counts = Object.fromEntries(TERMS.map((t) => [t, 0]));
  for (const { attributes: r } of data) {
    const text = `${r.title ?? ''} ${r.body ?? ''}`.toLowerCase();
    for (const t of TERMS) if (text.includes(t)) counts[t] += 1;
  }
  return { reviews: data.length, lowStar: data.filter((r) => r.attributes.rating <= 2).length, counts };
}

A keyword tally is crude, but it is enough to see whether the theme in your summary is still being written about this month. For labels that hold up across languages and phrasing, use a fixed taxonomy and an LLM, as in our guide to app review analysis with an LLM. For alerts on new reviews as they arrive, see App Store review alerts.

Track reviews and ratings across stores

The summary covers one store. If you also ship on Google Play or as a browser extension, the same problem shows up in several review streams at once. Extenify is an app review monitoring dashboard that records your App Store and Google Play ratings, rating counts and reviews every day, next to your Chrome, Edge and Firefox listings, and sends a change alert to email, Slack, Discord, Telegram or Teams when a rating drops or new one-star reviews arrive. Pair it with the summary script above and you see both the cause and the headline. Every plan starts with a free trial; see Extenify pricing.

App Store review summaries checklist

  • Check whether your app has a summary in the US and the other eight English storefronts.
  • Save the summary text daily through customerReviewSummarizations and alert on changes.
  • Treat the themes in the summary as a ranked bug list and confirm them against recent reviews.
  • After fixing a theme, spend rating prompts on users who just used the fixed feature.
  • Report inaccurate summaries in App Store Connect and record the date.
  • Do not expect a summary rating reset to clear old written reviews.
  • Watch one-star share and recent review topics per storefront, not just the average rating.

Frequently asked questions

How often are App Store review summaries updated?

Apple says summaries "are regularly refreshed on an ongoing basis" but does not publish a fixed schedule. Save the text daily with the API and you will see exactly when yours changes.

Why doesn't my app have a review summary?

Summaries need enough reviews to summarize, and Apple currently shows them in the United States and eight more English-language storefronts. A small app, or one whose reviews mostly come from other countries, may not have one yet.

Can I edit or remove my App Store review summary?

No. You cannot edit it. If it is inaccurate, report a concern from Ratings and Reviews > Review Summaries in App Store Connect. Otherwise the text changes as new reviews change the most common themes.

Do my replies to reviews change the summary?

Apple's published pipeline is built from user reviews and does not mention developer responses as an input. A reply can lead a user to update their review, and that updated review can change the summary, but the reply itself is not summarized.

Is there an API for App Store review summaries?

Yes. App Store Connect API 4.0 added GET /v1/apps/{id}/customerReviewSummarizations, which returns the summary text, locale, platform, creation date and territory. filter[platform] is required.

Summary

App Store review summaries turn your written reviews into a two- or three-theme paragraph that many people read instead of the reviews. Apple builds them from the most common topics in user reviews, refreshes them on an ongoing basis, and shows them in nine English-language storefronts. You can read yours in App Store Connect or through the customerReviewSummarizations endpoint, and a daily copy lets you see when it changes. The summary changes when your reviews change: fix the themes it names, earn reviews from users who saw the fix, report text that is wrong, and watch the review stream that feeds it.

Image credits

Put every store in one dashboard tonight.

Sign in with Google, paste one store link, and your unified view is live in under a minute. Then 7 days of Pro free, no credit card required, and you never touch your app's code.

Start free trial