
Unlock next-level performance with AI Max for Search campaigns

We previously announced our 2025 Google Ads API release plans. We are introducing a few changes to this schedule as a part of our ongoing efforts to evolve our release process. The new schedule lets us make various product features available earlier in the Google Ads API. As usual, additional details on new features will follow as part of the release notes for individual versions.
Here’s our updated schedule.
Version | Planned Release
Type |
Projected launch | Projected sunset |
---|---|---|---|
V20 | Major | June/July 2025 | June 2026 |
V21 | Major | August/September 2025 | August 2026 |
v19_2 | Minor | August/September 2025 | February 2026 |
v20_1 | Minor | August/September 2025 | June 2026 |
V22 | Major | October/November 2025 | October 2026 |
Please take a look at your future plans to make sure they still align with the upcoming Google Ads API release schedule.
If you have any questions or need help, check out the Google Ads API support page for options.
Starting today, Workspace admins can pre-configure the new Gemini conversation history admin settings before they take effect for their Gemini app users (expected by the end of May 2025). By default, “Gemini conversation history” will be ON and ”Conversation retention” will be set to 18 months (inline with current behavior).
Admins and end users
The Dev channel is being updated to OS version 16261.0.0 (Browser version 137.0.7137.0) for most ChromeOS devices.
Visit our ChromeOS communities
General: Chromebook Help Community
Beta Specific: ChromeOS Beta Help Community
Interested in switching channels? Find out how.
Luis Menezes
Google ChromeOS
IMA Android version 3.35.1 adds the ImaSdkFactory.initialize()
method. This call begins loading necessary SDK resources before the first ad request, leading to faster load times. These changes can limit ad buffering, and help maximize ad impressions and monetization. Depending on the device, the loading process can take several seconds to complete.
We strongly recommend making the initialize()
call as soon as possible after the app starts. This approach shortens the time to first frame for pre-roll ads, thus limiting the time users are waiting and increasing monetization potential.
For applications that implement these load time improvements, the following benefits show:
The following diagram shows an app using the initialize()
method call to load system resources before a user selects a video:
The ImaSdkFactory.initialize()
call accepts an ImaSdkSettings
instance. Use the same settings values that are used to create any AdsLoader
instances in the app. For client-side and DAI for more information, see optimize IMA load time . If you have any questions, feel free to reach out using the IMA technical forum.