Google Advertising and Measurement Developer Blog

The Google Ads Developer Blog is moving!

2026-11-10T00:00:00Z

Today we're announcing the move of the Google Ads Developer Blog from Blogger to the Google for Developers platform, where it will be joining the Google Advertising and Measurement Developers Hub and be known as the Google Advertising and Measurement Developer Blog.

You're probably already familiar with this platform: it's where we host guides and reference documentation for our various products. While this move will give our blog a new look, improved formatting, and additional features such as clearer tagging and curated product pages, it won't change the content. In fact, it will make it easier for you to get the information you need about the products you use.

Starting November 11, 2026:

Our current Blogger homepage, ads-developers.googleblog.com, will redirect to our new site at developers.google.com/ads/blog.
Any blog post published on or after January 1, 2024, and any Blogger label page updated since that date will automatically redirect to its migrated version on the new platform.
All new blog posts will be published solely on developers.google.com/ads/blog, with the most recent post available at developers.google.com/ads/blog/latest.

Any blog posts published before 2024 will continue to be hosted solely on Blogger. These posts won't be included in any feeds on the new platform, but will be listed in reverse chronological order on our archive page and available directly using the URL.

If you receive our content using RSS, point your RSS reader to our new feed at developers.google.com/ads/blog/rss.xml. This new feed contains the most recent 25 posts and doesn't support product-specific feeds. While blog updates will be reflected only in our new RSS feed after November 10, the existing feed will continue to be accessible to avoid breaking existing integrations.

After 15 years of the Google Ads Developer Blog on Blogger, we know that our dedicated readers and developers are accustomed to how they hear from us. Our priority with this migration is to make a better experience for you, and we intend to continue updating our blog with that in mind. If you have any questions, suggestions, or concerns, feel free to reach out to us on the "Google Advertising and Measurement Community" Discord server. We have created a temporary channel, #ads-developer-blog, for this discussion. It will be available for the next few weeks.

Display targeting changes in Demand Gen campaigns starting the week of December 1, 2026

2026-11-09T00:00:00Z

Starting the week of December 1, 2026, campaign-level Display targeting (network_settings.target_content_network) will default to enabled (true) for newly created Demand Gen campaigns. Display network targeting will be managed directly at the ad group level using channel controls (demand_gen_ad_group_settings.channel_controls.selected_channels.display) and channel strategies. Overall default campaign serving behavior will remain unchanged.

You will no longer be able to disable Display targeting for Demand Gen campaigns at the campaign level by setting network_settings.target_content_network to false. Setting this field during campaign creation or update will result in an OPERATION_NOT_PERMITTED_FOR_CONTEXT error.

Previously, disabling Display targeting at the campaign level overrode the Display targeting setting at the ad group level. Managing Display targeting exclusively at the ad group level eliminates this dual-level configuration, ensuring consistent channel representation across the Google Ads API, Google Ads UI, and Google Ads Editor.

Overview of changes and backfill

Default value alignment: When you create new Demand Gen campaigns without explicitly specifying target_content_network, the default value changes from false to true. Because ad group-level channel controls default to turning off Display targeting, the overall default targeting behavior remains unchanged (targeting owned and operated inventory unless explicitly opted in).
Existing campaign backfill: Existing campaigns currently set to target_content_network = false will be updated to target_content_network = true alongside automatic transformations applied to their ad groups:
- No-op ad groups: Where Display is opted out at both campaign and ad group levels, target_content_network is updated to true with no ad group changes required.
- Channel strategy pushdown: Ad groups using the ALL_CHANNELS strategy will be updated to ALL_OWNED_AND_OPERATED_CHANNELS.
- Channel control pushdown: Ad groups targeting Display alongside other channels will have their selected_channels.display field set explicitly to false.
- Unservable corner case: Ad groups that only target Display (while Display was opted out at campaign level) will have their status updated to PAUSED, preserving their non-serving status while leaving channel controls intact. This is because Demand Gen ad groups must target at least one channel, so turning off Display would leave them with no active channels, which is an invalid configuration.

None of the existing campaigns being backfilled will change their serving behavior, as the impacted campaigns are already opted out of Display.

How to manage Display targeting in the Google Ads API

Display targeting is now controlled at the ad group level using channel_controls.selected_channels. The following example shows how to configure or opt out of Display targeting during ad group creation or updates in the Google Ads API.

Example: Manage Ad Group Channel Controls

{
  "adGroup": {
    "resourceName": "customers/1234567890/adGroups/9876543210",
    "status": "ENABLED",
    "demandGenAdGroupSettings": {
      "channelControls": {
        "selectedChannels": {
          "youtubeInStream": false,
          "youtubeInFeed": false,
          "youtubeShorts": true,
          "discover": false,
          "gmail": false,
          "display": false
        }
      }
    }
  }
}

You can also set the channel_strategy field to ALL_OWNED_AND_OPERATED_CHANNELS as a high-level way to opt out of Display without having to explicitly enumerate every individual channel.

Recommended actions

Review campaign creation payloads: Verify API integrations and automated workflows for campaign creation. Update your application to rely on ad group channel controls (channel_controls.selected_channels.display) rather than campaign-level network_settings.target_content_network flags.
Audit existing campaigns: Check ad group channel configurations for Demand Gen campaigns to confirm that ad group channel selections accurately reflect intended channel reach:

SELECT
  campaign.id,
  campaign.advertising_channel_type,
  campaign.network_settings.target_content_network,
  ad_group.id,
  ad_group.status,
  ad_group.demand_gen_ad_group_settings.channel_controls.channel_config,
  ad_group.demand_gen_ad_group_settings.channel_controls.channel_strategy,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.youtube_in_feed,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.youtube_in_stream,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.youtube_shorts,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.discover,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.display,
  ad_group.demand_gen_ad_group_settings.channel_controls.selected_channels.gmail
FROM ad_group
WHERE
  campaign.advertising_channel_type = 'DEMAND_GEN'

If you have any questions or want to discuss this change, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Prepare for CocoaPods read-only mode: Migrate your iOS apps to Swift Package Manager

2026-11-06T00:00:00Z

On December 2, 2026, the CocoaPods Specs repository will permanently transition to read-only mode. As a result, we will no longer publish new versions of the Google Mobile Ads SDK or mediation adapters for iOS to CocoaPods after this date.

What this means for your iOS apps

If you currently use CocoaPods to install the Google Mobile Ads SDK (Google-Mobile-Ads-SDK) or User Messaging Platform SDK (GoogleUserMessagingPlatform), keep the following in mind:

Existing builds are not affected: All previously published versions of the Google Mobile Ads SDK and mediation adapters on CocoaPods will remain available in the read-only specs repository.
No future updates on CocoaPods: After December 2, 2026, new SDK releases, features, and bug fixes will only be distributed through Swift Package Manager and manual downloads.

Migrate to Swift Package Manager

To keep receiving the latest Google Mobile Ads SDK updates, we recommend migrating your iOS projects to Swift Package Manager (SPM). SPM is Apple's first-party dependency manager built directly into Xcode.

