Author Archives:

Unlocking the Power of the TPU Stack: Introducing our new Developer Hub

Google has officially launched the TPU Developer Hub, a centralized educational resource designed to help model builders and developers maximize the performance of Google Cloud TPUs. The hub offers code-first resources, open-source recipes, and deep-dive documentation covering hardware architecture, software optimization, debugging, parallelism, and networking. These materials are tailored for both human developers and AI-assisted tools to streamline everything from large-scale training to low-latency inference workloads.

AI note-taking is now available in Google Voice

“Take notes for me” is available in Google Voice for your phone calls. This powerful new feature records and transcribes calls, summarizes key points, and organizes action items, which are sent via Gmail and stored in the Voice app. This built-in tool eliminates manual note-taking, ensures critical details are never lost, and drives a highly professional customer experience.

This feature is available for new Voice users by default and requires manual enablement for existing Voice users. Admins can easily turn it on in the admin console at the domain, OU, or group level. Once turned on, eligible users will see the “Record” button become a “Notes” button during calls.

When you tap "Notes" during a Voice call, your conversation will be recorded and transcribed, while Gemini captures notes. When you hang up, you'll get an email with your notes in the body of the email. You can then find the transcript, audio recording, and notes saved right inside the Voice app alongside call details.





Privacy, ownership, and consent
  • Post-call notes and transcriptions are strictly accessible only to the individual who initiated the AI capture. If multiple people start it, everyone gets their own separate artifact.
  • An audio disclosure ("This call is being recorded and captured by AI") ensures all participants are fully informed the moment the feature is activated. Admins are able to customize the consent in the admin console. Admins can also customize the consent language to align with their company's standards.
Note that this feature is only available in English at this time.

Getting started

Rollout pace

Availability

  • Available to all Google Workspace customers with Voice Standard and Voice Premier add-ons, as well as customers with Voice Standard standalone plans

Resources

New discoverable space setting in Google Chat

Google Chat is expanding how users can find and join spaces by adding a third access option called "Discoverable."

Previously, spaces were either private (invite-only) or open (anyone in the organization can find and join). Discoverable spaces provide a new option between the two: they appear when users browse for spaces within their organization, but the conversation history and messages remain private until an owner or manager approves a user's request to join.

This update helps organization leaders and community managers build groups that are easy to find without sacrificing data privacy. For instance, this setup is ideal for employee resource groups, specialized internal committees, or project teams that want to maintain an organization-facing presence but require membership vetting before sharing ongoing discussions.

Space settings showing three access types
Space settings showing three access types

Additionally, for customers that allow sharing spaces with multiple groups of users, advanced settings can be used to mix and match different groups of users for who can find and join the space.

Note: Space access types are only in space settings for now, but we will also extend them to space creation in the future.

Getting started

  • Admins: There is no admin control for this feature.
  • End users: Space owners and managers can update this option by navigating to their existing space settings. Visit the Help Center to learn more about changing space access levels.

Rollout pace

API and mobile support will follow within the next month. Stay tuned to API release notes.

Availability

  • Available to all Google Workspace customers

Resources

Updates to Smart Bidding Strategy Naming and Organization in Google Ads

Starting in June 2026, Google Ads is updating how bidding strategies are labeled to offer greater clarity between volume-focused and target-focused goals.

As part of this update, we are decoupling Target CPA and Target ROAS from Maximize conversions and Maximize conversion value, reverting them to their previous, distinct standalone naming conventions

Information for Developers and Google Ads API Users

For developers managing Google Ads accounts programmatically using the Google Ads API, these changes align the UI experience with specific API strategy types.

API Strategy Types

Campaigns optimizing for a target will focus on achieving that stated target rather than maximizing volume by internally lowering bids when budgets become constrained. To support this distinction, standalone TARGET_CPA and TARGET_ROAS concepts are being prioritized over bundled Maximize strategies with optional targets for applicable campaign types (such as Search campaigns).

What you should do:

  1. Review Integrations: Make sure your applications and custom dashboards correctly parse and display the standalone TARGET_CPA and TARGET_ROAS strategy designations.
  2. Campaign Creation Logic: When you create new campaigns using the API, evaluate your logic for setting optional targets on MAXIMIZE_CONVERSIONS or MAXIMIZE_CONVERSION_VALUE versus using standalone target strategies where applicable.
  3. Monitor Releases: Continue to monitor Google Ads API release notes and documentation. Specifically, look for updates on the BiddingStrategyType enum, the reintroduction and usage of standalone TargetCpa and TargetRoas messages, and any deprecation or changes to the optional target_cpa and target_roas fields within the MaximizeConversions and MaximizeConversionValue messages for Search campaigns.

What is changing?

The following bidding strategy labels are changing in the Google Ads user interface:

  • "Maximize conversions with a Target CPA" is changing to "Target CPA"
  • "Maximize conversion value with a Target ROAS" is changing to "Target ROAS"

Maximize Conversions and Maximize Conversion Value will remain available as distinct options for advertisers looking to maximize volume within a given budget without specifying a particular target.

What is NOT changing?

Note that the underlying bidding behavior remains exactly the same. This is strictly a labeling and organizational update.

  • There is no impact on campaign performance or bidding logic.
  • The transition requires no action in your accounts for campaigns to continue bidding as expected.

For more background on how these strategies operate and are managed, refer to the following resources:

If you have questions about these upcoming changes, please reach out via our developer forum or standard support channels.

- Aalap Shastri, Google Ads API Team