Lakewood now online! GFiber starts sign-ups today.


Colorado, here we come! Starting today, residents in the Eiber neighborhood of Lakewood can sign up to get connected to high-speed internet from GFiber to meet their families’ internet needs, whatever their online lives require. 

Thumbnail

We’re marking the occasion with an ice cream social at The Ice Cream Farm. This afternoon many Lakewood residents braved the rain to come by and get the scoop on GFiber while enjoying some delicious frozen treats on us. 

Lakewood Mayor Wendi Strom stops by our event at The Ice Cream Farm.

Lakewood customers will be able to choose any GFiber plan — 1 Gig for $70/month, 2 Gig for $100/month, 5 Gig for $125/month or 8 Gig for $150/month —  all with symmetrical uploads and downloads and equipment and installation included at no additional cost, no annual contracts and no data caps. Local businesses can sign up for GFiber for Business, offering Business 2 Gig for $250/month or Business 1 Gig for $100/month. 


This is just the next step for GFiber in the Denver metro area. GFiber Webpass has been available in Denver since 2017. We’re continuing to build our network out across Lakewood. As new segments are complete, we’ll open service in those neighborhoods. Additionally, we’re set to start construction in Westminster soon, and actively working on design and permitting for Golden, Wheat Ridge, and additional parts of Adams County.  For the latest on our construction progress and service availability in Colorado, sign up here.

Posted by Andy Simpson, General Manager Central Manager







Chrome for Android Update

Hi, everyone! We've just released Chrome 128 (128.0.6613.127) for Android . It'll become available on Google Play over the next few days. 

This release includes stability and performance improvements. You can see a full list of the changes in the Git log. If you find a new issue, please let us know by filing a bug.

Android releases contain the same security fixes as their corresponding Desktop (Windows & Mac: 128.0.6613.119/120 and Linux:128.0.6613.119) unless otherwise noted.


Harry Souders
Google Chrome

Beta Channel Update for ChromeOS / ChromeOS Flex

The Beta channel is being updated to OS version: 16002.17.0, Browser version: 129.0.6668.28 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.

Matt Nelson,

Google ChromeOS

Targeting and pacing changes in the Display & Video 360 API and Structured Data Files

In the coming months, the following updates to the Display & Video 360 product might impact your integration with the Display & Video 360 API and Structured Data Files:

For details on how to prepare for each of these changes, read the rest of this blog post and check the Display & Video 360 API Announced Deprecations page.

Changes to content targeting for YouTube & partners line items

On September 30, 2024, the majority of Digital Content Label and Other Content Types exclusion targeting will no longer be available for YouTube & partners line items.

In Display & Video 360 API, all TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION (excluding CONTENT_RATING_TIER_FAMILIES values) and TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION AssignedTargetingOptions will be removed from YouTube & partners line items. This will impact responses from assigned targeting LIST requests and attempts to retrieve these resources using advertisers.lineItems.targetingTypes.assignedTargetingOptions.get will return a 404 error.

In Structured Data Files, Line Item files will no longer use the following values in the “TrueView Category Exclusions Targeting” column:

  • “Embedded Videos”
  • “Live Streaming”
  • “All Audiences”
  • “Younger Teens”
  • “Teens”
  • “Adults”
  • “Not Yet Rated”

Generated files will no longer populate these values in the column. Line Item file entries for YouTube & partners line items using these configurations will fail on upload.

To avoid any interruption of service, remove any impacted targeting from YouTube & partners line items using the UI or Structured Data Files upload.

Sunset of Oracle first- and third-party audiences

On September 30, 2024, first- and third-party audiences sourced from Oracle will sunset. Once sunset, these audiences will be removed from any resource targeting and combined audiences. This update will automatically pause any line items that target only sunset audiences, or negatively target any sunset audiences.

You can identify sunsetting third-party audiences in the UI as third-party audiences from providers “Bluekai”, “Datalogix”, and “AddThis”. If you have an external account link with Oracle to import audiences from their platform, check with your relevant team to identify sunsetting first-party audiences. These audiences can’t be easily identified using the Display & Video 360 API.

In the Display & Video 360 API, TARGETING_TYPE_AUDIENCE_GROUP AssignedTargetingOptions will be updated to remove sunset audiences. Requests to add sunset audiences to resource targeting will return a 400 error.