To switch your project to Swift Package Manager, follow these steps:

If you are removing CocoaPods from your project completely, run pod deintegrate in your project directory.
In Xcode, navigate to File > Add Package Dependencies....
In the search bar, enter the Google Mobile Ads Swift Package GitHub repository URL: https://github.com/googleads/swift-package-manager-google-mobile-ads.git
Select the version rule you want to use. We recommend Up to Next Major Version.
Add the package to your target.

For full setup instructions, including how to download the frameworks manually, see the Get Started guides for AdMob and Ad Manager. If you use mediation, you can migrate your adapters the same way. Google Mobile Ads mediation adapters support Swift Package Manager, and you can find each adapter's package URL in our mediation documentation.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Data Manager API now supports Google Ads call conversions and row-level diagnostics

2026-11-04T00:00:00Z

The latest release of the Data Manager API adds support for Google Ads call conversions. It also adds row-level details to diagnostics to help you find and fix the exact records that had problems during processing.

Send call conversions to Google Ads

You can now use the Data Manager API to send call conversions to Google Ads. Call conversions track when your ads lead to phone calls and when those calls lead to valuable customer actions.

To send a call conversion, set the new call_info field on the event. Its start_timestamp holds the time the phone call started. Identify the caller with a hashed phone number in user_data.

Row-level errors and warnings in diagnostics

A successful ingestion request doesn't guarantee that every record was processed. The Data Manager API now tells you which records had problems during processing. When you check request status and diagnostics for a request, each ErrorCount and WarningCount now includes a record_indices field. This field lists the 0-based positions of the affected records in your original request.

For example, a record_indices value of [0, 3] on an ErrorCount with reason PROCESSING_ERROR_REASON_CLICK_NOT_FOUND means the first and fourth events in your request failed for that reason. Use these indexes with the error reason to correct the failed records and resend them. Records with warnings weren't rejected, but some of their data was ignored, so fix the cause of the warning in future requests.

Send lead IDs with your conversions

Use the new lead_id field in ad_identifiers to send the Google-generated ID that's issued when a user submits a lead form. You can include lead_id and the existing match_id field as event identifiers for offline and multi-source events sent to Google Ads, Floodlight, and Google Analytics destinations.

Attribution using lead_id and match_id isn't available yet. Until it is, include other identifiers to ensure events are attributed.

Get started

Start sending call conversions:
- Send call conversions
- Upgrade call conversions from the Google Ads API
See Check affected records in the diagnostics guide to learn how to use record_indices.
Review the release notes for the full list of changes.

Building with AI coding tools? Explore the Data Manager API agent skills to get more accurate, efficient guidance directly in your AI-assisted coding environment.

If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server. You can also contact us through the support page if you have an issue or need help with the API.

If you're interested in becoming a data partner, please fill out the Partner Interest Form.

Upcoming changes to multi-party approvals in the Google Ads API

2026-11-04T00:00:00Z

Earlier this year, the Google Ads API started requiring multi-party approvals (MPA) when performing sensitive API actions. Starting the week of December 7, 2026, we are introducing additional changes to improve the developer experience for multi-party approvals.

What's changing?

Deferred access invitation creation: If a multi-party approval is required, the CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation method will defer the creation of the access invitation resource until the multi-party approval request is approved. The resource_name field is not populated in such cases. Once the pending MPA request is approved, the access invitation resource is available from the review results. Currently, this method creates the invitation and returns the resource_name of the invitation, but doesn't perform additional actions like sending an invitation email until the associated MPA request is approved.

New error code for stale requests: We will start returning a new MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST error code in the partial failure field when a pending MPA request is no longer valid because the target resource was modified or deleted after the review was created. This error code will be introduced in the upcoming v26.2 release. Older API versions (v23 through v25) will return a MultiPartyAuthReviewError.UNKNOWN error, and the unpublished_error_code field in GoogleAdsError.details will be set to MultiPartyAuthReviewError.STALE_MULTI_PARTY_AUTH_REQUEST.

Increased limits for MPA reviews: You can resolve up to 100 pending MPA reviews in a single call to the MultiPartyAuthReviewService.ResolveMultiPartyAuthReview method. Currently, this method is limited to one review per API call.

Action required

If you use multi-party approvals, review and update your code to reflect the new API behavior before December 7, 2026. If you are using v26 of the Google Ads API, download the latest client libraries after v26.2 is released to get support for the new STALE_MULTI_PARTY_AUTH_REQUEST error code. Refer to our technical guides to learn more about multi-party approvals. For technical support issues, reach out to Google Ads API support. If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server.

Announcing beta launch of Display & Video 360 API v5

2026-10-22T00:00:00Z

We're pleased to announce that Display & Video 360 API v5 is available in public beta starting today.

Here is a subset of changes introduced in v5:

Full management of advertiser-level YouTube video and channel exclusion targeting.
Support for Digital Out of Home InsertionOrder resources.
Updated Inventory Source retrieval and targeting.
Refactored audience targeting for Demand Gen and YouTube AdGroup resources.
Removal of Customer Match audience management features in favor of upgrading to use Data Manager API.

More detailed information about this release can be found in our release notes. Follow the steps in our migration guide to migrate from v4 to v5. Be aware that breaking changes may be made to v5 while in beta, and any such changes will be listed in the Display & Video 360 API release notes.

Before using new features, make sure to update your client library to the latest version.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Upcoming changes to image extraction in Performance Max campaigns starting December 4, 2026

2026-10-21T00:00:00Z

Starting December 4, 2026, image extraction (GENERATE_IMAGE_EXTRACTION) will be enabled by default (OPTED_IN) for newly created Performance Max campaigns across Google Ads interfaces, including the Google Ads API, Google Ads UI, and Google Ads Editor. Crucially, this new campaign-level default applies even if Dynamic Image Extensions are disabled at the account level (isImageExtractionAdExtensionEnabled). Previously, campaigns left unset inherited their status from this account-level setting.

With image extraction, Google AI scans provided landing pages for high-resolution images to enrich creative assets and expand reach across Search, YouTube, Display, Discover, Gmail, and Maps. Existing Performance Max campaigns will retain their current configurations, but developers relying on account-level controls should explicitly set OPTED_OUT on new campaigns if they do not want image extraction enabled.

How to manage image extraction in the Google Ads API

Image extraction is managed at the campaign level through the asset_automation_settings field on the Campaign resource:

Automation Type: AssetAutomationType.GENERATE_IMAGE_EXTRACTION
Status: AssetAutomationStatus.OPTED_IN or AssetAutomationStatus.OPTED_OUT

Example: Explicitly opting out during campaign creation

If your integration or clients prefer not to extract images from landing pages on new campaigns, you can explicitly set GENERATE_IMAGE_EXTRACTION to OPTED_OUT in your campaign mutate request. An example of how this would look using REST JSON is as follows:

