Introducing improved diagnostics for enhanced conversions for leads imports

Today in the Google Ads UI, you will see updated enhanced conversions for leads diagnostics that feature a number of improvements that offer better visibility into the state of your conversion import implementation. The goal of these changes is to help you identify common problems and address them quickly.

Here are some of the changes you’ll see:

  1. New "Importing limited user-provided data" Alert: A new, high-priority alert has been introduced to detect a common implementation error, where users fail to import incremental conversions that contain user-provided data (UPD) but not a GCLID. We recommend that you import all of your conversion data that has user-provided data, regardless of whether or not it has a GCLID. Doing so helps to find cross-device or Youtube EVC conversion touchpoints, driving performance uplift. You may not see these benefits if you omit UPD-only conversions.
  2. Improved Status for "Tagless" Implementations: A new "Good" status has been added to validate setups where advertisers import conversions with both a GCLID and user-provided data, but do not have the Google tag implemented on their website. Previously, this valid configuration could trigger confusing "Urgent" alerts. If you have not implemented the Google tag on your website, it’s important to include GCLIDs in your conversion imports whenever possible in order to get performance benefits.
  3. Reprioritized Alert Logic: Alert priorities have been updated to be more intelligent. For users sending GCLIDs with their offline data, import-related issues will be prioritized as more critical, while tag-related issues will be downgraded in severity.
  4. Complete Alert Visibility: The diagnostics interface has been updated to show all alerts at once, regardless of their severity tier. This allows developers to see a complete picture of all required and recommended actions upfront, rather than fixing one issue only to uncover another.
  5. Deprecation of CLICK_NOT_FOUND: The informational CLICK_NOT_FOUND error has been removed from the Diagnostics UI and API, and, correspondingly, the debug_mode parameter in the UploadClickConversions method that triggers it in API responses has also been removed. See this related blog post for reference.

Reach out to the Google Ads API support channel if you have any questions or need support. If you want to discuss this change with us, join our “Google Advertising and Measurement Community” Discord server.

Search Central Live Dubai 2025

For the first time, Search Central Live is coming to Dubai on October 21, 2025! After events in Europe, Latin America, and Asia, we're continuing our mission to help you enhance your site's performance in Google Search, live in Dubai, UAE.

Stable Channel Update for Desktop

The Stable channel has been updated to 140.0.7339.207/.208 for Windows/Mac, and 140.0.7339.207 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 Fixes and Rewards


Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

This update includes 3 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.


[TBD][430336833] High CVE-2025-10890: Side-channel information leakage in V8. Reported by Mate Marjanović (SharpEdged) on 2025-07-09

[N/A][443765373] High CVE-2025-10891: Integer overflow in V8. Reported by Google Big Sleep on 2025-09-09

[N/A][444048019] High CVE-2025-10892: Integer overflow in V8. Reported by Google Big Sleep on 2025-09-10

We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

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

Refine Google Chat messages with Gemini to communicate with confidence and clarity

What’s changing 

You can now use Gemini to refine messages you’re composing within Google Chat on the web. Gemini can help you improve clarity, conciseness, and accuracy in wording, grammar, and spelling. This can be particularly useful when composing an important message to a large space or a senior stakeholder, or for users communicating in a second language. 

By using the feature, users can press send with more confidence and communicate with greater clarity. 


Getting started 

  • Admins: This feature will be on by default for eligible users. Use our Help Center to learn how to manage access to Gemini features in Workspace services. 
  • End users: This feature will be available by default for eligible users. You can either select ‘Refine’ from the formatting toolbar, or highlight the text you want to refine and select ‘Refine’ from the floating toolbar. Visit the Help Center to learn how to manage Refine in Google Chat. 

Rollout pace 


Availability 

Available for Google Workspace: 

  • Business Standard and Plus 
  • Enterprise Standard and Plus 
  • Google AI Pro for Education
  • Google AI Ultra for Business 
  • Frontline Plus

Also available to: 
  • Google AI Pro and Ultra 

Anyone who previously purchased these add-ons will also receive this feature: 
  • Gemini Business* 
  •  Gemini Enterprise* 
*As of January 15, 2025, we’re no longer offering the Gemini Business and Gemini Enterprise add-ons for sale. Please refer to this announcement for more details. 

Resources 

Beta Channel Update for ChromeOS / ChromeOS Flex

The ChromeOS Beta channel is being updated to OS version 16404.23.0 (Browser version 141.0.7390.35) for most ChromeOS devices.

If you find new issues, please let us know one of the following ways:
  1. File a bug
  2. Visit our ChromeOS communities

    1. General: Chromebook Help Community

    2. Beta Specific: ChromeOS Beta Help Community

  3. Report an issue or send feedback on Chrome

  4. Interested in switching channels? Find out how.

Alon Bajayo

Google ChromeOS Release