Author Archives:

Announcing v24 of the Google Ads API

Today, we’re announcing the v24 release of the Google Ads API. To use the new v24 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 (April 23rd 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

Support for Conversions with Cart Data: Conversions with cart data is an extension to conversion tracking on your website or app. Using conversions with cart data, you can provide the details of products sold for each transaction, which helps you unlock advanced sales, profit reporting, and insights for your Google Ads account and campaigns, such as number of orders, average cart size, revenue and gross profit.

Google Ads API v24 adds support for this feature as follows:

  • Added a new resource CartDataSalesView that allows segmenting conversion metrics not only by the product clicked, but also by the product sold, with segments like product_sold_brand. These enable advertisers to view statistics on the products the customers actually bought after clicking ads, even if the ad was for a different product.
  • Added several “all” non-biddable metrics, which are metrics that also include the conversions your campaigns are not actively optimizing towards, for example all_cost_of_goods_sold_micros. The new metrics are added to all resources supporting corresponding biddable metrics.
  • Added the conversion_attribution_event_type segment to the ShoppingPerformanceView resource, making it selectable with cart data and other conversion metrics. This segment denotes whether the conversion is attributed to a click or to a view and it is necessary to recognize cart data stats produced by view-through conversions.

Updated features

Version v24 introduces updates to existing features that require code changes when upgrading. We cover the most important ones here; check out the release notes for the full list of changes.

Video content exclusion settings in campaigns: We simplified the ability to set video content exclusion settings on individual campaigns. This setting is available at the customer level, and applies to all the campaigns instead. These content exclusion settings are meant to give you additional control and help you exclude types of content that, while in compliance with our policies, may not fit your brand or business. See https://support.google.com/google-ads/answer/7515513 to learn more about video content exclusion settings.

Changes to AudienceInsightsService: As part of a code refactoring, we moved the InsightsAudience.topic_audience_combinations request field into the common namespace. You may need to update your import directives in some programming languages.

Changes to ReachPlanService: As part of a code refactoring, we moved the youtube_select_lineups field from the ReachPlanService.ListPlannableProducts service. Lineups are now available within the youtube_select_lineup_targeting field. YouTube Select Lineups are reservation products for eligible clients to target among the top 1% of popular channels on YouTube with the most passionate audiences in a given market. Learn more.

Changes to ContentCreatorInsightsService: As part of a code refactoring, we removed the is_brand_connect_creator field from the ContentCreatorInsightsService.GenerateCreatorInsights and ContentCreatorInsightsService.GenerateTrendingInsights services.
Users should instead look for a creator to have the CREATOR_PARTNERSHIPS option available instead in partnership_opportunities. The YouTube Creator Partnerships in Google Ads is the space where you can find YouTube creators to partner with on sponsored content and help you efficiently manage your creator partnerships. Learn more.

Changes to KeywordPlanIdeaService: To provide a more streamlined and reliable experience, we have unified our forecasting infrastructure. Google Ads API v24 introduces an updated GenerateKeywordForecastMetrics method that simplifies the planning process by focusing on the metrics that most directly impact your performance. We will share a more detailed blog post about this change in the coming days.

Changes to campaign_budget resource: We removed the ad_sub_network_type segment for the campaign_budget resource because it is incompatible with this view.

Changes to asset views: We removed the click_type segment from the ad_group_asset, campaign_asset, and customer_asset views. This change aligns with a recent product change that removed this segment from the Google Ads to avoid misrepresentation of data. You can use the click_type segmentation from the ad_group_ad resource to get details on the ad performance and the asset it was served with.

Changes to video responsive ad: VideoResponsiveAdInfo is now mutable. As part of this change, we have marked videos, business_name and logo_images as required fields in both the DemandGenVideoResponsiveAdInfo and VideoResponsiveAdInfo objects.

Changes to ShareablePreviewService: Updated ShareablePreviewService.GenerateShareablePreviews to not use partial failure anymore. Requests will throw an error if they fail for any ID. Learn more.

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

 - , Google Ads API Team

Streamline User Journeys with Verified Email via Credential Manager

Posted by Niharika Arora, Senior Developer Relations Engineer and Jean-Pierre Pralle, Product Manager, Credential Manager



In the modern digital landscape, the first encounter a user has with an app is often the most critical. Yet, for decades, this initial interaction has been hindered by the friction of traditional verification methods. Today, we're excited to announce a new verified email credential issued by Google, which developers can now retrieve directly from Android’s Credential Manager Digital Credential API.

The Problem: Authentication Friction in the Modern Era

The "current era" of authentication is defined by a trade-off between security and convenience. To ensure that a user owns the email address they provide, you typically rely on One-Time Passwords (OTPs) or "magic links" sent by email or SMS.

While effective, these traditional steps introduce significant hurdles:

  • Context switching: Users must leave the app, open their inbox or messaging app, find the code, and return, a process where many potential users simply drop off.
  • Delivery issues: While Emails are free, they can be delayed or diverted to spam folders.
  • Onboarding friction: Every extra second spent in the "verification loop" is a second where a user might lose interest, directly impacting conversion rates.

The Solution: Seamless, Verified Email

Google now issues a cryptographically verified email credential directly to Android devices. This verified email credential is delivered through the Credential Manager API, which is Android's implementation of the W3C's Digital Credential API standard.

For users, this completely removes the need to manually verify their email through external channels. For developers, the API securely delivers these verified user claims for any scenario whether you are building an account creation flow, a recovery process, or a high-risk step-up authentication.

While this specific verified email address is sourced securely from the user's Google Account on their device, the underlying Digital Credentials API is issuer-agnostic. This fosters an open ecosystem, allowing any holder of a digital credential with an email claim to offer that verification to your app.

User Experience

The beauty of this API lies in its simplicity for the end user. Instead of hunting for OTP codes, the experience is integrated directly into the Android OS:

  • Initiation: The process begins when a user focuses on an email input field or taps a "Sign up" or "Recover account" button. You can also initiate the process on page load.
  • Transparency: A native Android bottom sheet appears, clearly detailing exactly what data is being requested (for example, user’s verified email address).
  • One-tap consent: The user simply taps "Agree and continue" to share the data.
  • Immediate progress: Once consent is given, the app receives the data instantly. For sign-up or account recovery flows, you can then seamlessly transition the user into passkey creation, ensuring:
    • Users do not have to enter any user information manually, as compared to the traditional username/password registration.
    • Their next login is even faster and more secure.

Use case 1. Sign up

Accelerate onboarding by fetching a verified email the moment the user taps "Sign up". We strongly recommend you pair the verified email retrieval with passkey creation, also part of the Credential Manager API:



Note: You can also fetch other unverified fields such as a user’s given name, family name, name, profile picture and the hosted domain connected with the verified email.

Use case 2. Account recovery

Eliminate the frustration of users hunting for recovery codes in their spam folders by allowing them to recover their account using the verified email securely stored on their device.



Use case 3. Re-authentication for sensitive actions

Protect sensitive user actions, such as changing settings or updating profile details, by requiring a quick re-authentication step. Instead of an OTP, you can provide a low-friction verification using the device's verified email.



Important Considerations

As you design your authentication architecture around the Digital Credentials API, keep the following details in mind:

  • Account support: For the specific email credential issued by Google, only regular consumer Google Accounts are supported (Workspace and supervised accounts are currently not supported). Keep in mind that the Credential Manager API itself is issuer-agnostic, meaning other identity providers can issue credentials with their own account support policies.
  • Other user data: Beyond email, you can request the user's given name, family name, full name, and profile picture. However, note that only the email is verified by Google.
  • Auto verify your @gmail accounts: The API provides verified emails for all consumer Google Accounts. We recommend auto-verifying @gmail.com users and routing custom domains to your existing verification flow - for example, an OTP flow. This ensures you maintain long-term access for external domains not directly managed by Google.
  • Complementary to Sign in with Google: While both the new verified email credential & Sign in with Google API provides a verified email, the choice depends on the intended user experience:
    • Use Sign in with Google when your users want to create a federated login session.
    • Use Verified Email when your users want to sign in traditionally with a username/password or passkey but want to auto-verify the email address without the manual chore of an OTP.

Conclusion and Next steps

By integrating the new verified email via Credential Manager API, you can drastically reduce onboarding friction and provide users with a more streamlined, secure authentication journey. This represents a shift toward a future where "verification" is no longer a manual chore for the user, but a seamless, integrated part of the native mobile experience.

Ready to see how this fits into your own app? To get started, update your project to the latest Credential Manager API and explore our Integration Guide. We encourage you to explore how this streamlined verification can simplify your critical user journeys from optimizing account creation, to enhancing re-authentication flows.

Chrome for Android Update

 Hello Everyone! We've just released Chrome 148 (148.0.7778.49) for Android to a small percentage of users. It'll become available on Google Play over the next few days. You can find more details about early Stable releases here.

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Krishna Govind
Google Chrome

Chrome for Android Update

    Hi, everyone! We've just released Chrome 147 (147.0.7727.111) for Android. It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.


Android releases contain the same security fixes as their corresponding Desktop releases (Windows & Mac: 147.0.7727.116/.1117, Linux:  147.0.7727.116) unless otherwise noted.

Krishna Govind

Stable Channel Update for Desktop

The Stable channel has been updated to 147.0.7727.116/117 for Windows/Mac  and 147.0.7727.116 for Linux, which will roll out over the coming days/weeks. A full list of changes in this build is available in the Log

Security updates will be updated here shortly. 


Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Srinivas Sista

Google Chrome

Extended Stable Updates for Desktop

 The Extended Stable channel has been updated to 146.0.7680.208 for Windows and Mac which will roll out over the coming days/weeks.


A full list of changes in this build is available in the log. Interested in switching release channels? Find out how here. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Srinivas Sista
Google Chrome