{
  "name": "My Performance Max Campaign",
  "advertisingChannelType": "PERFORMANCE_MAX",
  "status": "PAUSED",
  "assetAutomationSettings": [
    {
      "assetAutomationType": "GENERATE_IMAGE_EXTRACTION",
      "assetAutomationStatus": "OPTED_OUT"
    }
  ]
}

To change the setting on an existing campaign, send a CampaignOperation update targeting campaign.asset_automation_settings. Note that asset_automation_settings is a repeated field. When updating a campaign, providing new settings replaces the entire array rather than merging with existing values. Be sure to retrieve and include all other desired AssetAutomationSetting entries (such as TEXT_ASSET_AUTOMATION) in your update request to avoid unintentionally clearing them.

Example: Auditing existing campaigns

To check the current automation settings across your Performance Max campaigns, you can query asset_automation_settings using Google Ads Query Language (GAQL):

SELECT
  campaign.id,
  campaign.name,
  campaign.asset_automation_settings
FROM campaign
WHERE campaign.advertising_channel_type = 'PERFORMANCE_MAX'

If a campaign does not have an entry for GENERATE_IMAGE_EXTRACTION, it is currently relying on the inherited account-level setting. You can check or toggle the account-wide Dynamic Image Extension setting directly in the Google Ads UI:

Navigate to Campaigns > Assets
Click the three-dot More menu > Account-level automated assets
Click the three-dot menu again > Advanced settings
Check whether Dynamic images is turned On or Off

Recommended actions

Review New Campaign Creation Workflows:
- If you want image extraction enabled: No action is needed. New Performance Max campaigns created after December 4, 2026 will automatically have image extraction enabled by default.
- If you prefer to opt out: Update your campaign creation payloads before December 4, 2026 to explicitly include GENERATE_IMAGE_EXTRACTION with asset_automation_status = OPTED_OUT.
Review Landing Page Media Rights:
- As with all automated asset features, confirm that you own all legal rights or permissions to the images published on your landing pages and allow Google to utilize them for commercial and advertising purposes.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Announcing v26 of the Google Ads API

2026-10-14T00:00:00Z

Today we are announcing the release of v26 of the Google Ads API. To use the new capabilities, you must upgrade your client libraries and client code. We've published all updated client libraries and code examples.

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord or our Ads Developers YouTube Live tomorrow (October 15 at 10:00 AM ET). We'll also record the walkthrough and post it on YouTube if you can't attend live.

New features

Here are the highlights of what's new in v26:

Streamlined EU political advertising declarations: Campaign.contains_eu_political_advertising is now optional for campaigns and Demand Gen ad groups with upgraded targeting that positively target only locations outside the European Union and contain no proximity or location group criteria. You can check whether a declaration is required using the new require_eu_political_advertising_declaration field on GeoTargetConstant, CampaignCriterion, and AdGroupCriterion.

Vertical-agnostic travel bid modifiers: We've renamed hotel-specific AdGroupBidModifier criteria to apply consistently across travel verticals: user_set_dates (replacing hotel_date_selection_type), advance_booking_window (replacing hotel_advance_booking_window), length_of_booking with min_days and max_days (replacing hotel_length_of_stay), start_day_of_week (replacing hotel_check_in_day), and start_date_range (replacing hotel_check_in_date_range).
Search Lift measurements: We've expanded lift measurement capabilities with support for Search Lift studies. You can now query the new read-only SearchLiftKeywordBundle resource and segment by segments.search_lift_keyword_bundle and segments.search_property. You can also analyze 15 new Search Lift metrics (including relative_search_lift, normalized_incremental_searches, and search_lift_impressions) alongside Campaign.lift_measurement_config.
Local Services Performance Max campaign creation: You can now create Google Local Services Performance Max campaigns with the API by setting PmaxCampaignSettings.local_services_enabled (which is now settable on creation and immutable afterwards) and providing the required country_code and Google Business Profile listing_id in LocalServicesPmaxCampaignSettings. We've also added support for linking leads to campaigns, coupon lead type, and message lead conversion category.
Unified enhanced conversions configuration: We have added Customer.enablement_setting and Customer.effective_enablement_setting to expose the unified enhanced conversions configuration for the account, replacing Customer.enhanced_conversions_for_leads_enabled.
Shopping and Demand Gen enhancements: We've expanded Campaign.listing_type support to Shopping campaigns. CurrencyConstant now exposes the minimum budget per day for a Demand Gen campaign in a given currency.

Reminder: changes to release cadence

As announced on October 12, 2026, Google Ads API is moving to two releases per month starting with v26. This faster cadence gives your automated agents and workflows earlier access to new Google Ads features. Our release blog posts and YouTube live events will move to twice a quarter, covering key updates across several releases at once. To follow individual releases, add the Google Ads API release notes to your saved pages to receive notifications whenever they change.

Getting started

If you use our client libraries, download the latest version of your client library to start using these features. Review the official release notes for a full list of changes. If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server.

For technical support issues, reach out to the Google Ads API support channel.

Google Ads API Release and Sunset Schedules for 2026-2027

2026-10-12T00:00:00Z

Last year, we shifted to a monthly release schedule for the Google Ads API to provide you faster API access to Ads features available in the Google Ads UI. As we enter a new agentic era where speed and agility are paramount, we are thrilled to accelerate our launch timelines even further - moving to two Google Ads API releases per month starting from version v26! This faster cadence gives your automated agents and workflows near-instant access to cutting-edge features, allowing you to stay ahead of the curve, reduce time-to-market, and innovate with unprecedented efficiency.

We will still ship four major releases per year. All other releases will be minor releases that add only new, non-breaking features. Each major release will still be available for one year after the release. Sunset schedules are also unchanged, so you will not need to migrate more often. Each minor release sunsets together with its parent major version.

Our release blog posts and YouTube live events will move to twice a quarter, covering key updates across several releases at once. To follow individual releases, add the Google Ads API release notes to your saved pages and you will be notified whenever they change.

Release schedule for 2026-2027

The following table shows the tentative release schedule for the rest of 2026 and for 2027. These dates are estimates and may change. We may also add or remove releases, or switch a release between major and minor.

Version	Release type	Projected launch *	Projected sunset *
v26	Major	October 2026	November 2027
v26.1	Minor	October 2026	November 2027
v26.2	Minor	November 2026	November 2027
v26.3 **	Minor	December 2026	November 2027
v27	Major	January 2027	February 2028
v27.1	Minor	February 2027	February 2028
v27.2	Minor	February 2027	February 2028
v27.3	Minor	March 2027	February 2028
v27.4 ***	Minor	March 2027	February 2028
v28	Major	April 2027	May 2028
v28.1	Minor	April 2027	May 2028
v28.2	Minor	May 2027	May 2028
v28.3	Minor	May 2027	May 2028
v28.4	Minor	June 2027	May 2028
v28.5	Minor	June 2027	May 2028
v29	Major	July 2027	August 2028
v29.1	Minor	July 2027	August 2028
v29.2	Minor	August 2027	August 2028
v29.3	Minor	August 2027	August 2028
v29.4	Minor	September 2027	August 2028
v29.5	Minor	September 2027	August 2028
v30	Major	October 2027	November 2028
v30.1	Minor	October 2027	November 2028
v30.2	Minor	November 2027	November 2028
v30.3 **	Minor	December 2027	November 2028

