Apple has added a new question to the App Store Connect age rating questionnaire: does the app let users redistribute, amplify, or interact with user-generated content through a social feed or similar discovery mechanism. From September 2026, answering it becomes mandatory for every new app submission and every update, including apps submitted for notarised distribution outside the App Store. Answer yes, and the app is placed in the Social Media time-allowance category, receives a minimum 13+ age rating, and gets a new “Social Media” content descriptor shown on its product page.
The immediate risk isn’t the questionnaire itself — it’s teams treating it as a one-off compliance checkbox rather than an acquisition and discoverability variable. A 13+ minimum rating changes who the App Store can legally and structurally surface an app to, interacts with parental Screen Time and Time Allowance controls in iOS 27, and adds a visible descriptor that can change a user’s decision to install before they ever open the app. Any app with in-app content sharing, comment feeds, or user-to-user interaction features — even ones that were never designed with “social media” as their core purpose — needs to check where this new flag lands and whether the answer they give matches how their features actually behave, not just how the team originally pitched the product.
Data Points to Track
- Age rating and content descriptor state per app version, logged at each submission, to catch when a feature addition silently crosses into “social media capability” territory
- Install volume segmented by rating tier, before and after any 13+ reclassification, to isolate the rating change’s effect from normal acquisition variance
- Time Allowance category assignment, since Social Media sits in its own bucket separate from Entertainment or Games and interacts differently with parental controls
- Product page bounce or exit rate, watching for a shift once the Social Media descriptor becomes visible to prospective users
- App Store search ranking and category placement, tracked before and after reclassification, in case the new descriptor affects how the app surfaces in browse and search
Setup Steps
- Audit every feature that redistributes, amplifies, or surfaces user-generated content — comment sections, activity feeds, resharing, public profiles — against Apple’s social media capability definition before the next submission.
- Answer the questionnaire based on actual current functionality, not the app’s original positioning, and re-answer it at every version submission where relevant features change.
- Baseline install volume and product page conversion in the weeks before submitting an update that changes the rating, so any shift has a clean before/after comparison.
- Monitor App Store Connect’s rating and descriptor fields after each submission to confirm the declared answer produced the expected outcome.
- Cross-check search ranking and category placement post-reclassification, since a rating change is a plausible confound for any ranking movement in the following weeks.
Actionable Insights
A 13+ reclassification is not automatically bad news for acquisition — for apps whose real audience already skews teen and adult, the descriptor mostly formalises what discovery patterns already showed. The data question worth answering is whether the drop, if any, concentrates in a specific segment (younger users, a specific territory, a specific acquisition channel) or spreads evenly, because that distinguishes a genuine access change from noise. Apps sitting close to the capability boundary — light social features bolted onto a non-social core product — are the ones worth the most scrutiny, since a borderline “yes” answer carries a real rating cost for a feature that may not be central to retention or revenue.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert