Stable Channel Update for ChromeOS / ChromeOS Flex

The ChromeOS Stable channel is being updated to OS version 16667.55.0 (Browser version 149.0.7827.226) 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.

Luis Menezes

Google ChromeOS

Google Workspace Weekly Recap – June 26, 2026

Troubleshoot formula errors quickly with Gemini in Google Sheets

We’re excited to introduce a new Gemini in Sheets capability that enables you to diagnose and fix formula errors in one click. When you encounter a formula error, Gemini can analyze the surrounding data structure to help provide an easy-to-understand explanation of the core issue alongside a corrected version of the formula. | Learn more.

Enhanced security monitoring with expanded Admin password reset alerts

In Alert Center, we are expanding the existing “Super Admin password reset” alert into a broader Admin password reset alert. With this update, the alert will now cover password resets for all administrator roles within your organization. | Learn more.

Join Google Meet calls from Safari on iOS devices

Prior to this update, iOS users without the Gmail or Meet apps were unable to participate in Google Meet sessions on their mobile devices. Now, iOS mobile device users can join meetings directly through Safari, without needing to install an app. | Learn more.

Google Apps Script is now a Google Workspace core service with enterprise-grade data protection

Google Apps Script is officially a Google Workspace core service. Covered under the Google Cloud Terms of Service and Google Workspace for Education Terms of Service, Apps Script now offers the same enterprise-grade data protection, robust administrative controls, and standard technical support that safeguards other core services. | Learn more.

Connect to Google Meet hardware with room codes now in Early Preview

Google Meet users can now connect to nearby conference room hardware by entering a 5-character room code on their personal device. Meet recently launched Connect Room using proximity-based detection to identify nearby hardware. | Learn more.

Updates to Gemini in Google Classroom

We are introducing several updates to the Gemini tab in Google Classroom designed to make its tools even more helpful for teachers. These changes make it easier for educators to collaborate with AI and create visual aids from any device, while expanding options for refining lesson plans. | Learn more.

Stricter classifications for Google Groups to enhance data security and privacy

Earlier this year, we announced changes to Google Groups to enhance data security and privacy. The changes, which are rolling out now. | Learn more.

Read Along in Google Classroom is now available to all education users to support foundational literacy

Read Along in Google Classroom, an AI-powered literacy tool that provides in-the-moment support to students as they read aloud, is now available to all Google Workspace for Education users at no cost. | Learn more.

Streamline your data backups with incremental exports for Google Workspace

Google Workspace administrators can now utilize incremental exports when backing up organizational data. Instead of re-exporting their entire organization's data, admins can export frequent snapshots of their data into their organization’s own Google Cloud Storage (GCS) bucket. | Learn more.

The announcements above were published on the Workspace Updates blog over the last week. Please refer to the original blog posts for complete details.

July 2026 changes for Display & Video 360 API and Structured Data Files

Today we’re announcing two unversioned changes to the Display & Video 360 API and Structured Data Files that will take effect on July 13, 2026 and may impact your existing integrations.

The following changes have been fully detailed on our Announced Deprecations page:

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

- Trevor Mulchay, Display & Video 360 API Team

Unlocking Data Strength with Data Manager API: Ads DevCast E7

We are thrilled to share the newest episode of Ads DevCast, the podcast series brought to you by Google’s Ads Developer Relations team.

This episode features a conversation with Data Manager PMs Xuezhu Li and Stephen Chang on unlocking data strength using the Data Manager API.

Watch it: goo.gle/watchadsdevcast

Hear it: goo.gle/listenadsdevcast

Streamlining Ingestion: Send Once, Fan Out Everywhere

Ingesting first-party signals into disparate advertising and measurement platforms has historically required building and maintaining separate, asynchronous ingestion pipelines. In this episode, Xuezhu explains how the Data Manager API introduces a "send once, fan out everywhere" architecture. You push your first-party data in one time, and the system seamlessly routes and distributes it across whichever destinations you choose, such as: CM360, DV360, SA360, and GA4.

Effortless Pipeline Monitoring with the Status API

For developers managing high-volume ingestion pipelines, tracking execution health is critical. The episode explores the new Status API — a dedicated request-tracking service that lets you monitor pipeline health using a simple request ID. Instead of digging through legacy multi-step offline queries, you get unified status checks with aggregated row-level error reporting.

Built-In Privacy & Confidential Compute

The Data Manager API is built from the ground up to keep sensitive user signals secure. That’s why it provides Confidential Match. Confidential Match relies on Confidential Compute, utilizing hardware-isolated Trusted Execution Environments (TEEs) to ensure your data remains completely locked down even during active processing.

Four Reasons to Adopt & Engineering Best Practices

Stephen and Xuezhu break down the four core reasons to adopt the Data Manager API today:

  1. Performance
  2. Privacy
  3. New Features
  4. Developer Experience

We Want to Hear From You

Your feedback is vital to help us tailor future episodes. Please take a minute to share your thoughts at our Episode Survey. Be sure to subscribe on YouTube and join our Discord community to keep the conversation going!

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Developers Community” Discord server. Also follow our new Google Advertising and Measurement Developers” LinkedIn page.