* Estimated and subject to change.

** We may skip this release because it falls during the holiday season.

*** v27 has fewer minor version releases because it falls during the holiday season (January)

Sunset schedule for 2027

The following is the tentative sunset schedule for 2027. As with the release schedule, these dates are estimates and may change. The minor versions (e.g., v23.x) sunset with their parent major version (e.g. v23).

Version	Projected sunset*
v23	February 2027
v24	May 2027
v25	August 2027
v26	November 2027

* Estimated and subject to change.

Learn more and get help

As always, you can find the details of individual releases at the following pages.

If you have any questions or want to discuss this post, join the conversation on our "Google Advertising and Measurement Community" Discord server.

For technical support issues, please reach out to the Google Ads API support channel.

Launching Structured Data Files v11

2026-10-08T00:00:00Z

Today we're announcing the general availability of Structured Data Files v11. All users can now use v11 when downloading and uploading SDFs in the Display & Video 360 interface.

SDF v11 includes the following changes:

Expanded the availability of Lookalike audience inclusion and exclusion targeting to all ad groups except for those under YouTube Ad Sequence line items.
Added support for Business Chain proximity targeting to the line item file format.
Updated the format of four existing YouTube third-party vendor columns in the line item file format to incorporate reporting IDs and support multiple vendor assignments. The related YouTube third-party vendor reporting ID columns, now redundant, have been removed.
Added new columns, column options, and column restrictions to support YouTube Instant Deal line items, their ad groups, and their ads. Support for YouTube Instant Deals is in beta and only available to allowlisted partners. YouTube Instant Deal line items and the ad groups and ads under them will not be included in any downloaded files and can only be uploaded through the YouTube Instant Deal creation workflow of the Display & Video 360 interface.

See the release notes for the details on the changes in v11. Please be aware that if you are using a version earlier than v10, you are using a deprecated version that will sunset in January 2027. Follow the instructions in our migration guide to migrate to v11 from any available version.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Announcing v25.2 of the Google Ads API

2026-09-23T00:00:00Z

Today we are announcing the release of v25.2 of the Google Ads API. To use the new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

Come join us for a live walkthrough of this release in our Google Ads API Release Highlights event on Discord or our Ads Developers YouTube Live tomorrow (September 24th at 10am ET). This will also be recorded and posted on YouTube for those who can't make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

New Features

Here are the highlights of what's new in v25.2:

Competitive benchmarks percentile metrics: BenchmarksService.GenerateBenchmarksMetrics now surfaces metrics representing your competitive standing among other advertisers in percentile tier format using PercentileMetrics and BenchmarksCustomerPercentileTier. You can request this data by adding PERCENTILE_DATA to supplemental_data, setting benchmarks_source to ALL_ADVERTISERS and specifying the category_filter.
Generate Performance Max drafts from Smart campaigns: The new SmartCampaignSettingService.GeneratePMaxDraftCampaign method allows you to programmatically generate a Performance Max draft campaign directly from an existing Smart campaign, simplifying your campaign upgrade workflows.
Asset group URL options: You can now configure tracking templates (tracking_url_template), custom parameters (url_custom_parameters), and final URL suffixes (final_url_suffix) directly at the asset group level on AssetGroup for Performance Max campaigns.
Creator insights by YouTube channel handles: ContentCreatorInsightsService.GenerateCreatorInsights now supports searching directly by YouTube channel handles in addition to channel IDs, streamlining your creator discovery process.
Vertical ads itinerary dimensions and price competitiveness: For hotel and travel advertisers, we've added new itinerary dimension segments (advance_booking_window, length_of_booking, start_date, start_day_of_week, user_set_dates) along with new vertical ads metrics metrics and segments such as vertical_ads_price_difference_percentage, vertical_ads_price_tier and vertical_ads_potential_impressions.
Search bid adjustment recommendations: New recommendations (raise_target_cpa_performance_bid_too_low_recommendation and lower_target_roas_performance_bid_too_low_recommendation) notify you when Target CPA or Target ROAS bids are too low for Search campaigns to enter auctions.

Getting started

Google Ads API v25.2 is a drop-in upgrade for v25. If you use our client libraries, download the latest version of your client library to start using these features. Review the official release notes for a full list of changes. If you have any questions or want to discuss this post, reach out to us on our Google Advertising and Measurement Community Discord server.

For technical support issues, please reach out to the Google Ads API support channel.

A new onboarding experience for Google Ads API developers

2026-09-10T00:00:00Z

To improve the developer onboarding and usage experience, we built a new homepage for the Google Ads API in the Google Cloud Console. Basic Access applications are now automated for developers who have completed brand verification. This blog post covers several related changes that will start rolling out today. Developers should review the action required section of this post to ensure a smooth transition.

Changes to API access management

We are updating how you sign up for and manage Google Ads API access.

New onboarding experience for Google Ads API: You can now sign up for access to the Google Ads API directly in the Google Cloud Console without requiring a Google Ads manager account. We are sunsetting all the new signup and API access management functionality in the API Center page in manager accounts and transitioning to the Google Ads API Overview page in Google Cloud Console. You can still access the API Center page to refer to your old developer details. This page will completely sunset in the future.

API Access levels are associated with Google Cloud projects: We are sunsetting developer tokens. Your current and active developer token access level is automatically transferred to your Google Cloud projects based on recent API activity. You can continue sending developer tokens in your API call headers, but this is optional and ignored by the API servers. Your existing code will continue working without any changes. Your API Access levels are now determined by the Google Cloud project you used to generate your OAuth credentials. Refer to our FAQ page to learn more about this change and troubleshoot any issues you may encounter.

New error code: Version v25 of the Google Ads API will throw a CLOUD_PROJECT_NOT_APPROVED_FOR_PRODUCTION error if you try to use a Google Cloud project with Test Account Access level to make calls to a production account. Older API versions will throw an ACTION_NOT_PERMITTED error instead. If you run into this error, navigate to the Google Ads API Overview page for your Google Cloud project and apply for Explorer Access.

Changes to API review process

Brand verification required for Basic and Standard access: For new Basic and Standard Access applications, you must complete brand verification for your Google Cloud project . Existing access holders are not required to complete brand verification, though it is encouraged.

Automated Basic access approvals: Basic Access applications are now automated and will be reviewed within minutes after brand verification and submission.

One-time rejection of pending Basic access applications: Due to these process updates, all the pending Basic API access applications will be closed as part of this transition. Affected applicants will receive an email with details and should reapply for API access from the Google Ads API Overview page.

Action required

Verify your API access: Check that your project's API access level correctly matches your existing developer token:

Find your developer token's access level in your Google Ads manager account's API Center.
Confirm your Google Cloud project has the same access level on the Google Ads API Overview page.
If the access levels do not match, please reapply for API access from the Google Ads API Overview page or reach out to the Google Ads API support if you need help.

