With the release of a new major Google Mobile Ads SDK version, earlier major versions may be given a sunset date. After an SDK version is sunset, ad traffic from that version is at risk of receiving automatic no fill due to stopped ad serving.
- Benefits of a deprecation schedule
Introducing a predictable deprecation schedule offers the following benefits:
- Ability to predict and plan for SDK updates with a year of lead time.
- Legacy SDK code that only exists to support old versions can be deleted, thereby decreasing SDK size and lowering the risk of bugs.
- Engineering resources can focus more on support for newer SDKs and innovation of new SDK features.
The following table lists the specific deprecation and sunset dates for each version. We encourage you to migrate to the newest version as soon as possible after its release.
|Versions||Release date||Deprecation date||Sunset date||Migration guide|
|v22.x.x||March 29, 2023||Q1 2025||Q2 2026|
|v21.x.x||May 25, 2022||Q1 2024||Q2 2025||Migrate to v22|
|v20.x.x||April 5, 2021||March 29, 2023||Q2 2024 1||Migrate to v21|
|v7.x.x - v19.x.x||March 19, 2015||September 30, 2022||June 30, 2023||Migrate to v20|
1 A more specific sunset date will be announced on the Google Ads Developer blog, and updated on this page with two months notice.
Differences between supported, deprecation, and sunset
|SDK Versions||All releases with major release N and N-1, where N is the latest major version.||All releases with major release N-2.||All releases with major release N-3 or below. Releases with major version N-3 will sunset approximately two months after major version N is released.|
|Ad serving||Ads serve to this version.||Ads serve to this version.||Ads at risk of not serving to this version. We will regularly review usage of all sunset versions going forward to consider disabling ad serving. The oldest versions with lower usage and higher maintenance costs will be targeted first. When ad serving is disabled, ad requests return a no fill with an error indicating that this version is sunset.|
|Support||Technical SDK support questions are welcomed on the Google Mobile Ads SDK developer forum.||Technical SDK support questions specific to this version are no longer supported on the Google Mobile Ads SDK developer forum. You will be asked to validate the issue in a supported version to receive full support.||Technical SDK support questions specific to this version are no longer supported on the Google Mobile Ads SDK developer forum. You will be asked to validate the issue in a supported version to receive full support.|
Lifecycle of a major SDK version
In general, a new major version will live in the supported state for about two years, and in a deprecation state for an additional year before moving to a sunset state.
The deprecation and sunset timelines for the Google Mobile Ads SDK revolve around major SDK releases. We plan to have one major version release in the first quarter of each year. The release of a new major version triggers changes in support for earlier major versions.
When a new major version N is released:
- All SDK versions with major version N-2 are considered deprecated immediately.
- All SDKs versions with major version N-3 will sunset after approximately two months.
This deprecation schedule provides a framework for predictable lifetimes for an SDK version. However, there may be exceptions in the future. This schedule does not preclude us from sunsetting an SDK version at an earlier date, but we are committed to providing proactive communication with ample lead time for any future changes.