Cory Liseno
Google’s Advertising and Measurement Developer Relations team

Streamline your data backups with incremental exports for Google Workspace

Google Workspace administrators can now utilize incremental exports when backing up organizational data. Instead of re-exporting their entire organization's data, admins can export frequent snapshots of their data into their organization’s own Google Cloud Storage (GCS) bucket.

Key benefits include faster completion times, reduced Google Cloud Storage consumption and costs, and the ability to establish more frequent backup schedules to mitigate the risk of potential data loss. 

Specifically, admins can schedule automated exports for Gmail, Drive, and Chat, with the flexibility to scope data by organizational unit (OU), group, or specific users. They can initiate:

  • Periodic full backups - establishing a baseline snapshot through regular full exports
    • Quarterly (every 3 months)
    • Semi-annually (every 6 months)
    • Annually (every year)
  • Frequent incremental backups - supplementing the baseline with frequent incremental backups, such as backing up data from the "last x days" every "y days"
    • Capture data from the last 5 days, running every 3 days
    • Capture data from the last 7 days, running every 5 days


Getting started

Rollout pace

Availability

Resources

Chrome Dev for Desktop Update

The Dev channel has been updated to 151.0.7912.0 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. 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.

Chrome Release Team
Google Chrome

Google Ads API v21 sunset reminder

Google Ads API v21 will sunset on August 5, 2026. Starting on this date, all v21 API requests will begin to fail. Migrate to a newer version prior to August 5, 2026 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

You can view a list of methods and services your project has recently called using the Google Cloud Console:

  1. Open APIs & Services in the Google Cloud Console.
  2. Click Google Ads API in the table.
  3. On the Metrics subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as 
    google.ads.googleads.v21.services.GoogleAdsService.Mutate.
  4. (Optional) Choose the timeframe you want to view for your requests.

If you have any questions or want to discuss this post, please reach out to Google Ads API support or start a discussion on our “Google Advertising and Measurement Community” Discord server.

Ben Karl
Google’s Advertising and Measurement Developer Relations team

Chrome for Android Update

Hi, everyone! We've just released Chrome 149 (149.0.7827.200) 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: 149.0.7827.200/201, Linux: 149.0.7872.200) unless otherwise noted.

Harry Souders

Multi-party approvals in the Google Ads API

As part of improving security for Google Ads accounts, the Google Ads API will start requiring multi-party approvals when performing sensitive API actions. This is part of a broader change in Google Ads that requires multi-party approvals to perform sensitive actions in your Google Ads account. These important security updates will start rolling out starting on July 27, 2026, and will be enabled for all users over the next few weeks.

What is changing?

When this change goes live, the following API calls will change their behavior.

Inviting a user

If you use the CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation method to invite a new user to manage a Google Ads account, the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the system will pause the standard workflow and will not immediately generate a CustomerUserAccessInvitation or dispatch the invitation email. A MultiPartyAuthReview resource is initiated instead, with its resource name provided in the response. Once the pending review receives approval from a second account administrator, the CustomerUserAccessInvitation will be created and the invited user will receive their email. No new invites can be created for the user until the pending review is resolved.

Updating or terminating a user’s access

If you use the CustomerUserAccessService.MutateCustomerUserAccess method to adjust a user's permissions using the update operation or revoke access using the remove operation, the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the API generates a MultiPartyAuthReview resource in a pending state and returns its resource name. Your requested modifications will remain pending and will only take effect once the multi-party review is successfully approved by a second account administrator. The CustomerUserAccess under review cannot be mutated until the pending review is resolved.

How do I approve a multi-party approval request?

You can fetch a pending MultiPartyAuthReview by using the GoogleAdsService.Search or GoogleAdsService.SearchStream methods, using the following GAQL query. 

SELECT 
    multi_party_auth_review.resource_name,
    multi_party_auth_review.multi_party_auth_review_id,
    multi_party_auth_review.creation_date_time,
    multi_party_auth_review.request_user_email,
    multi_party_auth_review.operation_type,
    multi_party_auth_review.justification,
    multi_party_auth_review.target_resource,
    multi_party_auth_review.customer_user_access_review.old_customer_user_access,
    multi_party_auth_review.customer_user_access_review.new_customer_user_access,
    multi_party_auth_review.customer_user_access_invitation_review.new_customer_user_access_invitation
FROM multi_party_auth_review 
WHERE multi_party_auth_review.review_status = 'PENDING'

A pending MultiPartyAuthReview request can be approved or rejected using a MultiPartyAuthReviewService.ResolveMultiPartyAuthReview API request. The review needs to be done by a second administrator who did not create the original request. This can either be a human or a service account with administrator privileges. The pending review can be revoked by the original requestor.

What do I need to do?

If your application uses these methods, make sure to update it to handle the multi-party approval workflows before July 27, 2026. We have added support for multi-party approvals to all the major versions of the API (v24.2, v23.3, v22.2 and v21.2). If you are using an official client library, make sure to download their latest version. You can refer to the following guides to learn more about these changes, which cover details on

For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server. For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

 - Anash P. Oommen, Google Ads API Team