Update your API contact email address: Visit the IAM (Identity and Access Management) page for your Cloud project. Ensure that the list of users in the owner and editor roles are up to date. We will start sending Mandatory Service Announcements (MSAs) to these email addresses to notify you about any future changes to the Google Ads API.

Code changes: We encourage you to update your application code to stop sending developer tokens as part of the API calls. We have published new versions of the client libraries which allows you to make API calls without setting a developer token. We will start rejecting developer tokens in API calls in a future major version of the Google Ads API.

Reapply for API access if applicable: If your pending Basic API access application was closed as part of this transition, please reapply for an API Access from the Google Ads API Overview page of your Google Cloud Console.

We have published updated documentation to help you navigate these changes. For technical support issues, refer to our FAQ page or reach out to Google Ads API support. If you have any questions or want to discuss this post, please reach out to us on our Google Advertising and Measurement Community Discord server.

Google Ads API v22 sunset reminder

2026-09-02T00:00:00Z

Google Ads API v22 will sunset on October 7, 2026. Starting on this date, all v22 API requests will begin to fail. Migrate to a newer version prior to October 7, 2026 to ensure your API access is unaffected.

Here are some resources to help you with the migration:

To view a list of methods and services that your project has recently called, use the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.
Click Google Ads API in the table.
On the Metrics subtab, your recent requests are plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as google.ads.googleads.v22.services.GoogleAdsService.Mutate.
(Optional) Select the timeframe for which you want to view your requests.

If you have any questions or want to discuss this post, reach out to Google Ads API support or start a discussion on our "Google Advertising and Measurement Community" Discord server.

Making Google Ads More Secure with Updates to Developer Policies

2026-08-31T00:00:00Z

We are updating our Google Ads Developer Policies formerly the "Google Ads API Policy", to support developers in building robust, high-quality integrations as new AI capabilities continue to shape the advertising industry.

These updates establish clear frameworks for emerging technologies that are more secure and drive better outcomes for our shared customers.

To ensure a seamless transition to these updated standards, the Ads API Compliance team is actively reviewing existing integrations. Please check if your application requires updates by reviewing the policy. We will also reach out directly to developers who will need to transition with detailed guidance, technical resources and additional details.

Why we are introducing these updates now

As technology evolves, we periodically review our policies to make sure they reflect the current landscape. Historically, some integrations have relied on programmatic proxies, which bypass the verifiable and secure interface between end-users and Google. To help protect advertising partners against fraud and security risks, integrations now need to connect directly to Google Ads services using their own dedicated Google Cloud project.

This is critical to mitigate risks for customers, including:

Security Vulnerabilities: Using unaudited proxies can provide unauthorized actors access to your account. They also introduce the risk of cross-tenant data leaks, which could expose your data more broadly than intended.
Performance Bottlenecks: High-volume traffic routed through a single proxy can throttle throughput, cause latency across all users, and require enforcement across all users of a proxy when mitigating localized Denial of Service (DoS).

Next steps

Review your integrations to ensure they still follow Google Ads API policies. For full guidelines, visit the updated Google Ads Developer Policies.
Please ensure your contact email is up to date in the API Center so our Ads API Compliance team can easily share helpful communication or direct assistance from our compliance team as we do reviews. These communications will come from the google.com domain.

For technical support issues, please reach out to Google Ads Developer Support.

October 2026 changes to the Display & Video 360 API and Structured Data Files

2026-08-27T00:00:00Z

Today we're announcing three unversioned changes to the Display & Video 360 API and Structured Data Files that will take effect in October 2026 and may impact your existing integrations.

These changes will take place on the following dates and have been fully detailed on our Announced Deprecations page:

Starting October 1, 2026:

You will no longer be able to exclude specific digital content labels using targeting, impacting available TARGETING_TYPE_DIGITAL_CONTENT_LABEL_EXCLUSION targeting options in the Display & Video 360 API and valid values for the Digital Content Labels - Exclude column in Line Item Structured Data Files.
You will no longer be able to exclude the majority of sensitive categories using targeting, impacting available TARGETING_TYPE_SENSITIVE_CATEGORY_EXCLUSION targeting options in the Display & Video 360 API and valid values for the Brand Safety Sensitivity Setting and Brand Safety Custom Settings columns in Line Item Structured Data Files.

Starting October 12, 2026:

You will be required to provide a business name and logo when you create or update YouTube responsive ads if default values are not already assigned to the parent advertiser, impacting the upload of Ad Structured Data Files.

If you believe these changes will impact your integration, follow the recommended actions in the change description.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Google Ads API Developer Assistant v4.0.0

2026-08-25T00:00:00Z

A major release of the Google Ads API Developer Assistant is now available. This release transitions the assistant from a standalone project setup to a unified plugin architecture designed to bring specialized Google Ads API capabilities directly into AI agent workflows.

What is it?

The Google Ads API Developer Assistant brings deep Google Ads domain expertise into AI coding environments like Antigravity and Claude Code. It equips your AI assistant with specialized tools and guardrails. Functions include:

Generate idiomatic code: Create tested, best-practice integration code across Python, Java, PHP, .NET, and Ruby.
Validate GAQL queries: Automatically verifies syntax, field compatibility, date segmentation, and zero-impression rules before running queries.
Inspect Protobuf schemas: On demand discovery of resource fields, data types, and enum definitions for any active Google Ads API version to ensure that GAQL query fields are valid.
Troubleshoot API issues: Diagnose offline conversion upload failures, navigate manager account hierarchies, and construct Performance Max listing filters. You can pose natural language questions like "Show me all the ads in my account with problems and recommend how to fix them."
Answer API questions: The assistant answers questions by combining embedded Google Ads API architectural rules with dynamic, local Protobuf schema inspection to deliver version-accurate guidance and verified code snippets. It grounds its responses directly in official API definitions and client library source code rather than relying solely on general model training. An example question might be, "What is a shared set and how do I use it?"
Adhoc reporting: You can ask for performance data in plain English, and the assistant instantly constructs, validates, and runs the required GAQL queries directly against your Google Ads account. It streams live results back into your chat as clean, formatted tables, making ad hoc reporting and metric investigations effortless. If you want to save the results, ask it to "Save results as a CSV file in <your directory>" and you can load it into a spreadsheet for analysis.

Support for Antigravity and Claude Code

This release introduces dual-platform support:

Antigravity: Native support for Antigravity developer environments with global and workspace plugin registration.
Claude Code: Full integration with the Claude Code CLI plugin system, including custom slash commands (such as /validate-gaql, /inspect-object, /troubleshoot-conversions, and /get-cids).

Unified installation scripts are available for Linux, macOS (bash), and Windows (PowerShell) to provide consistent lifecycle management across all three platforms.

Improved performance

