South Carolina, it’s time to connect!

Google Fiber is officially available in Fort Mill and Tega Cay, South Carolina! Residents can sign up for the new lifestyle product that best fits their household —and we can’t wait for you to experience what your best internet can do.

Thumbnail

With speeds up to 8 Gigs — whether you’re streaming your favorite shows, working from home, gaming online, or all of the above, our fast, dependable lifestyle internet products are available to keep up with your life — GFiber can keep up and then some. As always, all products come with all the equipment you need and no data caps or annual contracts.

Check availability and sign up for service at fiber.google.com. If we’re not at your address just yet, we’ll keep you posted as we continue to expand our network.

A huge thank you for the warm welcome we’ve received in South Carolina. We’re proud to be part of the community and look forward to even stronger connections! 

Posted by Jess George, Head of Government and Community Affairs, East Region



Google Ads AI Max for Search campaigns Open Beta

The open beta launch of AI Max for Search campaigns in the Google Ads UI will begin on 27 May 2025.

While full AI Max for Search campaigns support in the Google Ads API is planned for v21 in August 2025, we want to ensure you're prepared for the open beta rollout and understand its potential impact on your API interactions.

What is AI Max for Search campaigns?
What is Changing?
During the open beta period, before full API support arrives in v21, there will be a transitional phase. Here's what API users need to know:
  1. Feature Grouping in the UI: When a user enables AI Max for Search campaigns for a campaign in the Google Ads UI, several legacy features will be grouped into the new AI Max for Search campaigns settings:
    • Text customization (formerly known as Automatically created assets (ACA))
    • Campaign-level broad match (the setting itself)
    • Brand inclusions (previously tied to campaign-level broad match)
    • Campaign-level brand exclusions
  2. Potential API Conflicts During Transition: Once AI Max for Search campaigns has been enabled and then disabled for a campaign via the UI, managing its associated features (ACA, brand list inclusions/exclusions) using any API version is subject to feature grouping and may cause errors. Starting with v21, AI Max for Search campaigns can be activated through the API.
    • Why? Disabling AI Max for Search campaigns in the UI during this interim period doesn't fully revert the underlying settings configuration back to the pre-AI Max for Search campaigns state compatible with older API versions for these specific features.
    • Campaign-Level Broad Match: Attempts to toggle the campaign-level broad match setting via the API will be allowed but may function differently depending on the AI Max for Search campaigns state. Keywords will still be converted to Broad Match if the setting is enabled via the API, but the primary control mechanism moves to AI Max for Search campaign.
    • Text customization: Attempts to deactivate text customization via API requests will raise an error if Final URL expansion is enabled in the UI.
  3. Mitigation - UI Warnings: To prevent accidental disruption, the Google Ads UI will display warning messages when enabling or disabling AI Max in Search campaigns for campaigns that use these legacy features, explicitly mentioning the potential impact on API workflows during this beta period.
  4. Recommendation: We strongly advise coordinating within your teams. If your organization relies heavily on API workflows for managing ACA or Brand Lists, be cautious about enabling and then disabling AI Max in Search campaigns in the UI for those campaigns until full API support lands in v21 in August 2025.
What Stays the Same:
  • You can continue to manage existing Search campaigns using ACA, campaign-level broad match, and brand exclusions via the current API version (v19) as long as AI Max in Search Campaigns has not been enabled and then disabled for those specific campaigns in the UI.
  • Ad Group level Brand Inclusions and Locations of Interest (LOI) pilots (outside of AI Max for Search campaigns) are ending. Functionality for these will only be available within AI Max for Search campaigns going forward.
Preparing for the Future - v21 and beyond:
  • Full Support Coming: API v21 (planned for August 2025) will introduce dedicated fields and services to fully manage all AI Max for Search campaigns features, including the new consolidated controls.
  • Legacy Field Deprecation: Following the launch and adoption of v21, older API versions will sunset. At that point, the legacy fields for ACA, campaign-level broad match, and standalone brand exclusions/inclusions will be fully deprecated and removed from the API.
If you have any questions, please contact us on the forum.
Bob Hancock, Google Ads API Team

Update to the 2025 Google Ads API release schedule

We previously announced our 2025 Google Ads API release plans. We are introducing a few changes to this schedule as a part of our ongoing efforts to evolve our release process. The new schedule lets us make various product features available earlier in the Google Ads API. As usual, additional details on new features will follow as part of the release notes for individual versions.

  1. V20_1 will be upgraded to a major version and named V21.
  2. V21 will be renamed to V22.
  3. We will add two minor releases (v19_2, v20_1) alongside V21 to add these features in existing Google Ads API versions.
  4. The projected launch dates will remain unchanged.

Here’s our updated schedule.

Version Planned Release

Type

Projected launch Projected sunset
V20 Major June/July 2025 June 2026
V21 Major August/September 2025 August 2026
v19_2 Minor August/September 2025 February 2026
v20_1 Minor August/September 2025 June 2026
V22 Major October/November 2025 October 2026

Please take a look at your future plans to make sure they still align with the upcoming Google Ads API release schedule.

How to get help

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

 - , Google Ads API Team

Pre-configure Gemini app conversation history admin settings before they take effect

What’s changing

Starting today, Workspace admins can pre-configure the new Gemini conversation history admin settings before they take effect for their Gemini app users (expected by the end of May 2025). By default, “Gemini conversation history” will be ON and ”Conversation retention” will be set to 18 months (inline with current behavior). 

Generative AI > Settings > Gemini app > Gemini conversation history


Who’s impacted

Admins and end users

Additional details

  • If "Gemini conversation history" is OFF, chats are saved in user accounts for up to 72 hours. This lets Google provide the service and process any feedback. This chat activity won’t appear in a user’s Gemini Apps Activity.
    • Regardless of whether the Gemini app history is on or off, content in chats adheres to enterprise privacy and security protections as described in the Google Workspace Terms of Service. You can also learn more in the Privacy Hub. 
    • If you turn the setting from ON to OFF, existing user conversation history from before the setting is turned OFF is stored for the length of time specified by the "Conversation retention" setting.
  • This update will not impact your current Gemini app service setting.
  • This update will not impact Gemini in Workspace apps (e.g., Gemini in Gmail).

Getting started

  • Admins: 
    • Review and update the "Gemini conversation history" settings before we enforce these settings (expected by the end of May 2025). Visit the Help Center to learn more about configuring Gemini app conversation history settings for your users.
    • If no changes are made, the default settings will apply: “Gemini conversation history” set to ON and "Conversation retention” set to 18 months. Activity older than 18 months will be automatically deleted.

  • End Users: 
    • Users cannot override the Gemini conversation history settings configured by their admin.
    • These admin settings will override any individual user changes previously made to their Gemini Apps Activity settings (gemini.google.com or Gemini mobile app).

Rollout pace


We will publish a separate Workspace Updates blog post once we begin to enforce these settings, which is expected by the end of May 2025.


Availability

  • Available for all Google Workspace users with access to the Gemini app.

Resources


Dev Channel Update for ChromeOS / ChromeOS Flex

The Dev channel is being updated to OS version 16261.0.0 (Browser version 137.0.7137.0) 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