Introducing the new Meetings section in Google Chat

We’re introducing a dedicated Meetings section in Google Chat—a new way to organize your conversation list and keep your meeting conversations in one place.

Previously, meeting conversations lived in your direct messages, often making it difficult to find specific project discussions or meeting notes.

You can now group all past and future meeting chats into a single, dedicated section in your conversation list. Once a meeting concludes, the meeting conversation (if used) seamlessly moves into this section, providing a persistent home for ongoing follow-ups.

When the feature becomes available, users may see a promotional in-app banner or tooltip highlighting the new Meetings section and inviting them to enable it to better organize their conversation list.

Image depicts a user selecting "Try it" from the promotional prompt to initiate the new Meetings section

Once created, the new Meetings section appears as a distinct category in the conversation list, located under Direct Messages and Spaces. It acts as a smart folder that automatically aggregates any continuous meeting conversation in one place. This section can be moved, deleted, or reordered at any time.

Image depicts the newly created Meeting section under Direct Messages and Spaces in the conversation list

Key benefits include:

  • Organization: Keeps all meeting related conversations in one place.
  • Discoverability: Easily find details from a meeting days after the call has ended.
  • Control: This is an optional feature. You decide where the section sits in your conversation list, and you can move individual meeting threads to any custom section you’ve created.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: This feature is off by default and requires user opt-in. To activate this feature, users must go to the three-dot overflow menu found on any section of their conversation list. From the resulting dropdown, they should choose "Create a meeting section" and then click "Create." Once enabled, the section will appear in the conversation list  beneath Direct Messages and Spaces, and can be moved or removed at any time. Visit the Help Center to learn more.
Image depicts a user going to the 3 dot overflow to manually create the meeting section.

Rollout pace

Availability

  • Available to all Google Workspace customers, Workspace Individual subscribers, and users with personal Google accounts

Resources

Upcoming changes to Lookalike user lists in the Google Ads API, starting April 30, 2026

Google Ads is committed to providing a reliable and efficient environment for all advertisers. To ensure that our systems remain stable and that resources are allocated fairly, we are introducing a uniqueness check for Lookalike user lists that prevents the creation of duplicate lists. These changes primarily impact Demand Gen campaigns and will begin to be enforced starting on April 30, 2026.

A Lookalike user list is considered a duplicate if it shares all of the following attributes with an existing list:

  • Seed lists: The underlying source audiences used to build the Lookalike.
  • Expansion level: The degree of similarity to the seed lists.
  • Country targeting: The geographical reach of the Lookalike list.

If an advertiser attempts to create a duplicate list after April 30, 2026, the Google Ads API will return the error code DUPLICATE_LOOKALIKE for v24 and beyond. For earlier versions, the error will be RESOURCE_ALREADY_EXISTS.

What this means for you

For the majority of advertisers, these changes will go unnoticed, as most current usage falls well within these new boundaries. However, to ensure a smooth transition, we recommend the following:

  • Reuse audiences: Instead of creating a new, identical Lookalike list, verify if an existing one with the same configuration can be reused in your campaigns.
  • Update error handling: If you use the Google Ads API, ensure your integrations are prepared to handle the new error starting on April 30, 2026: v24 will return the DUPLICATE_LOOKALIKE error code and all previous versions will return RESOURCE_ALREADY_EXISTS.

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.

 - Dora Sun - Google Ads API Team

Workspace audit logs: New functionality and expanded event fields

We’re releasing a number of enhancements to Workspace audit logs, including:

  1. Log filtering enhancements for Resource fields in the security investigation tool for Gmail and Google Drive
  2. Updated Application and Network fields available in the Workspace audit log integration with Google Security Operations (SecOps)
  3. Expanded filtering in the AdminSDK Activities.List method
  4. New OwnerDetails field in the events published to the AdminSDK and BigQuery

Log filtering enhancements for Resource fields in the security investigation tool for Gmail and Google Drive

The security investigation tool now features improved filtering for the Resources attribute for Gmail and Google Drive log events. These updates enable administrators to execute more granular searches, particularly by utilizing classification labels. Because classification labels offer essential metadata for identifying sensitive content and enforcing security policies, the capability to filter audit logs through these labels is vital for analyzing data patterns and investigating security incidents.

Additionally, we have also added filtering support for the Actor application info attribute for Gmail log events.

Updated Application and Network fields available in the Workspace audit log integration with Google Security Operations (SecOps)

The following fields will now be included in the audit events sent to SecOps, where applicable:


Expanded filtering in the AdminSDK Activities.List method

We’re adding filtering for the following fields in the Activities.List method of the AdminSDK:

  • RegionCode: Filter audit logs belonging to specified region using networkInfoFilter field in the api request
  • OAuthClientId: Filter audit logs where actions are done by specified app using applicationInfoFilter field in the api request
New OwnerDetails field in the events published to the AdminSDK and BigQuery

A new OwnerDetails field in Resource Details identifies who owns a resource using two primary fields:

  • Owner Type: This specifies the category of the owner. The owner of the resource can be an individual person (USER), entire organization (CUSTOMER), or a GROUP. SHARED_DRIVE
  • Owner Identity: This contains specific details (like IDs or email addresses) of that owner

Getting started

Rollout pace

Availability

Resources