Upcoming changes to Search and SearchStream responses in Google Ads API

What’s changing?

Last year, we introduced query_resource_consumption metric as a way to measure how expensive a Google Ads API query is. However, this cost was not returned when the query results were empty.

Starting the week of August 4, 2025, we will modify the behavior of both the Search and SearchStream methods of GoogleAdsService in all the API versions to return the query_resource_consumption metric and the field_mask field even when the query results are empty. The responses for empty query results will change as follows:

Method Old response New response
Search 
{    
    "fieldMask": "..."     
}
 
{
    "fieldMask": "...",
    "query_resource_consumption": 123
}
SearchStream 
[]
 
{
    "fieldMask": "...",
    "queryResourceConsumption": 206
}

What do I need to do?

If you are using Search and SearchStream methods to download Google Ads API reports, make sure your application can handle the modified response.

If you have any questions or need help, check out the Google Ads API support page for options.

Reach out to the Google Ads product support team for any questions related to account policies.

 - , Google Ads API Team

Access Gemini Audit logs using the Reporting API, the security and audit investigation tools

What’s changing

Gemini Audit logs are now accessible through the Reporting API (Admin SDK). This allows admins to track user activity and interactions with Gemini across Workspace app, including: 
  • The action performed by the user within a Workspace application, initiated or assisted by Gemini. For example: formalizing copy, generating a background, or summarizing a conversation. 
  • The specific app where Gemini inWorkspace apps was used, for example Chat, Gmail, or Docs. 
  • The specific features which were used, for example “help me write”, “remove image background” or “help me organize”. 
  • And more – see our API documentation for more information on the types of Gemini in Workspace activity you can query. 
As part of this update, this information will be available in the security investigation tool and audit investigation tool as well. 

Who’s impacted 

Admins 

Why you’d use it

Admins can use the Reports API to analyze how their users are engaging with Gemini at scale. These valuable insights can help organizations get the most out of Gemini. Specifically: 
  • Monitoring adoption and usage: Admins can track the overall use of Gemini features across the organization and within specific Workspace applications (Gmail, Docs, Slides, Sheets, Gemini app). This includes identifying the number of active Gemini users, their usage patterns per app, and the “Last Used” time stamp for each user. 
  • Understanding feature utilization: The reports detail how frequently specific Gemini features like content summarization and generation are used within different applications. 
  • Identifying training needs: By observing feature and app usage, admins can pinpoint areas where users might require additional training or resources to maximize their use of Gemini's capabilities. 
  • Identifying power users: The reports can help identify individuals who are heavily utilizing Gemini features, potentially recognizing internal champions who can share their expertise and best practices with other users. 
Further, surfacing this information in the audit and investigation tool can help admins review user activity related to Gemini, while the security and investigation tool can help admins to identify, triage, and take action on potential security and privacy issues.

Getting started 

Rollout pace 

  • Reports API: Available now.
  • Security investigation tool and the audit investigation tool: Extended rollout (potentially longer than 15 days for feature visibility) beginning on July 1, 2025

Availability 

  • Available for all customers with a Google Workspace edition that includes access to Gemini in Workspace apps, as well as customers with a Gemini add-on*. 
  • The Reports API and audit and investigation tool is available for all Google Workspace customers. 
  • The security investigation tool is available for Google Workspace
    • Frontline Standard and Plus 
    • Enterprise Standard and Plus 
    • Education Standard and Plus 
    • Enterprise Essentials Plus 
    • Cloud Identity Premium.

*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 

Access Gemini Audit logs using the Reporting API, the security and audit investigation tools

What’s changing

Gemini Audit logs are now accessible through the Reporting API (Admin SDK). This allows admins to track user activity and interactions with Gemini across Workspace app, including: 
  • The action performed by the user within a Workspace application, initiated or assisted by Gemini. For example: formalizing copy, generating a background, or summarizing a conversation. 
  • The specific app where Gemini inWorkspace apps was used, for example Chat, Gmail, or Docs. 
  • The specific features which were used, for example “help me write”, “remove image background” or “help me organize”. 
  • And more – see our API documentation for more information on the types of Gemini in Workspace activity you can query. 
As part of this update, this information will be available in the security investigation tool and audit investigation tool as well. 

Who’s impacted 

Admins 

Why you’d use it

