Today, we’re announcing the v24.1 release of the Google Ads API. To use the new v24.1 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.
Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord, our Ads Developers YouTube Live, or our LinkedIn Live event tomorrow (May 14 at 10a ET). This will also be recorded and posted on YouTube for those who can’t make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.
New Features
Mobile Device Platform Segment: Understanding where your traffic comes from is critical for campaign optimization. With v24.1, you can now segment campaign-level and customer-level reports using the segments.mobile_device_platform column.
This field utilizes the new MobileDevicePlatform enum (supporting values like IOS and ANDROID), allowing you to cleanly isolate performance data and adjust bid strategies based on the user's mobile operating system.
Classic images in DemandGen campaigns: As of v24.1, you can use the classic_display_images field of DemandGenMultiAssetAd to upload static image ads to serve on the Google Display Network (GDN) within your Demand Gen campaigns. These images are served as-is, without being combined with additional assets. This format provides full control over your creative branding. Refer to our help center for more information.
Support for passkeys: Passkeys provide a simple and secure alternative to passwords. Google now requires some advertisers to use a passkey to authorize sensitive actions within their Google Ads account. The v24.1 introduces a new passkey_enabled field that indicates whether the user has a passkey enabled.
Revamped support for Experiments: Experiments let you test the impact of your proposed changes. If you split the budget or traffic between the original campaign and experiment, you can easily compare the results over a specified time period. If the experiments produce better results, you can apply the experiment to the original campaign or replace the original campaign.
The v24.1 introduces support for new experiment types: AI Max experiments, Video experiments, Demand Gen experiments (this and video are the same API type) and Performance Max experiments. You can now retrieve and compare detailed performance metrics (such as clicks, conversions, and impressions) across individual experimental arms. This makes side-by-side performance analysis easier and more transparent. Refer to our guide to learn more about experiment workflows.
New Data Retention Policy for Google Ads: We recently announced that starting June 1, 2026, Google Ads and related measurement APIs will transition to a 37-month data retention policy for granular performance statistics (daily, hourly, and weekly). The V24.1 introduces a new DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED error code to support this change.
The following resources can help you get started:
For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api