Reduced token consumption: Progressive disclosure of rules and schemas loads only the context needed for a given task, reducing prompt token overhead.
Faster response times: On-demand skill execution and targeted command routing deliver faster end-to-end task completion.
Lower CPU utilization: Streamlined execution pipelines eliminate background process overhead during development sessions.
Reduced disk I/O: Reducing the number of unneeded files in the plugin tree prevents file watchers, linters, and IDE indexers from scanning tens of thousands of unused protobuf/SDK files.
Lower memory (RAM) footprint & zero daemon overhead: Skills and commands now run ephemerally as fast child processes only when called, dropping system resource usage to zero when idle.
Cached API version and Protobuf schema resolution: The assistant avoids making repetitive remote metadata or reflection API calls when inspecting standard fields, resources, and enums.
Deterministic command execution versus multi-turn LLM reasoning: Instead of the LLM guessing or iteratively debugging GAQL syntax across 3–4 round-trips, the local validator checks fields, resources, zero-impression metrics, and date clauses in a single step.

A major release built on a modern plugin architecture

This is a major release that is not compatible with prior releases. Earlier versions relied on a local workspace project structure. This version is built on a standardized plugin architecture that is installed to be globally available.

Modularizing rules, skills, and diagnostic commands into a self-contained plugin bundle allows developers to install, update, and manage the assistant across multiple environments and projects.

See the README.md for technical details on the plugin architecture.

Getting started

Because of the architectural changes in this release, review the documentation before installation:

Read README_BEFORE_INSTALLATION.md for prerequisites and environment preparation.
Follow the installation instructions in README.md.

We want your feedback

Share your feedback, report issues, and suggest capabilities using the survey form:

👉 Submit your feedback

Announcing v25.1 of the Google Ads API

2026-08-19T00:00:00Z

Today we are announcing the release of v25.1 of the Google Ads API. To use the new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord or our Ads Developers YouTube Live tomorrow (August 20th at 10am ET). This will also be recorded and posted on YouTube for those who can't make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

New Features

Here are the highlights of what's new in v25.1:

Conversion lift and brand lift measurement: We've added comprehensive support for lift studies in the API. Read-only resources LiftMeasurementConfig and LiftMeasurementFlight allow you to inspect study configurations, flight dates, campaign details, and conversion goals. This release includes 24 new Conversion Lift metrics and winner score metrics for statistical analysis, as well as new Brand Lift dimension resources: LiftMeasurementAgeRange, LiftMeasurementCampaign, LiftMeasurementDevice, LiftMeasurementGender, and LiftMeasurementVideo. Refer to our help center article to learn more about Brand lift and Conversion lift. Both these features are available only to allowlisted Google Ads accounts. To use these features, contact your Google account representative.
BenchmarksService category scoping and new metrics: You can now scope your benchmark analysis against advertisers in specific Product & Service Categories using the new category_filter parameter in BenchmarksService.GenerateBenchmarksMetrics. Supported categories can be discovered via ListBenchmarksSources. In addition, new customer ad metrics (aggregate cost, views) and share metrics such as share_of_voice are now surfaced via AggregateMetrics and ShareMetrics.
Brand Sentiment Insights: ContentCreatorInsightsService now supports brand sentiment data, allowing you to retrieve sentiment distributions and summaries for creators and brands via BrandSentimentInsight.
Loyalty Program Segmentation and Conversion Value Rules: You can now segment report metrics by the loyalty program tier of converting users using Segments.loyalty_membership. Additionally, the new LOYALTY_MEMBERSHIP primary dimension in ConversionValueRulePrimaryDimension allows you to track when a loyalty membership condition was satisfied for a conversion value rule.
Original Conversion Value Metric: The new Metrics.original_conversion_value metric surfaces the unadjusted conversion value from biddable conversions before any conversion value rules or customer lifecycle goal adjustments are applied.
Parental Status Targeting in Reach Planning: ReachPlanService now supports parental_statuses targeting within Targeting and PlannableTargeting for reach forecasting and plannable product discovery.

Getting Started

Google Ads API v25.1 is a drop-in upgrade for v25. If you use our client libraries, download the latest version of your client library to start using these features. For a full list of changes, please review the official release notes. If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

For technical support issues, please reach out to the Google Ads API support channel.

Google Ads language targeting changes starting September 2026

2026-08-13T00:00:00Z

We're making changes to language targeting for Search, AI Max for Search, and Performance Max campaigns in Google Ads, simplifying campaign management while maintaining a high-quality ad experience.

Effective late September 2026:

For Search and AI Max for Search campaigns, the campaign-level language targeting setting will be removed. Search ads will automatically match based on the language of your ads.
For Performance Max campaigns, the way language targeting is used will be updated:
- On Google Search: The campaign-level language setting will no longer be used for ads shown on Google Search. Language matching will function the same as Search campaigns, using the language of your ads.
- On other channels (like YouTube, Display, Discover, Gmail): The campaign-level language setting you select will continue to be used to guide who sees your ads.

In cases where multiple eligible campaigns exist within your account, AI-based ad group prioritization will select the most relevant ad language.

Historically, the language criterion in the Google Ads API allowed you to manually specify target languages for your campaigns. These language criteria will still be returned when querying even though they are not used for targeting. Any mutates to add or update Search campaign CampaignCriterion.language will result in a ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT error. For Performance Max campaigns, there will be no error as language targeting may be used on other channels.

What should I change for the Google Ads API?

While existing Search and AI Max for Search campaigns will continue to operate without disruption (as their language settings will not apply), we recommend the following code updates:

Stop setting language criteria:
- For new Search campaigns: Stop including language criteria when creating or updating Search campaigns when sending Google Ads API requests.
- For existing Search campaigns: You may optionally remove existing language criteria from your Search campaigns for cleanliness, though it is not strictly required as they will not apply.
Focus on Ad and Landing Page Language: Ensure your ad creatives and landing pages are clearly structured in the intended languages. Search ads will primarily use these signals, alongside user language preferences, for matching.

Where can I get support?

For technical support issues, please reach out to us using the support form. If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Query report data with the Campaign Manager 360 API

2026-08-12T00:00:00Z

You can now use the reportData.query endpoint in the Campaign Manager 360 API to synchronously query your campaign performance data and retrieve structured JSON data directly in the response.

The new reportData.query endpoint offers a simplified option for report data retrieval compared to the standard reporting API workflow:

Queries run synchronously with a 60-second execution limit, making this endpoint ideal for real-time dashboards and ad-hoc data explorations.
Report data is returned as structured JSON directly in the HTTP response, which eliminates file management overhead.
You no longer need to create a preconfigured Report resource to fetch data, as you can specify your dimensions, metrics, and filters directly in the request body.

The existing Reports service is still recommended for retrieval of large datasets, scheduled jobs, or applications that rely on downloadable report files (CSV or Excel). This service requires multiple steps: developers must create and manage Report configurations, trigger a run of the report, poll for status updates, and download the report file.

Get Started

Review the Query Report Data guide to learn more about request parameters, pagination, and best practices.
Compare reporting approaches on the Reporting Overview.
Check out the reportData.query REST reference documentation.

If you have any questions or need technical support, please reach out to Campaign Manager 360 API Support.

