New AdMob preloading APIs did not establish universal access

The current reference still carries a limited-alpha boundary.
AdMob added new preloading interfaces in June 2025 while retaining a limited-alpha label. The current package reference still carries that label. The supported outcome is continued documented limitation, not a failed launch. Release notes; Package reference.
API visibility is not account availability
A public method can exist in a client library without being generally usable by every publisher. Our recommendation is to record both the SDK capability and the account’s access state when planning a feature-dependent release. Neither should be inferred from the other.
This check did not inspect a publisher account or a private access agreement. It also did not run a preloading experiment. The evidence therefore supports a narrower statement than “preloading is available to all” or “preloading never launched”.
Plan a fallback around the player journey
If a team proposes to depend on this feature, ask what happens when it cannot be used. The fallback should preserve a clear user experience rather than leave the game waiting indefinitely for an ad. Define the expected behaviour before using the feature as a solution to a monetisation or retention problem.
The timeline preserves the original limited scope and the later reference state. A useful next update would be an explicit provider change in availability or a documented account-level test with its scope stated. Until then, the feature belongs in a conditional implementation plan, with performance benefits left as hypotheses rather than reported results.
Inspect the evidence
Download the announcement-to-outcome evidence timeline. The extraction separates documented facts from our analysis and unknowns.
| Field | Evidence or limit |
|---|---|
| Earlier record | 2025-06-09 — The release added preloading APIs while describing the feature as limited alpha. |
| Later evidence | 2026-02-17 — The package reference still labels preloading limited alpha. |
| Outcome supported | General availability is not established by these inspected documents |
| Still unconfirmed | Account eligibility and any newer private access arrangement were not inspected. |
| Next check | Recheck the feature status and confirm account access before committing a release |
Further reading in the existing archive: Rewarded Video's Retention Mandate, Beyond the Install; The MMP Migration Checklist to Run Before You Switch. These links provide background; this check does not independently verify their full contents.
Frequently asked questions
What happened next, and what should UA change after: New AdMob preloading APIs did not establish universal access?
Keep the supported outcome as continued documented limitation, not a failed launch and not general availability. AdMob added new preloading interfaces on 9 June 2025 while describing the feature as limited alpha; the package reference still carried that limited-alpha label as of 17 February 2026. API visibility is not account availability — a public method can exist in a client library without being generally usable by every publisher. Record both the SDK capability and the account’s access state when planning a feature-dependent release; infer neither from the other. If a team proposes to depend on preloading, define a fallback that preserves a clear player experience rather than waiting indefinitely for an ad, and define expected behaviour before using the feature as a monetisation or retention solution. Performance benefits stay hypotheses until an explicit provider availability change or a documented account-level test with stated scope. This check did not inspect a publisher account or run a preloading experiment.
Related posts

market intelligence
media buying
·1 min read
Lunar New Year UA gates from an official calendar, not a CPI myth

market intelligence
media buying
·2 min read
WeChat Mini Games upgrades 2026 IAP / virtual-payment incentives for debut titles

market intelligence
media buying
·2 min read