Google Play’s 2026 target API rule has two different gates
Analysis
By UA Ledger staff — 2 min read

Submission eligibility and existing-app discoverability require separate checks.
Google Play’s 2026 requirement should produce two launch checks. One concerns whether a new submission is accepted; the other concerns whether an existing game remains available to certain new users. Treating both as a single “Android compliance” task hides the decision the media buyer needs.
Separate release and discovery
For a planned update, ask the release owner which target API is declared in the candidate. For an unchanged live game, inspect the published version and test availability for the audience being bought. The requirement concerns target API, which should not be confused with the minimum OS version your game supports.
Our recommendation is to put the device category on the record. Google lists exceptions for other Android device classes; a phone-game checklist should not be copied unchanged into a television or wearable launch. This edition confines its extracted rule to standard phone and tablet apps.
Record extensions as account facts
Google’s page describes an extension route to 1 November 2026. That does not prove any particular app received an extension. Preserve the actual account decision if one is being used to justify continued distribution or a delayed update.
For growth planning, an unavailable destination can resemble weak conversion until someone checks the store path. Establish eligibility and discoverability before using such a result to judge a new creative. The table records the public rule; the missing evidence is the state of the particular game and the devices targeted by its campaign.
The governing record is Target API level requirements for Google Play apps. This edition checks the provider documentation; it does not inspect a studio account or certify a shipped build.
Inspect the evidence
Download the applicability and deadline record. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Provider | |
| Effective or release date | 2026-08-31 |
| Applies to | Standard Android phone and tablet apps; other device classes have separate rules |
| Documented change | From 31 August 2026, standard new apps and updates require API 36; existing apps need API 35 for the described new-user availability rule. |
| Suggested owner | Android release engineering and store operations |
| Next verification | Check the production target API, intended device class and any granted extension. |
Further reading in the existing archive: Google Play's Developer Verification Push: A Checklist; Android Alternative App Stores and Attribution Setup. These links provide background; this check does not independently verify their full contents.
Featured
Related posts
measurement
platforms
·1 min read
When to turn rewarded ads off for payers (and how to measure the loss)
measurement
platforms
·1 min read
When custom product pages need their own MMP campaign mapping
measurement
platforms
·1 min read
Season pass refund rate versus standard IAP refund rate
measurement
platforms
·1 min read
Pre-reg cohort quality vs post-launch paid cohort quality
More from the Measurement desk
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
measurement
platforms
·1 min read
Pity-adjusted expected value versus player-facing banner claims
measurement
platforms
·1 min read