What is included in Apple App Store review data?

The exact schema depends on the collection. These are the commonly available fields to validate in your sample.

review_id
app_id
app_name
rating
review_title
review_text
review_date
app_version
storefront
reviewer_display_name
language
source_url

Example normalized record

This anonymized, illustrative record shows the expected shape. Confirm actual fields and values using the sample for your selected collection.

{
  "review_id": "IOS_19B72",
  "app_id": "123456789",
  "app_name": "Example App",
  "rating": 5,
  "review_title": "Simple and reliable",
  "review_text": "The new version fixed the issue I had.",
  "review_date": "2026-08-19",
  "app_version": "6.2.0",
  "storefront": "US",
  "language": "en"
}

Common use cases

Sentiment analysis

Classify review sentiment and compare rating-to-text agreement.

Topic and aspect extraction

Identify recurring product, service, feature, or support themes.

Competitive intelligence

Compare ratings, review volume, response patterns, and customer concerns.

AI evaluation and training

Develop retrieval, summarization, classification, and language-analysis workflows.

Trend monitoring

Measure how feedback changes by version, business, market, or time period.

Collection and quality considerations

Before purchasing or training a model, verify the collection date, geographic and language coverage, rating distribution, duplicate rate, missing fields, deleted-content policy, and source-specific limitations.

A current snapshot is suitable for present-state analysis. Measuring changes over time requires dated recurring snapshots collected with a consistent method.

Request a targeted extract

Scope the collection by app, business, country, language, rating, or date range when those filters are exposed by Apple App Store. We can also discuss recurring delivery and a normalized schema.

Discuss your review data requirements

iOS App Store Reviews Dataset FAQ

Common fields include review id, app id, app name, rating, review title, review text, review date, app version. Exact fields and completeness depend on the selected collection and are documented in its sample.

Yes. Where available, reviews can be collected from selected Apple App Store storefronts and filtered by app, rating, language, date, or app version.

Yes. You can review representative fields and request sample records for the apps, businesses, markets, languages, or date range relevant to your project.

The rating and text fields can support sentiment classification, topic extraction, summarization, retrieval, and model evaluation, subject to the applicable dataset license.

Yes. Availability depends on the source and scope. Ask for a dated historical snapshot or a recurring collection schedule when requesting access.

Review datasets are commonly delivered in CSV or JSON. Confirm the format, encoding, record count, and delivery method for the selected collection.

Yes, when those fields are available from the source. Custom extracts can be scoped by rating, date range, language, country, app, or business.

Public samples should omit or anonymize unnecessary reviewer identifiers. Review the exact retained fields, privacy treatment, and license before using the full dataset.

Explore more customer review datasets

Compare mobile app, business, product, and hotel review collections from the main reviews hub.