Admins can use the Reports API to analyze how their users are engaging with Gemini at scale. These valuable insights can help organizations get the most out of Gemini. Specifically: 
  • Monitoring adoption and usage: Admins can track the overall use of Gemini features across the organization and within specific Workspace applications (Gmail, Docs, Slides, Sheets, Gemini app). This includes identifying the number of active Gemini users, their usage patterns per app, and the “Last Used” time stamp for each user. 
  • Understanding feature utilization: The reports detail how frequently specific Gemini features like content summarization and generation are used within different applications. 
  • Identifying training needs: By observing feature and app usage, admins can pinpoint areas where users might require additional training or resources to maximize their use of Gemini's capabilities. 
  • Identifying power users: The reports can help identify individuals who are heavily utilizing Gemini features, potentially recognizing internal champions who can share their expertise and best practices with other users. 
Further, surfacing this information in the audit and investigation tool can help admins review user activity related to Gemini, while the security and investigation tool can help admins to identify, triage, and take action on potential security and privacy issues.

Getting started 

Rollout pace 

  • Reports API: Available now.
  • Security investigation tool and the audit investigation tool: Extended rollout (potentially longer than 15 days for feature visibility) beginning on July 1, 2025

Availability 

  • Available for all customers with a Google Workspace edition that includes access to Gemini in Workspace apps, as well as customers with a Gemini add-on*. 
  • The Reports API and audit and investigation tool is available for all Google Workspace customers. 
  • The security investigation tool is available for Google Workspace
    • Frontline Standard and Plus 
    • Enterprise Standard and Plus 
    • Education Standard and Plus 
    • Enterprise Essentials Plus 
    • Cloud Identity Premium.

*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 

Improving Google Meet hardware admin log events with more granular information

What’s changing 

We’re improving the granularity of Google Meet hardware Admin log events. This upgrade offers a more comprehensive and precise audit trail, enabling you to better track and understand administrative actions related to your Google Meet hardware. This increased visibility will enhance your organization's security and facilitate more effective troubleshooting. 

First, the “HANGOUTS DEVICE SETTING” event category is going away and will be replaced with a new event type: “GOOGLE MEET HARDWARE”. This does not apply for “Chromebox for meetings Device Setting Change”, which will move to “APPLICATION SETTING” in a follow-up launch. 

The following changes made in the Google Meet hardware Admin console will be logged as an Admin log event under “GOOGLE MEET HARDWARE”:
  • Change lifecycle state on Meet device 
  • Change OU membership of Meet device 
  • Change properties on Meet device 
    • This includes all information found in the Admin console under Devices > Google Meet Hardware > Devices > [Device name] > Device settings. 
  • Perform bulk action on Meet devices
  • Perform command on Meet device

You can also view additional fields related to these new events, including: 
  • Device ID 
  • Resource ID(s) for Serial Number 
  • Device type (will always be ‘meet’) 
  • Action(s) (if applicable) 
  • Setting name (if applicable) 
  • And, if applicable, additional information, such as the meeting code and more. 
Note that some fields are not visible in the log viewer by default; you can add additional fields using the “Manage columns” button.



In the coming weeks, you will be able to create, change, and delete application settings under “Application Settings”. All changes to settings found in the Admin console under Devices > Google Meet hardware > Settings will be audited here. We will share more details in the coming weeks. 

Additional details 

In the coming months, we are removing all events under the “HANGOUTS DEVICE SETTINGS” event type since the product name is obsolete, and the new events will include this information and even more data. Prior to their removal, you’ll still be able to filter for these events, however new activity will be only captured under the new “GOOGLE MEET HARDWARE” events.


 This table has more details:

New Event name 

Associated Actions 

Perform command on Meet device

  • Reboot 

  • Connect to Meeting 

  • Mute 

  • Hangup 

  • Run Diagnostics 

  • Passcode viewed 

Perform bulk action on Meet devices 

  • Download device information

  • Bulk update devices

  • Reboot

  • Connect to Meeting

  • Mute

  • Hangup


*Audit logs will also be created for the individual devices included in a bulk action.

Change properties on Meet device 

Occupancy detection, noise cancellation, etc.

Change lifecycle state on Meet device 

Provision or deprovision a Meet device

Change OU membership of Meet device 

Moving a device from OU to OU


 Getting started 

  • Admins: Visit the Help Center to learn more about admin log events. 
  • End users: There is no end user impact or action required. 

Rollout pace 

Important note: The new log events will be available in the user interface via the Event filter drop-down under “Google Meet Hardware” beginning July 7, 2025, however data will remain under the old log events (“Hangouts Device Settings”).Data will become available under the new log events starting July 21, 2025. You can use the time in between to update any scripts or rules to align with the new log events. 


Availability 

  • This update impacts all Google Workspace customers with Google Meet hardware devices. 

Resources 

Improving Google Meet hardware admin log events with more granular information