Migrate Campaign-level Broad Match and Automatically Created Assets to AI Max

2026-08-12T00:00:00Z

The legacy automigrations are divided into two separate phases:

Phase 1 (Campaign-level Broad Match and Automatically Created Assets), which starts September 1, 2026.
Phase 2 (Dynamic Search Ads), which has been rescheduled to February 2027.

1. Campaign broad and ACA auto-migration: September 1 – September 30, 2026

On September 1, 2026, Google Ads will begin automatically upgrading Search campaigns using Campaign-level Broad Match (CB) or standalone Automatically Created Assets (ACA) to AI Max. The migration job will roll out progressively throughout the month.

To find the campaigns that have been migrated at any point during the month:

   SELECT
      campaign.id,
      campaign.name,
      campaign.aca_migration_date_time,
      campaign.broad_match_migration_date_time
    FROM campaign
    WHERE campaign.aca_migration_date_time > '1970-01-01 00:00:00'
      AND campaign.broad_match_migration_date_time > '1970-01-01 00:00:00'

Default migrated configurations

To support campaign management continuity and minimize performance volatility, campaigns will be migrated in-place to equivalent AI Max settings.

Campaign-Level Broad Match (CB):
- Text Customization (TC): OPT_OUT (OFF)
- Final URL Expansion (FUE): OPT_OUT (OFF)
- Search Term Matching (STM): true (ON) by default
- Brand Lists: Existing brand inclusions and exclusions are preserved and moved into the new setup in-place.
Standalone Automatically Created Assets (ACA):
- Text Customization (TC): OPT_IN (ON) by default
- Final URL Expansion (FUE): OPT_OUT (OFF)
- Search Term Matching (STM): true (ON) by default

2. API creation blocks and legacy cleanup

To prevent the creation of new legacy structures ahead of the auto-migration, strict enforcement blocks are now in place across the developer surfaces:

Legacy creation end of life (August 3, 2026): Creating new Campaign-level Broad Match configurations or legacy Automatically Created Assets (ACA) is now blocked across the UI, Google Ads Editor, and all versions of the API.

3. API versioning lifecycle and support grace period

How you manage these features depends on the API version your integration targets:

New API versions (post-September 1, 2026)

Any new versions of the Google Ads API released after September 1, 2026, will completely remove the legacy entities used to create or manage:

Campaign-level Broad Match settings
Automatically Created Assets

Older API versions (grace period)

Active support: Previously released API versions that are currently active will temporarily continue to support legacy ACA and Broad Match settings.
Sunset timeline: You can continue to edit and manage these legacy setups through older API versions until those specific versions reach their standard scheduled sunset (typically one year after their introduction, around September 2027). At that point, all remaining legacy entities will be permanently removed.

4. Dynamic Search Ads automigration February 2027

Your active legacy DSA campaigns are excluded from the September auto-migrations and will continue to serve as normal. However, prepare for the upcoming DSA timeline:

September 2026: Google will launch in-account pre-migration banners in the UI to warn unmigrated advertisers of the upcoming transition and encourage voluntary one-click upgrades by selecting "Upgrade Your Dynamic Search Ads (DSAs) to AI Max" under Campaign Settings | Dynamic Search Ads setting.
January 15, 2027: Official MSA reminder notification will be sent to all impacted accounts.
February 1–28, 2027: Automigration begins. The ability to create new DSA ad groups will be permanently removed, and unmigrated DSA campaigns will automatically upgrade to standard Search ad groups with AI Max enabled.

Developer action plan

Audit your integration: Identify any scripts, external tools, or client libraries still attempting to create or edit campaign-level broad match settings or legacy ACA.
Move to standard entities: Begin updating your campaign construction workflows to use standard Search campaigns with the AI Max settings bundle (Uber Toggle, Text Customization, and Search Term Matching).
Handle grandfathered read-only entities: Be prepared to handle API error codes if your integration attempts to modify (rather than pause or delete) legacy Expanded Dynamic Search ads (eDSAs) or criteria once they transition to standard ad groups.

Google Ads API pilot: Secure API Access to your Manager Accounts

2026-08-03T00:00:00Z

The Google Ads API is piloting a security feature designed for securing API access to Google Ads manager accounts. We are seeking developers who would like to participate in this pilot project and provide us with feedback.

What are we offering?

The new pilot program protects accounts under a Google Ads manager hierarchy by restricting access to sensitive API methods such as account management, user management, and billing API calls to a pre-approved allowlist of Google Cloud projects. This happens in the following phases:

You sign up for the pilot program, and share the customer ID of your top-level Google Ads manager account.
Google performs an audit of the API activity of all the accounts under the Google Ads manager account to identify the list of applications and their Google Cloud project numbers.
Google works with you to establish an allowlist of approved applications and projects as a new mechanism for controlling API access to sensitive methods.

After the Google Ads manager account is secured, any unapproved application that tries to make sensitive API calls to any account under the protected manager account will fail.

This security measure provides benefits:

Enhanced Security: Lowers the risk of account takeovers by malicious applications by helping to restrict access so that only verified tools can perform sensitive operations, even if your credentials are compromised.
Improved Visibility: Provides advertisers with a clear and concise view of exactly which applications have access to their advertising data and are performing sensitive actions on their accounts.

How do I join this program?

To participate in this program, express your interest by filling out the application form. You should provide your contact email address and the customer ID of the top-level Google Ads manager account that you want to secure. If Google selects your account for participation in the pilot program, then we will reach out to you using the email address you provided, and list the next steps required to secure the accounts under your Google Ads manager account under this pilot program.

How do I authorize new applications under this program?

If you are participating in this program and want to allowlist a new application to make sensitive API calls to the accounts under the protected Google Ads manager account, let us know the Google Cloud project number of the application by filling out the form. If you don't have these details, you can reach out to your application developer for this information. Google will make the necessary changes within 10 business days and let you know.

How do I stop participating in this program?

If you are participating in this program and want to stop your participation, contact Google Ads API support using the same email address you used when signing up for this program and let us know the reason why you are opting out of this program. Google will make the necessary changes within 10 business days and let you know.

What happens if I unlink an account from a protected top-level manager account?

If you unlink an account from the hierarchy under a protected top-level manager account the account loses the API protection offered under this program.

What happens if I link a new account under a protected top-level manager account?

If you link an account under the hierarchy of a protected top-level manager account, the newly linked account will inherit the protection from the top-level manager account. In addition, if a newly linked account has existing applications, but those applications are not already authorized by the manager account, they might fail and may need to be authorized.

If you have more questions about this pilot program, you can contact support.

Data Manager API updates: RemoveAllAudienceMembers method, ingestion field warnings, expanded address data

2026-07-30T00:00:00Z

The latest release of the Data Manager API introduces features that simplify audience management, enhance ingestion workflows with field-level warnings, and enable more granular user-provided data for Google Analytics.

Remove all audience members

Use the new RemoveAllAudienceMembers method to clear all members from specified user lists in a single operation. The optional removeAsOfTime parameter lets you target only those members added before a specific timestamp.