In Structured Data Files, IDs of sunset audiences will no longer be included in “Audience Targeting - Include” or “Audience Targeting - Exclude” columns in Insertion Order, Line Item, and YouTube Ad Group files, as well as the “Bid Multiplier” column in Line Item files. File entries using sunset audience IDs in these columns will fail on upload.

To avoid any interruption of service, review the audiences used in your resource targeting, identify any Oracle audiences, and remove them. If you cache audience ID, make sure to remove any of these audiences from your cache.

Ineligibility of Optimized Targeting for certain bid strategies

On September 30, 2024, line items using the following bid strategies will no longer be able to use optimized targeting:

  • Maximum views with in-view time over 10 seconds
  • Maximum completed in-view and audible views
  • Maximum viewable impressions
  • Target viewable CPM

At this time, line items that use one of these bid strategies combined with optimized targeting will be updated to turn off optimized targeting.

In the Display & Video 360 API, LineItem resources with targetingExpansion.enableOptimizedTargeting set to True and bidStrategy.maximizeSpendAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_CIVA, BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_IVO_TEN, or BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_AV_VIEWED or bidStrategy.performanceGoalAutoBid.performanceGoalType set to BIDDING_STRATEGY_PERFORMANCE_GOAL_TYPE_VIEWABLE_CPM will be updated to set targetingExpansion.enableOptimizedTargeting to False. Requests creating or updating LineItem resources with any of these sunset configurations will return a 400 error.

In Structured Data Files, Line Item file entries with either “Optimized vCPM” in the “Bid Strategy Type” column or a combination of “Maximum” in the “Bid Strategy Type” column and “CIVA”, “IVO_TEN”, or “AV_VIEWED” in the “Bid Strategy Unit” column will be updated, if needed, to set the “Optimized Targeting” column to False. Line Item file entries using the sunset configurations will fail on upload.

To avoid any interruption of service, update and verify that your line items using these bid strategies don’t have optimized targeting turned on.

Sunset of “Flight ASAP” pacing for insertion orders

On November 5, 2024, “Flight ASAP” pacing will sunset for insertion orders. All existing Insertion Orders with “Flight ASAP” pacing will be updated to “Flight Ahead” pacing.

In the Display & Video 360 API, InsertionOrder resources with a pacing.pacingPeriod of PACING_PERIOD_FLIGHT and a pacing.pacingType of PACING_TYPE_ASAP will be updated to use a pacing.pacingType of PACING_TYPE_AHEAD. Requests creating or updating InsertionOrder resources with this configuration will return a 400 error.

In Structured Data Files, Insertion Order file entries with “Flight” and “ASAP” values in “Pacing” and “Pacing Rate” columns, respectively, will be updated to an “Ahead” value in the “Pacing Rate” column. Insertion Order file entries using the sunset configuration will fail on upload.

To avoid any interruption of service, update the pacing of any existing insertion orders currently using the “Flight ASAP” configuration.

If you run into issues or have questions about these changes, please contact us using our new Display & Video 360 API Technical support contact form.

- Trevor Mulchay, Display & Video 360 API Team

Gemini (gemini.google.com) now shows related content links in its responses

What’s changing 

Starting today, you can access additional information on topics directly in Gemini’s (gemini.google.com) responses to your prompts. Specifically, you’ll see links to related content in responses to fact-seeking prompts — you can click the arrow chips to dive deeper into the topic. If you have a Gemini for Workspace license and Google Workspace extensions in Gemini are enabled, Gemini will also now include inline links to relevant emails referenced in responses where the Gmail extension is used. 


Including this information offers another easy way to dig deeper into Gemini’s responses. You can also use Gemini’s double-check feature to verify responses by using Google Search to highlight which statements are corroborated or contradicted on the web.


Additional details

  • At this time, this feature is limited to English prompts only.
  • This feature is available in most countries where Gemini (gemini.google.com) is available

Getting started

Rollout pace


Availability

  • Available to any Google Workspace users with access to gemini.google.com.
  • Users with a Gemini Business, Enterprise, Education, Education Premium add-on license will see Gmail citations if Google Workspace extensions in Gemini are enabled by their admin.