What’s changing 

We’re improving the granularity of Google Meet hardware Admin log events. This upgrade offers a more comprehensive and precise audit trail, enabling you to better track and understand administrative actions related to your Google Meet hardware. This increased visibility will enhance your organization's security and facilitate more effective troubleshooting. 

First, the “HANGOUTS DEVICE SETTING” event category is going away and will be replaced with a new event type: “GOOGLE MEET HARDWARE”. This does not apply for “Chromebox for meetings Device Setting Change”, which will move to “APPLICATION SETTING” in a follow-up launch. 

The following changes made in the Google Meet hardware Admin console will be logged as an Admin log event under “GOOGLE MEET HARDWARE”:
  • Change lifecycle state on Meet device 
  • Change OU membership of Meet device 
  • Change properties on Meet device 
    • This includes all information found in the Admin console under Devices > Google Meet Hardware > Devices > [Device name] > Device settings. 
  • Perform bulk action on Meet devices
  • Perform command on Meet device

You can also view additional fields related to these new events, including: 
  • Device ID 
  • Resource ID(s) for Serial Number 
  • Device type (will always be ‘meet’) 
  • Action(s) (if applicable) 
  • Setting name (if applicable) 
  • And, if applicable, additional information, such as the meeting code and more. 
Note that some fields are not visible in the log viewer by default; you can add additional fields using the “Manage columns” button.



In the coming weeks, you will be able to create, change, and delete application settings under “Application Settings”. All changes to settings found in the Admin console under Devices > Google Meet hardware > Settings will be audited here. We will share more details in the coming weeks. 

Additional details 

In the coming months, we are removing all events under the “HANGOUTS DEVICE SETTINGS” event type since the product name is obsolete, and the new events will include this information and even more data. Prior to their removal, you’ll still be able to filter for these events, however new activity will be only captured under the new “GOOGLE MEET HARDWARE” events.


 This table has more details:

New Event name 

Associated Actions 

Perform command on Meet device

  • Reboot 

  • Connect to Meeting 

  • Mute 

  • Hangup 

  • Run Diagnostics 

  • Passcode viewed 

Perform bulk action on Meet devices 

  • Download device information

  • Bulk update devices

  • Reboot

  • Connect to Meeting

  • Mute

  • Hangup


*Audit logs will also be created for the individual devices included in a bulk action.

Change properties on Meet device 

Occupancy detection, noise cancellation, etc.

Change lifecycle state on Meet device 

Provision or deprovision a Meet device

Change OU membership of Meet device 

Moving a device from OU to OU


 Getting started 

  • Admins: Visit the Help Center to learn more about admin log events. 
  • End users: There is no end user impact or action required. 

Rollout pace 

Important note: The new log events will be available in the user interface via the Event filter drop-down under “Google Meet Hardware” beginning July 7, 2025, however data will remain under the old log events (“Hangouts Device Settings”).Data will become available under the new log events starting July 21, 2025. You can use the time in between to update any scripts or rules to align with the new log events. 


Availability 

  • This update impacts all Google Workspace customers with Google Meet hardware devices. 

Resources 

Level up your game: Google Play’s Indie Games Fund in Latin America returns for its 4th year

Posted by Daniel Trócoli – Google Play Partnerships

We're thrilled to announce the return of Google Play's Indie Games Fund (IGF) in Latin America for its fourth consecutive year! This year, we're once again committing $2 million to empower another 10 indie game studios across the region. With this latest round of funding, our total investment in Latin American indie games will reach an impressive $8 million USD.

Since its inception, the IGF has been a cornerstone of our commitment to fostering growth for developers of all sizes on Google Play. We've seen firsthand the transformative impact this support has had, enabling studios to expand their teams, refine their creations, and reach new audiences globally.

What's in store for the Indie Games Fund in 2025?

Just like in previous years, selected small game studios based in Latin America will receive a share of the $2 million fund, along with support from the Google Play team.

As Vish Game Studio, a previously selected studio, shared: "The IGF was a pivotal moment for our studio, boosting us to the next level and helping us form lasting connections." We believe in fostering these kinds of pivotal moments for all our selected studios.

The program is open to indie game developers who have already launched a game, whether it's on Google Play, another mobile platform, PC, or console. Each selected recipient will receive between $150,000 and $200,000 to help them elevate their game and realize their full potential.

Check out all eligibility criteria and apply now! Applications will close at 12:00 PM BRT on July 31, 2025. To give your application the best chance, remember that priority will be given to applications received by 12:00 PM BRT on July 15, 2025.




Google Play logo