This is particularly useful when you need to perform a full refresh (or "replace all") of your audience data, allowing you to clear the existing list and populate it with a new set of users.

Ingestion field warnings

Data Manager API ingestion responses now include detailed field-level warnings for validation issues on optional fields. If the API detects validation issues with optional fields, your ingestion request will succeed and the rest of your ingestion data will still be processed. Validation failures for required fields will continue to fail the entire request following the fast-fail model.

If any optional field you provide is invalid, the response from IngestEventsRequest or IngestAudienceMembersRequest includes a field_warnings field with a list of FieldWarning objects. Each warning provides a specific reason (WarningReason), a descriptive message, and the location of the field in the request where the issue occurred.

Additional address data for Google Analytics events

You can now provide additional user address information when ingesting events to Google Analytics destinations. Along with the given_name, family_name, region_code, and postal_code fields, AddressInfo resource now supports:

address_line (street address)
city
administrative_area (state or province)

Also, you can now use the existing user-provided data (user_data) field to meet the Identifiers requirement for multi-source events sent to web data streams. This gives you another option when you don't have the ad_identifiers.gclid, user_id, or client_id for a multi-source event.

Get started

Learn how to implement the new RemoveAllAudienceMembers method for your workflow:
- Google Ads Customer Match
- Display & Video 360 Customer Match
See the Ingestion warnings section of the Understand API errors guide to learn how to check your responses for warnings.
Start sending events to Google Analytics with the Data Manager API:

Build faster with AI agent skills: We recently introduced new Data Manager API agent skills to help you speed up your integrations. Explore the new skills in the Google Skills GitHub repository to get more accurate, efficient guidance directly within your AI-assisted coding environment.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server. You can also contact us through the support page if you have an issue or need help with the API.

If you're interested in becoming a data partner, please fill out the Partner Interest Form.

Launching Structured Data Files v10.1

2026-07-29T00:00:00Z

Today we're announcing the general availability of Structured Data Files v10.1. All users can now use v10.1 when downloading and uploading SDFs in the Display & Video 360 interface.

SDF v10.1 includes the following changes:

The ability to specify whether a YouTube video asset identified in a Video ID or Related Videos column contains content that was created or edited with AI. Read more about AI labeling in ads using SDF.
Support for digital out-of-home Insertion Order and Line Item resources.
New columns identifying the Display & Video 360 creatives in use by ads and ad groups.
Updated options for the Inventory Mode column of Line Item files.

See the release notes for the details on the changes in v10.1. If you are using a version previous to v10, it is now deprecated. Follow the instructions in our migration guide to migrate to v10 from any available version.

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Support for AI Content Labeling using the Campaign Manager and Display & Video 360 APIs

2026-07-28T00:00:00Z

As the use of AI becomes more prevalent, transparency is key. In the last week, we have launched updates in both the Campaign Manager 360 API and Display & Video 360 API that add new optional fields to resources in both APIs, which allow you to label a creative or creative asset as having been created or edited with AI. Labels will be applied to ads with such assets serving in regions with local AI labeling regulations. As of today, those regions are the European Union (EU), India, and New York state. Read more about AI content labeling at the Campaign Manager 360 Help Center and Display & Video 360 Help Center.

In both APIs, this configuration is set using the optional syntheticContentAttestationStatus field in relevant resources. Setting this field to IS_SYNTHETIC applies the label in the regions listed above, while setting it to NOT_SYNTHETIC confirms that the content does not require a label. You can also leave the field unset. A label will not be applied if the field is left unset. However, once the field is set for a resource, it can't be unset and may only be updated to be either IS_SYNTHETIC or NOT_SYNTHETIC.

If you have any questions regarding the Campaign Manager API, contact Campaign Manager 360 API support. If you have any questions regarding Display & Video 360 API or Structured Data Files, or want to discuss this post, reach out to us on the #display-video-360-api or #structured-data-files channels on Discord.

Using Campaign Manager 360 API

In the Campaign Manager 360 API, this configuration is set in Creative resources. The syntheticContentAttestationStatus field can be set at resource creation using creatives.insert or updated for existing resources using creatives.patch and creatives.update.

For more information about how synthetic content labels work in Campaign Manager 360 API, see our guide page.

Using Display & Video 360 API

In the Display & Video 360 API, this configuration is set in Creative and AdAsset resources. The syntheticContentAttestationStatus field can be set at resource creation using advertisers.creatives.create, advertisers.adAssets.create, advertisers.adAssets.bulkCreate and advertisers.adAssets.upload. It can also be set or updated for existing resources using advertisers.creatives.patch and advertisers.adAssets.patch.

For more information about how synthetic content labels work in Display & Video 360 API, see our guide page.

Using Display & Video 360 Structured Data Files

Starting in Structured Data Files (SDF) v10.1, which is scheduled to launch in the coming weeks, you will be able to add labels when using YouTube videos as video assets in Ad files or as related videos in Line Item files. More details on this implementation will be provided in the upcoming launch announcement of SDF v10.1 and the associated reference documentation.

Passkey authentication requirement for the Google Ads API

2026-07-27T00:00:00Z

As part of improving security for Google Ads accounts, the Google Ads API will start requiring passkeys for Google Ads API users. This is part of a broader change in Google Ads that requires passkeys to authorize sensitive actions in your Google Ads account. These important security updates will start rolling out from August 5, 2026, and will be enabled for all users over the next few weeks.

What is changing?

Once this change goes live, users following the user authentication workflow to generate new OAuth 2.0 refresh tokens for Google Ads API will always be required to authenticate using a passkey. If you haven't created a passkey, you will be asked to create one, and use it to complete the authentication workflow. Other forms of authentication that use password alone, or 2-factor authentication (2FA) mechanisms such as Time-based One-Time Password (TOTP) or SMS-based codes will be disallowed.

What action do I need to take?

You may be affected by this change, depending on the authentication workflow that your application uses.

Service account workflow: Service account workflows are not affected by this change, so no action is required. We strongly recommend using service account workflow for applications that require automated or offline workflows.
User authentication workflow: If your app generates OAuth 2.0 refresh tokens for users, you will be affected as follows:
- Existing OAuth refresh tokens are not affected by this change. They will continue to work as usual, and you won't be prompted for reauthorization when obtaining OAuth access tokens.
- New users will be challenged to authorize with a passkey. A 7-day security delay may apply before a new passkey becomes trusted and operational. To ensure it's ready for use when you need it, create your passkey at your earliest convenience.

To set up a passkey,

Go to g.co/passkeys.
Click Create a Passkey to sign in to the Security Key Manager.
Create a passkey by following the steps provided by your device.

What other platforms are affected by this change?

Google products that use Google Ads API, such as Google Ads Editor, Google Ads scripts, BigQuery Data Transfer Service or Data Studio to manage Google Ads will also start requiring a passkey-based authentication. If you don't have passkeys enabled, you will be prompted to add one.

To learn more about how to set up passkeys, visit the Help Center. If you encounter issues, you can contact support.

For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server.