Author Archives:

Google Vault now supports retention rules and litigation holds for Gemini app

Google Vault now supports retention rules and litigation holds for the Gemini app on web and mobile. Previously, administrators were able to use Vault to search Gemini app conversations and export those search results. With this update, administrators can now also create, update, and delete the following for the Gemini app:

  • Default retention rules: Set default retention rules for the Gemini app for a finite or indefinite retention period.
  • Custom retention rules: Create custom retention rules for the Gemini app by organizational unit (OU) or the entire domain for a finite or indefinite retention period.
  • Litigation holds: Place holds on the Gemini app data for a specific OU or a list of users.
Google Vault is an eDiscovery and information governance tool for Google Workspace that enables customers to retain, hold, search, and export users’ Google Workspace data. With this update, customers can expand their regulatory and legal eDiscovery management to include retention and holds for the Gemini app, making it easier to comply with data obligations from a central tool.

Additional details

  • Application scope: This update applies specifically to the Gemini app (on web and mobile) and is not applicable to Gemini in Google Workspace features integrated into other apps (such as "Help me write" in Gmail or Docs), as those specific interactions are not retained in the same manner.
  • Policy precedence: Vault retention rules and holds will always take precedence over Admin console settings, user deletion settings, or user activity settings.
    • Example: If a user deletes a conversation or turns off their activity setting, but an active Vault hold requires retention, the data is hidden from the user but remains fully retained and visible to Vault administrators.
  • API support: Support for Vault API users will be available in the coming weeks.

Getting started

Rollout pace

Availability

  • Business: Business Plus
  • Other Editions: Frontline Standard and Plus; Enterprise Essentials Plus
  • Enterprise: Enterprise Standard and Plus
  • Education: Education Fundamentals, Standard and Plus
  • Other Add-ons: Vault

Resources

Dynamic Search Ads (DSA) Automigration Delayed to February 2027 and Campaign Creation Restored

What is changing?

Google is extending the timeline for the transition of Dynamic Search Ads (DSA) to AI Max for Search campaigns and restoring campaign creation functionality.

  • Automigration Delayed: The automatic upgrade of DSA campaigns to AI Max (or Search campaigns with broad match and Smart Bidding) has been postponed from September 2026 to February 2027.
  • Creation Restored: The ability to create new DSAs is being restored on June 15, 2026.

This change is designed to give advertisers additional time to manage their own transitions, perform thorough testing, and ensure a seamless migration to AI Max.

What is the DSA Migration?

Dynamic Search Ads (DSA) have long helped advertisers capture relevant searches by using website content to target ads. As part of our commitment to delivering the best performance through Google AI, we are transitioning legacy search features to more advanced, asset-based AI Max for Search campaigns.

Why is this changing?

By moving the automigration to February 2027 and restoring the ability to create new DSAs, we are providing additional flexibility to perform these migrations on your own schedule and terms.

How to Prepare

Although you now have additional time, we strongly recommend proactively managing your migration rather than waiting for the automatic upgrade in February 2027. Manual migration allows you to tailor your assets and maintain tighter control over your campaign structures.

Step 1: Audit Your Accounts

Identify all active DSAs and ad groups currently running in your accounts.

If you are using the Google Ads API, you can query the campaign resource to find campaigns with the advertising channel type set to SEARCH and targeting settings configured for dynamic search ads: 

SELECT
  campaign.id,
  campaign.name,
  campaign.status,
  campaign.dynamic_search_ads_setting.domain_name
FROM
  campaign
WHERE
  campaign.status = 'ENABLED'
  AND campaign.dynamic_search_ads_setting.domain_name IS NOT NULL

Step 2: Begin Side-by-Side Testing

Use the restored DSA creation functionality to maintain your baseline while you test AI-powered alternatives. We recommend setting up Campaign Experiments to test AI Max for Search campaigns (with broad match and Smart Bidding) against your existing DSA campaigns to measure performance parity.

Step 3: Utilize Voluntary Upgrade Tools

When you are ready to transition, use the voluntary upgrade tools available in the Google Ads UI. These tools allow for a "one-click" transition that preserves historical reporting and minimizes learning-phase disruptions by mapping your DSA targets to their modern equivalents.

The Updated Transition Timeline

We encourage you to take advantage of this extension to complete your migrations. The updated timeline is as follows:

  • Immediate (June 2026): DSA campaign creation is fully restored. Advertisers can create and edit DSA campaigns as needed.
  • June 2026 – January 2027: Extended testing and voluntary migration period. Advertisers should actively transition campaigns.
  • January 2027: Ability to create DSAs is removed.
  • February 2027: Automigration begins. Any remaining active DSA campaigns will be automatically upgraded to Performance Max or AI-powered Search campaigns.

Bob Hancock, Google Ads API Team

DiffusionGemma: The Developer Guide

DiffusionGemma is an experimental text-generation model built on the Gemma 4 architecture that uses diffusion-based parallel generation instead of token-by-token autoregression, enabling much faster inference, bidirectional context awareness, and real-time self-correction while remaining deployable on consumer GPUs. Its architecture generates and refines 256-token blocks in parallel through iterative denoising, allowing it to handle complex constraint-based tasks such as Sudoku more effectively than traditional language models and demonstrating strong gains from fine-tuning. The model integrates with vLLM and other popular inference frameworks, giving developers access to a new non-autoregressive approach that combines high performance, efficient long-context scaling, and straightforward customization and deployment.

Google Meet now supports sending 1080p HD video from ChromeOS meeting room hardware

We previously launched support for sending full HD video (1080p) in Meet on the web, and we’re now extending that capability to Google Meet room hardware based on ChromeOS.

Google Meet will use full HD when the additional bandwidth is needed for sharp video from the room, such as:

  • On large screens: When others in the call are viewing the room on large monitors or TVs with a layout that makes 1080p necessary, such as full-screen views in Spotlight mode, 1:1 calls or dual-screen rooms. ​
  • When someone pins your video: If a person in the meeting "pins" the room, Meet will send the highest available quality.
  • ​When the meeting is being recorded: Recorded meetings use full HD from the room for the saved meeting video.
​Full HD is available from devices that use a high-resolution camera and can handle the additional processing over a fast, stable internet connection. Meet will continue to automatically adjust video quality downwards if network constraints are detected to ensure a smooth meeting experience.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: There is no end user setting for this feature; the upgrade happens seamlessly in the background when conditions are met.

Rollout pace

Availability

  • Available to all Google Workspace customers with Google Meet hardware devices

Resources