Google Ads Developer Blog

Google Ads API v21 sunset reminder

2026-06-25T17:06:36.798-07:00

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

Here are some resources to help you with the migration:

You can view a list of methods and services your project has recently called using the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.
Click Google Ads API in the table.
On the Metrics subtab, you should see your recent requests 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.v21.services.GoogleAdsService.Mutate.
```
(Optional) Choose the timeframe you want to view for your requests.

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

Ben Karl

Google’s Advertising and Measurement Developer Relations team

Multi-party approvals in the Google Ads API

2026-06-25T16:24:24.037-07:00

As part of improving security for Google Ads accounts, the Google Ads API will start requiring multi-party approvals when performing sensitive API actions. This is part of a broader change in Google Ads that requires multi-party approvals to perform sensitive actions in your Google Ads account. These important security updates will start rolling out starting on July 27, 2026, and will be enabled for all users over the next few weeks.

What is changing?

When this change goes live, the following API calls will change their behavior.

Inviting a user

If you use the CustomerUserAccessInvitationService.MutateCustomerUserAccessInvitation method to invite a new user to manage a Google Ads account, the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the system will pause the standard workflow and will not immediately generate a CustomerUserAccessInvitation or dispatch the invitation email. A MultiPartyAuthReview resource is initiated instead, with its resource name provided in the response. Once the pending review receives approval from a second account administrator, the CustomerUserAccessInvitation will be created and the invited user will receive their email. No new invites can be created for the user until the pending review is resolved.

Updating or terminating a user’s access

If you use the CustomerUserAccessService.MutateCustomerUserAccess method to adjust a user's permissions using the update operation or revoke access using the remove operation, the Google Ads API now evaluates whether multi-party approval may be necessary. In cases where our servers determine that a review is required, the API generates a MultiPartyAuthReview resource in a pending state and returns its resource name. Your requested modifications will remain pending and will only take effect once the multi-party review is successfully approved by a second account administrator. The CustomerUserAccess under review cannot be mutated until the pending review is resolved.

How do I approve a multi-party approval request?

You can fetch a pending MultiPartyAuthReview by using the GoogleAdsService.Search or GoogleAdsService.SearchStream methods, using the following GAQL query.

SELECT 
    multi_party_auth_review.resource_name,
    multi_party_auth_review.multi_party_auth_review_id,
    multi_party_auth_review.creation_date_time,
    multi_party_auth_review.request_user_email,
    multi_party_auth_review.operation_type,
    multi_party_auth_review.justification,
    multi_party_auth_review.target_resource,
    multi_party_auth_review.customer_user_access_review.old_customer_user_access,
    multi_party_auth_review.customer_user_access_review.new_customer_user_access,
    multi_party_auth_review.customer_user_access_invitation_review.new_customer_user_access_invitation
FROM multi_party_auth_review 
WHERE multi_party_auth_review.review_status = 'PENDING'

A pending MultiPartyAuthReview request can be approved or rejected using a MultiPartyAuthReviewService.ResolveMultiPartyAuthReview API request. The review needs to be done by a second administrator who did not create the original request. This can either be a human or a service account with administrator privileges. The pending review can be revoked by the original requestor.

What do I need to do?

If your application uses these methods, make sure to update it to handle the multi-party approval workflows before July 27, 2026. We have added support for multi-party approvals to all the major versions of the API (v24.2, v23.3, v22.2 and v21.2). If you are using an official client library, make sure to download their latest version. You can refer to the following guides to learn more about these changes, which cover details on

Various states of a multi-party approval request
How to retrieve and review multi-party approval requests
How to handle multi-party approval requests when inviting users
How to handle multi-party approval requests when updating user roles or removing user access

For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server. For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

- Anash P. Oommen, Google Ads API Team

Announcing v24.2 of the Google Ads API

2026-06-24T18:00:31.600-07:00

Today, we’re announcing the v24.2 release of the Google Ads API. This minor release brings critical security updates, new AI transparency features, reporting enhancements, and powerful planning insights. To use these new capabilities, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

We are also releasing minor versions v23.3, v22.2 and v21.2 of the Google Ads API to add additional support for multi-party approvals and synthetic content labeling.

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 (June 25th at 10a 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

Multi-party approvals (MPA) for Google Ads API: We are introducing support for multi-party approval in the Google Ads API. This feature secures sensitive account actions such as user invitations and user access level updates by requiring a second administrator to approve the changes.

AI Transparency: Synthetic Content Labeling: As AI-generated assets become more common, transparency is essential. Google Ads API v24.2 exposes the SyntheticContentInfo and SyntheticContentAttestation structures on both Asset and Ad resources, allowing you to programmatically label AI-generated ad creatives. Both the advertiser and Google systems can attest whether the assets and ads are AI-generated or not, as well as whether they were generated fully automatically, or with advertiser-review. If you're preparing for the EU AI Act taking effect on August 2, 2026, then explore this feature. To help you plan your upcoming integration work for v25, the interface for mutating advertiser attestation fields is being introduced early for versions v22 and later. The interface is visible in these versions, but synthetic_content_info.advertiser_attestation.status and synthetic_content_info.advertiser_attestation.source fields will remain immutable for these versions.

If you attempt a mutate request on either of these fields, one of these errors will be returned:

"The field attempted to be mutated is immutable" or "Field cannot be set". These fields will become fully mutable starting in v25. We recommend using the interface now to build and test your internal logic so your system is ready for full write capabilities when v25 is launched.

PMax Placement Reporting & Video Linkages: This release also includes key reporting and video asset enhancements:

PMax Placement Segmentation: You can now segment your performance_max_placement_view reporting by ad_network_type, giving you granular visibility into where your PMax ads are serving across Search, Display, and partner networks.
YouTube Brand Channel Links: Create secure YouTube data links associated with a specific brand channel directly via the Google Ads API, enabling richer video asset integrations.
Landing page text generation: Opt-in to automatic text asset generation derived directly from your landing page using the new LANDING_PAGE_TEXT_GENERATION AssetAutomationType.

New Experiment Types: We have introduced new experiment types to provide greater testing flexibility.

Campaign Mix Experiments: This new workflow supports the COMPARE_CAMPAIGNS experiment type, which is equivalent to Custom mixed campaign types in the Google Ads UI. It allows you to assign existing campaigns across up to 5 experiment arms to compare multiple variables and campaign types within a single experiment. This workflow also supports creating custom Performance Max experiments.
Performance Max Feature Testing: The new PMAX_TEXT_CUSTOMIZATION_FINAL_URL_EXPANSION experiment type lets you split traffic within a single campaign to test the impact of text customization (formerly automatically created assets) and final URL expansion.

Documentation updates

We have revamped the release notes format to help you identify the changes introduced in each release. Breaking changes are now listed separately from non-breaking feature updates. The Feature deprecations and unversioned changes guide helps you keep track of feature sunsets.

We hope this new format helps you perform API upgrades more easily. Try it out, and let us know your feedback by clicking the Send Feedback button.

Getting Started

Google Ads API v24.2 is a drop-in upgrade for v24.1. 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. For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

- Anash P. Oommen, Google Ads API Team

More autonomy, less context: Introducing Agent Skills for Google Advertising and Measurement

2026-06-24T10:01:23.103-07:00

The way developers build and integrate software is changing. With the rapid adoption of AI-powered coding assistants, we are launching a dedicated set of Google Advertising and Measurement agent skills in the Google skills repository to empower your integration with products.

These skills transform your AI agents into Google ads and measurement specialists. For example, you’re working in your favorite agentic-enabled IDE and want to set up Google Ads API credentials and a client library. Our new repository serves as the official hub for curated sets of context and best practices designed to guide AI agents in helping you complete your task faster and more accurately.

What are Agent Skills?

Think of an Agent Skill as a token-efficient cheat sheet for an AI assistant. They follow the Agent Skills open standard, letting your agents use skills as modular tools when relevant. Each skill has a title and short description that the agent uses to decide when to activate the skill.

How do Agent Skills work?

Skills are more powerful than reusable prompts and AGENTS.md files because Agent Skills use “progressive disclosure”. This means your agent only pulls in the exact context it needs - and nothing it doesn't. Full instructions load only when a task calls for them, so agents can keep many skills on hand with only a small context footprint.

When your agent encounters a specific task, such as integrating the Google Mobile Ads (GMA) SDK, the agent selectively activates the relevant skill and reads its instructions to complete the task.

Why Agent Skills?

AI assistants are only as good as the information they can access. By providing a dedicated repository of official guidance, we aim to:

Provide accurate and up-to-date guidance directly within your AI-assisted coding environment.
Lower the barrier to entry for our SDKs and APIs by giving AI agents the necessary context to offer successful integration advice.
Establish a unified hub that provides official, high-quality guidance from Google developers.

Implement Google ads with core skills

Our initial launch includes a targeted set of skills across several ads products:

Skill Name	Description
google-mobile-ads-get-started	Assists with adding the Google Mobile Ads SDK to your app for the first time, setting the application ID, and initializing the SDK.
google-mobile-ads-android-migrate-to-next-gen	Assists with migrating your Android codebase from the legacy Android Google Mobile Ads SDK to GMA Next-Gen SDK.
google-mobile-ads-banner	Assists with implementing banner ads, such as large anchored adaptive banners and inline adaptive banners.
google-mobile-ads-interstitial	Assists with implementing full-screen interstitial ads and showing them at natural transition points in your app.
google-mobile-ads-rewarded	Assists with implementing rewarded ads, showing them and handling user reward callbacks.
ima-sdk-basics	Assists with implementing Interactive Media Ads (IMA) SDK client-side ad insertion to request VAST or VMAP video ads across websites, apps, and TVs.
google-ads-api-mcp-setup	Assists with installing the official open-source Google Ads MCP server to a user’s AI assistant to query campaigns or retrieve reporting metrics using natural language.
google-ads-api-quickstart	Assists with Google Ads API credential setup, choosing a client library, running a "retrieve campaigns" script and troubleshooting common errors.
data-manager-api-audience-ingestion	Assists with getting started using the Data Manager API for sending audience data to supported Google products.
data-manager-api-event-ingestion	Assists with getting started using the Data Manager API for uploading event and conversion data to supported Google products.

How to install ads agent skills

You can discover and install these skills using npx:

npx skills add google/skills/skills/ads

This lets you choose specific skills for your project, ensuring your AI assistant has exactly the context it needs without unnecessary bloat.

And to keep your skills up to date, you can run the following command:

npx skills update

Share your feedback

Visit https://github.com/google/skills today to get started. Share your feedback directly in GitHub or join our Discord. And stay tuned for more updates.

- Justin Malandruccolo, Mobile Ads Developer Relations

Changes to Support for Smart Campaigns in the Google Ads API

2026-06-23T07:59:33.306-07:00

Starting on August 3, 2026 you will no longer be able to create new Smart Campaigns using the Google Ads API. You will still be able to update your existing Smart Campaigns, and they will continue to serve ads.

In lieu of new Smart Campaigns, we recommend exploring other campaign types, such as Performance Max, an automated campaign type that serves across Google's advertising channels. Other campaign types, such as Search or Demand Gen, are also available, depending on your business goals.

Technical details

To determine whether your application is creating Smart Campaigns, look for campaign mutate requests with create operations where the campaign's advertising_channel_type is set to SMART and the advertising_channel_sub_type is set to SMART_CAMPAIGN.
When attempting to create a new Smart Campaign, the following will occur:
- In v24 of the Google Ads API:
  - A SmartCampaignError.CREATION_FAILED error will be returned and the request will fail.
  - In v23 and earlier of the Google Ads API
    - A OperationAccessDeniedError.CREATE_OPERATION_NOT_PERMITTED error will be returned and the request will fail.

For technical support issues, please 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.

Ben Karl

Google’s Advertising and Measurement Developer Relations team

Dynamic Search Ads (DSA) Automigration Delayed to February 2027 and Campaign Creation Restored

2026-06-11T09:39:32.911-07:00

What is changing?

Google is extending the timeline for the transition of Dynamic Search Ads (DSA) to AI Max for Search campaigns and restoring campaign creation functionality.

Automigration Delayed: The automatic upgrade of DSA campaigns to AI Max (or Search campaigns with broad match and Smart Bidding) has been postponed from September 2026 to February 2027.
Creation Restored: The ability to create new DSAs is being restored on June 15, 2026.

This change is designed to give advertisers additional time to manage their own transitions, perform thorough testing, and ensure a seamless migration to AI Max.

What is the DSA Migration?

Dynamic Search Ads (DSA) have long helped advertisers capture relevant searches by using website content to target ads. As part of our commitment to delivering the best performance through Google AI, we are transitioning legacy search features to more advanced, asset-based AI Max for Search campaigns.

Why is this changing?

By moving the automigration to February 2027 and restoring the ability to create new DSAs, we are providing additional flexibility to perform these migrations on your own schedule and terms.

How to Prepare

Although you now have additional time, we strongly recommend proactively managing your migration rather than waiting for the automatic upgrade in February 2027. Manual migration allows you to tailor your assets and maintain tighter control over your campaign structures.

Step 1: Audit Your Accounts

Identify all active DSAs and ad groups currently running in your accounts.

If you are using the Google Ads API, you can query the campaign resource to find campaigns with the advertising channel type set to SEARCH and targeting settings configured for dynamic search ads:

SELECT
  campaign.id,
  campaign.name,
  campaign.status,
  campaign.dynamic_search_ads_setting.domain_name
FROM
  campaign
WHERE
  campaign.status = 'ENABLED'
  AND campaign.dynamic_search_ads_setting.domain_name IS NOT NULL

Step 2: Begin Side-by-Side Testing

Use the restored DSA creation functionality to maintain your baseline while you test AI-powered alternatives. We recommend setting up Campaign Experiments to test AI Max for Search campaigns (with broad match and Smart Bidding) against your existing DSA campaigns to measure performance parity.

Step 3: Utilize Voluntary Upgrade Tools

When you are ready to transition, use the voluntary upgrade tools available in the Google Ads UI. These tools allow for a "one-click" transition that preserves historical reporting and minimizes learning-phase disruptions by mapping your DSA targets to their modern equivalents.

The Updated Transition Timeline

We encourage you to take advantage of this extension to complete your migrations. The updated timeline is as follows:

Immediate (June 2026): DSA campaign creation is fully restored. Advertisers can create and edit DSA campaigns as needed.
June 2026 – January 2027: Extended testing and voluntary migration period. Advertisers should actively transition campaigns.
January 2027: Ability to create DSAs is removed.
February 2027: Automigration begins. Any remaining active DSA campaigns will be automatically upgraded to Performance Max or AI-powered Search campaigns.

Bob Hancock, Google Ads API Team

Introducing the Google Ads API Developer Assistant v3.0.0

2026-06-10T08:52:46.774-07:00

We are pleased to announce the release of v3.0.0 of the Google Ads API Developer Assistant. This major release marks a significant milestone in the evolution of the Assistant, focusing on architectural modernization, improved reliability, and a more modular design.

With this release, we are migrating the Assistant to the Google Antigravity agent framework and transitioning to a Skills-based architecture. These changes make the Assistant more robust, easier to maintain, and reduce token use.

What’s new in v3.0.0?

1. Powered by the Antigravity framework

The Google Ads API Developer Assistant has migrated from gemini-cli to the Antigravity agent framework (v3.0.0). This underlying framework upgrade provides a more structured and reliable execution environment. Along with this, the directory and file structure of the project has been updated to be fully Antigravity-ready.

Support for gemini-cli will terminate on June 18, 2026, as detailed in this Google blog announcement.

2. A modular, skills-based architecture

We have transitioned the Assistant's core capabilities into Skills. Instead of relying on broad, unstructured instructions in a context file, the Assistant now loads specialized, test-backed tool directories (Skills) dynamically when needed. This drastically reduces "hallucinations" and ensures tasks are executed using precise, verified procedures.

Key updates in this modular transition include:

GAQL validation (validate_gaql): Moved to a dedicated skill. It now includes enhanced static query checks for date segments, click_view single-day filters, and change_status boundaries.
Troubleshoot conversions (troubleshoot_conversions): Replaces the old conversions_support_package. It consolidates all conversion troubleshooting and upload summary scripts, and tests into a single, cohesive skill directory.
Structured commands (explain and step_by_step): Converted to skills to enforce consistent, structured layouts for explanations.
New account mapping (get_cids_under_mcc): A new skill to retrieve all child accounts under a Manager Account (MCC).
New object inspection (inspect_object): A new skill for dynamically looking up Protobuf messages and Enums on the fly, to help ensure the Assistant always uses correct structures.
New PMax listing filter (pmax_listing_filter): A new skill to standardize listing group webpage exclusion tree modifications for Performance Max campaigns.

3. Enhanced consistency & rigor

We've introduced stricter rules and requirements to help ensure high-quality code generation and query validation:

Explicit API versioning: Critical skills like get_cids_under_mcc, validate_gaql, and troubleshoot_conversions now require an explicit api_version argument, eliminating ambiguity.
Strict GAQL rules:
- Added a rule to AGENTS.md to prevent the use of SQL aggregate functions (such as SUM, COUNT, and AVG) in GAQL queries, as they are not supported.
- Added a rule to check Google Ads API Developer site release notes first for the current API version to ensure the Assistant uses up-to-date documentation.
- Streamlined configuration: AGENTS.md has been streamlined leading to a smaller initial context window. Duplicate conversion documentation has been removed in favor of programmatic skills.

4. Developer Experience (DX) improvements

We've made several quality-of-life improvements to make your development loop faster and smoother:

Persistent virtual environment (.venv): The virtual environment is no longer deleted at the end of a session. On startup, the Assistant checks your system's Python version; it only rebuilds the .venv if a newer Python version is available.
Smart API version caching: The Assistant now caches the current Google Ads API version with a TTL of 19 hours, reducing startup time by avoiding redundant network checks.
Better debugging with persistent logs: Log messages now include datetime stamps. The log file is written to the .agents/ directory and is no longer reset on each run, preserving history for troubleshooting.

Why should you upgrade?

The upgrade to v3.0.0 is primarily about reliability and structure. By moving to the Antigravity framework and modularizing features into Skills, we have made the Assistant more predictable and resource efficient.

If you want a faster startup, more reliable GAQL validation, and a more robust troubleshooting experience, we recommend upgrading to v3.0.0.

Get started

First installation

Install Antigravity CLI: Follow instructions at https://antigravity.google/.
Clone the Assistant:

git clone https://github.com/googleads/google-ads-api-developer-assistant.git

Run the Install Script:
- Linux/macOS: Run ./install.sh (defaults to Python support, use flags like --php or --ruby for other languages).
- Windows: Open PowerShell and run .\install.ps1.

Upgrade from v2.x

Copy any custom code or data from saved/ to a secure location outside the project directory.
Delete your local clone of the Assistant.
Clone the repository:

git clone https://github.com/googleads/google-ads-api-developer-assistant.git

Run the install script (install.sh or install.ps1) to initialize the new Antigravity environment.

Bob Hancock, Google Ads API Team

Data Manager API now supports sending events to Google Marketing Platform destinations and IP ingestion for Google Ads Customer Match

2026-05-28T14:53:06.733-07:00

Google Marketing Platform event ingestion

The Data Manager API has introduced support for sending offline conversion events to Google Marketing Platform products, including Campaign Manager 360, Search Ads 360, and Display & Video 360.

The AdIdentifiers object now includes dclid, impressionId, matchId, and encryptedUserIds. Check out the Get started guide to see which fields are required for uploading conversions that occur away from your website.

If you're currently using the Campaign Manager 360 API for conversion uploads, we recommend reviewing our upgrade guide to explore the advantages of the Data Manager API. These include a unified schema across all Google advertising products, encryption of user identifiers such as email and phone number, and the ability to route events to multiple destinations in a single request.

Composite data & IP ingestion for Google Ads Customer Match

In addition, you can now send IP addresses in Google Ads Customer Match uploads using the new CompositeData field.

Composite data allows you to include IP data, either on its own or alongside user identifiers like email address, phone number, and address information. Providing IP addresses along with their corresponding observation timestamps in IpData will help drive higher match rates for Google Ads Customer Match beginning in Q3 2026.

While we'll continue to support the user_data field for user identifier uploads, we recommend sending user identifiers using composite_data to ensure your integration is ready for future improvements and features.

Get started

Learn how to upgrade your existing Campaign Manager 360 offline conversion upload workflows:
- Upgrade from the Campaign Manager 360 API
Learn how to send IP addresses for Google Ads Customer Match:
- Composite data
- IP ingestion for Customer Match

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.

- Lindsey Volta, on behalf of the Data Manager API Team

Standardizing Reach Metrics with Total Co-view in the Google Ads API

2026-05-27T09:33:19.067-07:00

Starting on June 2nd, 2026, the Google Ads API will transition reach metrics to a "Total Co-view" definition. This update aligns Google Ads reporting with offline media and third-party measurement standards, ensuring consistency across all reporting surfaces, including the Google Ads UI and Editor.

The updated definition of the video view metrics will include all individuals who viewed the ad on connected TV devices, including cases where multiple people are watching YouTube together on the same TV screen.

This change impacts the following reach metrics at the campaign level:

metrics.unique_users
metrics.average_impression_frequency_per_user
metrics.unique_users_two_plus
metrics.unique_users_three_plus
metrics.unique_users_four_plus
metrics.unique_users_five_plus
metrics.unique_users_ten_plus

Required actions

No API version migration or code changes are required to see this new behavior, as it is a data definition change that will be applied automatically.

However, developers and advertisers should be prepared for a potential change in reported reach and frequency values for dates beginning with the launch date. We recommend updating internal documentation or dashboards to reflect this shift in measurement methodology.

If you have any questions or concerns regarding this update, please reach out via the

“Google Advertising and Measurement Community” Discord server.

Mattia Tommasone

Google’s Advertising and Measurement Developer Relations team

Ads DevCast: Google Marketing Live 2026 bonus episode

2026-05-21T07:07:00.480-07:00

We're excited to bring you a special bonus episode of Google’s Ads DevCast! We’re going over a few of the bigger announcements and updates from Google Marketing Live (GML) 2026 that directly affect our developers and technical users, across Tagging, Data Manager, and Meridian.

Watch it at goo.gle/watchadsdevcast

Hear it at goo.gle/listenadsdevcast

Key Highlights from the Episode

Tagging improvements: Discover the new Google tag gateway In-UI setup offerings (featuring GCP, Akamai, Cloudflare, and Fastly) and new CMS integrations. We also discuss Visual Tagging for troubleshooting purchase conversions, and how we are bringing GTM capabilities directly to the Google tag.
Data Manager API: Learn about the value of single ingestion and multi-feed, allowing you to flow first-party data to multiple Google products with a unified schema. We also touch on Confidential Matching for privacy-safe audience building.
Meridian (open-source MMM): Get an overview of the new Meridian offerings announced at GML, including Meridian in GA360, Meridian Studio (featuring native agentic capabilities), and Meridian GeoX for incrementality calibration.

Listen to the episode to get all the details and prepare for next week's deep dive into Meridian!

Don't forget to take our Episode Survey to let us know what you think!

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.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Changes to Offline Click Conversion Import Support in the Google Ads API

2026-05-15T09:20:41.339-07:00

Starting on June 15, 2026, the Google Ads API will no longer accept new adopters of offline conversion imports, including enhanced conversions for leads. As with our previous announcements for session attributes and IP address, and Customer Match, Data Manager API is now the primary API for importing offline conversions.

Developers who have not adopted offline conversion imports or Enhanced conversion for leads, or have not imported offline conversions between December 2025 and May 2026, will receive an error if they attempt to import offline conversions. Developers who have already adopted offline conversions or Enhanced conversions for leads can continue importing using the Google Ads API while they integrate with the Data Manager API.

See our migration guide for Google Ads API users to start integrating with the Data Manager API.

Technical details

Developers will be allowlisted by their developer token.
Once this change is rolled out, new adopters will receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting to use the ConversionUploadService.UploadClickConversions method.
See the documentation for integrating with the Data Manager API for offline conversion imports for Google Ads API users.

Reach out to the Google Ads API support or Data Manager API support channels if you have any questions.

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.

- Ben Karl, on behalf of the Google Ads API Team

Announcing expanded experiment functionality in Google Ads API v24.1

2026-05-14T08:33:21.865-07:00

We are excited to announce a significant expansion of the Google Ads A/B experiments feature set in the v24.1 release, launched yesterday, May 13, 2026. We know API functionality is critical for advertisers who manage large sophisticated accounts, and we want to give these advertisers the capability to better create and manage their A/B experiments at scale. This update broadens the platform's current scope, enabling advertisers to leverage the power of experiments for a broader range of testing scenarios to drive campaign performance.

Direct experiment reporting

One of the most requested enhancements is the ability to query experiment statistics directly through the API. Previously, you had to manually calculate statistics by querying campaign resources. With v24.1, we are exposing experiment arm-level and significance stats, including:

Control arm stats: The average value of metrics in the control arm.
Point estimates: The mean value of the difference between the control and treatment arms, calculated via the jackknife method.
Margin of error: The radius of the confidence interval.
P-values: Represents the calculated probability that the difference could have occurred by chance.

New experiment types

We are expanding support for a variety of experiment types to help you find the best configurations for your business:

Feature-specific tests (AI Max and broad match): Test the impact of enabling AI Max or broad match keywords. These use an intra-campaign workflow, where the feature is tested within the original campaign shared by both the control and treatment arms.
Custom video experiments: Run custom experiments consisting of Video campaigns.
Performance Max replacement: Test how your Shopping campaigns perform compared to Performance Max.
Performance Max asset optimization: Specifically for Performance Max, you can test different variations of assets including text, images, and videos. This asset optimization workflow helps determine which creative combinations drive the best results.

While these updates cover a significant number of use cases, we are continuing to work on the platform and plan to introduce even more experiment types in future releases.

Where can I learn more?

Updated documentation and code examples are available on the Google Ads API Developer site. We also encourage you to join the discussion and share your feedback on our Ads and Measurement Community Discord server.

- Laura Chevalier, Google Ads API Team

Announcing v24.1 of the Google Ads API

2026-05-13T14:28:26.366-07:00

Today, we’re announcing the v24.1 release of the Google Ads API. To use the new v24.1 features, 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, our Ads Developers YouTube Live, or our LinkedIn Live event tomorrow (May 14 at 10a 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

Mobile Device Platform Segment: Understanding where your traffic comes from is critical for campaign optimization. With v24.1, you can now segment campaign-level and customer-level reports using the segments.mobile_device_platform column.

This field utilizes the new MobileDevicePlatform enum (supporting values like IOS and ANDROID), allowing you to cleanly isolate performance data and adjust bid strategies based on the user's mobile operating system.

Classic images in DemandGen campaigns: As of v24.1, you can use the classic_display_images field of DemandGenMultiAssetAd to upload static image ads to serve on the Google Display Network (GDN) within your Demand Gen campaigns. These images are served as-is, without being combined with additional assets. This format provides full control over your creative branding. Refer to our help center for more information.

Support for passkeys: Passkeys provide a simple and secure alternative to passwords. Google now requires some advertisers to use a passkey to authorize sensitive actions within their Google Ads account. The v24.1 introduces a new passkey_enabled field that indicates whether the user has a passkey enabled.

Revamped support for Experiments: Experiments let you test the impact of your proposed changes. If you split the budget or traffic between the original campaign and experiment, you can easily compare the results over a specified time period. If the experiments produce better results, you can apply the experiment to the original campaign or replace the original campaign.

The v24.1 introduces support for new experiment types: AI Max experiments, Video experiments, Demand Gen experiments (this and video are the same API type) and Performance Max experiments. You can now retrieve and compare detailed performance metrics (such as clicks, conversions, and impressions) across individual experimental arms. This makes side-by-side performance analysis easier and more transparent. Refer to our guide to learn more about experiment workflows.

New Data Retention Policy for Google Ads: We recently announced that starting June 1, 2026, Google Ads and related measurement APIs will transition to a 37-month data retention policy for granular performance statistics (daily, hourly, and weekly). The V24.1 introduces a new DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED error code to support this change.

The following resources can help you get started:

For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

- Anash P. Oommen, Google Ads API Team

Data Manager API: Introducing support for Google Ads store sales and more event ingestion use cases for Google Analytics

2026-05-07T13:09:00.000-07:00

We're excited to announce several significant enhancements to the Data Manager API. This release introduces support for uploading store sales conversions to Google Ads and broadens support for Google Analytics event ingestion.

Store sales conversions

The Data Manager API offers a streamlined ingestion workflow for sending store sales conversions to Google Ads. This workflow eliminates the need to create and monitor multiple offline jobs and replaces those jobs with a single API request. You can also leverage additional features such as confidential matching, encryption for user identifiers, and support for sending multiple items per event in CartData. To use this feature, your Google Ads account must meet certain eligibility requirements.

Google Analytics web and app events

Building on our existing capabilities, we've expanded support for sending events to Google Analytics within the Data Manager API.

Web and app data stream event ingestion: You can now send any event to both your Google Analytics web and app data streams, provided they're not reserved events.
- Data Manager API is an alternative to Measurement Protocol for sending recommended and custom events directly to Google Analytics.
- Data Manager API's unified schema now supports important metadata like app instance ID, event location, and mobile device information for app events.
Event routing: Configure a destination using your Firebase App ID or Measurement ID to send an event to your Google Analytics app stream or web stream respectively.
Expanded support for events sent as an additional data source: The Data Manager API now supports sending any event with a transaction ID to both web and app data streams as an additional data source for your tag or Google Analytics for Firebase (GA4F) SDK implementation.
- This feature is no longer restricted to purchase events sent to web data streams.
- This feature is limited to Google Analytics properties on an allowlist; please fill out this form if you're interested in adding your property to the allowlist.

Get started

Upgrade your existing store sales workflows to gain access to future improvements and features:
- Upgrade from the Google Ads API
Start sending events to Google Analytics with the Data Manager API:

Connect with us

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

- Lindsey Volta, on behalf of the Data Manager API Team

Managing your integrations at scale: Ads DevCast E4

2026-05-07T10:38:00.000-07:00

Scaling an advertising integration is more than just writing code—it requires a deep understanding of efficiency, resilience, and auditability. In Episode 4 of Ads DevCast, "Managing your integrations at scale," we break down universal architectural best practices and product-specific solutions to help you optimize your advertising integrations.

Watch the full episode

Hear the full episode

Whether you are working with the Google Ads API, Google Ads scripts, Data Manager API, DV360, or Google Analytics, here is a summary of the key takeaways to build high-performance, scalable systems.

Universal Principles of Robust Integrations

Respect Rate Limits: Rate limits are a reality of using APIs at scale. Understand your limits beforehand to prevent lockouts and maintain a healthy integration. Read the error messages — they may contain instructions on what to do next. For transient or retry-able errors, don't hammer the server with rapid retries. Instead, implement exponential back-off with jitter to give the system time to recover.
Prioritize Logging and Monitoring: Always consider logging in production where appropriate. Capture crucial metadata, like the Google Ads API request_id, in your structured logs to trace failures instantly. If a call is erroring, write that error payload to logs. Set up proactive alerts to catch errors before they impact operations.
Use Official Client Libraries: While direct REST/gRPC calls are supported in many of our products, using official libraries saves development time and handles heavy lifting (e.g., serialization and authentication) out of the box.
Cache Smartly: Reduce redundant queries. If you are querying historical data that will no longer change, cache it locally to save bandwidth and rate limits.

Product-Specific Best Practices

Google Ads API: Optimize efficiency by Batching Operations. Group operations logically to reduce round-trips. Order your operations correctly to improve execution efficiency.
Data Manager API: Batch ingestion requests to process events efficiently. Understand the difference between synchronous errors (structural issues returned instantly that reject the whole batch) and asynchronous validation (monitored via the Diagnostics endpoint).
Google Ads scripts: Avoid sequential iterations when dealing with many accounts at once. Use Bulk Uploads with CSV tables to apply scaled operations, and leverage the executeInParallel method for MCC scripts to run up to 50 concurrent execution threads.
Display & Video 360 API: Utilize Structured Data Files (SDFs) to manage YouTube line items and ad group bulk operations that aren't natively supported by the API.
Google Analytics: Enable daily BigQuery Exports for event-level data, and utilize Long-running Asynchronous Report Tasks in the Analytics Data API v1alpha to build scalable, customized reports without HTTP timeouts.

Next Steps:

Watch the full episode on our YouTube channel (or listen on YT Music)

Check out our Advertising and Measurement Developer Hub.

Join our community on Discord and share your scaling stories or questions with Googlers and other developers.

Learn more in our guides below:

Google Ads API Best Practices and Batch Processing
Google Ads scripts Bulk Upload and Best Practices
Analytics BigQuery Solution and Report Tasks Fundamentals
Data Manager API Best Practices, Limits, and Diagnostics
Display & Video 360 Structured Data Files (SDFs)

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

New Data Retention Policy for Google Ads starting June 1, 2026

2026-05-01T17:40:17.036-07:00

Starting June 1, 2026, Google Ads and related measurement APIs will transition to a 37-month data retention policy for granular performance statistics (daily, hourly, and weekly). High-level data (monthly, quarterly, and yearly) will continue to be available for 11 years.

API	Impact	Next Steps
Google Ads API and Google Ads scripts	Starting June 1, 2026, queries that request granular segments (such as segments.date, segments.week) for ranges older than 37 months from the current date will return a `DateRangeError.INVALID_DATE` error. Future API versions will return `DateRangeError.REQUESTED_DATE_GRANULARITY_NOT_SUPPORTED` error. To retrieve data older than 37 months, you must update your queries to use `segments.month`, `segments.quarter`, or `segments.year`. Unsegmented queries for historical data must align perfectly with calendar month boundaries (1st to last day of month) to succeed.	Please review your applications and make updates. If you require granular historical data beyond 37 months, we recommend exporting it prior to the June 1, 2026 deadline. If you have any questions, you can contact us on our Google Ads API support channel or Google Ads scripts support channel.
Google Analytics Data API	The Google Analytics Data API will truncate affected metrics to the latest 36-month window if the dimension "date" is also used in the report. Affected metrics include Advertiser Ad Cost, Clicks, and Impressions. Only reports with all of affected metrics, 37-months or older, and including the dimension "date" are impacted. Date-equivalent dimensions like "Day of week" and "day" are also impacted.	Review your data stitching logic to account for this truncation.
DV360 API and CM360 API	These APIs currently maintain a 24-month retention period, which remains unchanged.	No impact.
BigQuery Data Transfer Service	Starting June 1, 2026, the BigQuery Data Transfer Service for Google Ads and BigQuery Data Transfer Service for Search Ads 360 connectors will stop populating data for backfill runs with dates older than 37 months from the current date. Data transferred and stored in BigQuery will remain in the tables with no impact. Starting June 1, 2026, BigQuery Data Transfer Service for Google Analytics 4 connector will stop populating data for backfill runs with dates older than 37 months from the current date. Data transferred and stored in BigQuery will remain in the tables, but if a transfer is manually triggered for a report date 37-months or older, the data of the date in BigQuery table will be overwritten by empty value.	If you want to keep historical data beyond 37 months in BigQuery, we recommend starting backfilling runs early so that they can complete before June 1, 2026.

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.

Nadine Wang, Advertising and Measurement APIs Team

Product reporting changes for Google Ads starting June 15, 2026

2026-04-30T07:47:00.000-07:00

Starting June 15, 2026, the Google Ads API will begin transitioning product reporting to include data from all Performance Max networks. This update also provides comprehensive performance metrics across all campaign types and channels, including Performance Max, Shopping, Video, App, and Demand Gen.

What is changing?

Previously, reporting for products in Video, Demand Gen, and App campaigns was limited to high-level metrics like impressions and clicks. Also for Performance Max campaigns, only some networks were reported. This update introduces:

Expanded metrics for shopping_product: Cost and Conversion metrics will start returning data for Video, Demand Gen, and App campaigns, not just Shopping and Performance Max.
Consistent campaign reporting with shopping_performance_view: All campaign types that use Google Merchant Center (GMC) will have results returned with shopping_performance_view.
Network transparency for Performance Max: All networks will start being returned for Performance Max campaigns when querying for shopping_performance_view, so you may notice a one-time increase in all product reporting metrics for these campaigns. Note that data for these new metrics and expanded campaign coverage will only be available starting from June 15 2026. Historical API requests for dates prior to the launch will not contain this expanded data.

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.

- Dora Sun - Google Ads API Team

Google Ads API v20 sunset reminder

2026-04-29T10:47:00.000-07:00

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

Here are some resources to help you with the migration:

You can view a list of methods and services your project has recently called using the Google Cloud Console:

Open APIs & Services in the Google Cloud Console.
Click Google Ads API in the table.
On the Metrics subtab, you should see your recent requests 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.v20.services.GoogleAdsService.Mutate.
```
1. (Optional) Choose the timeframe you want to view for your requests.

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

- Ben Karl, on behalf of the Google Ads API Team

Simplifying Keyword Forecast Metrics in Google Ads API v24

2026-04-23T09:40:00.000-07:00

To provide a more streamlined and reliable experience, we have unified our forecasting infrastructure. Google Ads API v24 introduces an updated GenerateKeywordForecastMetrics method that simplifies the planning process by focusing on the metrics that most directly impact your performance.

What's changing?

To streamline our systems and focus on the primary data that drives successful Search planning, Google Ads API v24 introduces the following refinements:

1. Alignment with Bidding Strategies

To provide a more consistent experience across Google Ads tools, forecasts now focus exclusively on the primary metrics that your chosen bidding strategy directly impacts. This alignment ensures that the data you use for planning is synchronized with the high-impact performance indicators for your actual campaigns:

Manual CPC and Maximize Clicks: Forecasts provide clicks, average CPC, and cost.
Maximize Conversions: Forecasts provide conversions, average CPA, and cost.
Metric Focus: To maintain consistency across the platform, forecasts no longer include cross-metric data (such as conversion estimates for click-oriented strategies) or secondary metrics like impressions and conversion value.

2. Streamlined Request Parameters

We have made the following updates to simplify forecasting requests, improve system reliability, and remove inputs which have a minimal effect on overall forecast accuracy:

CampaignToForecast.geo_modifiers[] is replaced by CampaignToForecast.geo_target_constants[]
ForecastAdGroup.biddable_keywords[] is replaced by ForecastAdGroup.keywords[].
The following fields are removed:
- CampaignToForecast.keyword_plan_network
- CampaignToForecast.negative_keywords
- ForecastAdGroup.max_cpc_bid_micros
- ForecastAdGroup.negative_keywords
- CriterionBidModifier

Timeline

The transition follows our standard release and sunset cycle:

April 2026: Google Ads API v24 is available with the updated GenerateKeywordForecastMetrics functionality.
February 2027: Google Ads API v23 is scheduled for sunset. At this time, all versions of the Google Ads API will utilize this unified forecasting infrastructure.

Next Steps

Developers that use GenerateKeywordForecastMetrics should review their integrations to ensure compatibility with the updated parameter set in v24. Review the Generate Forecast Metrics guide and the GenerateKeywordForecastMetrics v24 reference for the latest usage details.

If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our Ads and Measurement Community Discord server.

- Laura Chevalier, Google Ads API Team

Announcing v24 of the Google Ads API

2026-04-22T14:24:00.000-07:00

Today, we’re announcing the v24 release of the Google Ads API. To use the new v24 features, 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, our Ads Developers YouTube Live, or our LinkedIn Live event tomorrow (April 23rd at 10a 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

Support for Conversions with Cart Data: Conversions with cart data is an extension to conversion tracking on your website or app. Using conversions with cart data, you can provide the details of products sold for each transaction, which helps you unlock advanced sales, profit reporting, and insights for your Google Ads account and campaigns, such as number of orders, average cart size, revenue and gross profit.

Google Ads API v24 adds support for this feature as follows:

Added a new resource CartDataSalesView that allows segmenting conversion metrics not only by the product clicked, but also by the product sold, with segments like product_sold_brand. These enable advertisers to view statistics on the products the customers actually bought after clicking ads, even if the ad was for a different product.
Added several “all” non-biddable metrics, which are metrics that also include the conversions your campaigns are not actively optimizing towards, for example all_cost_of_goods_sold_micros. The new metrics are added to all resources supporting corresponding biddable metrics.
Added the conversion_attribution_event_type segment to the ShoppingPerformanceView resource, making it selectable with cart data and other conversion metrics. This segment denotes whether the conversion is attributed to a click or to a view and it is necessary to recognize cart data stats produced by view-through conversions.

Updated features

Version v24 introduces updates to existing features that require code changes when upgrading. We cover the most important ones here; check out the release notes for the full list of changes.

Video content exclusion settings in campaigns: We simplified the ability to set video content exclusion settings on individual campaigns. This setting is available at the customer level, and applies to all the campaigns instead. These content exclusion settings are meant to give you additional control and help you exclude types of content that, while in compliance with our policies, may not fit your brand or business. See https://support.google.com/google-ads/answer/7515513 to learn more about video content exclusion settings.

Changes to AudienceInsightsService: As part of a code refactoring, we moved the InsightsAudience.topic_audience_combinations request field into the common namespace. You may need to update your import directives in some programming languages.

Changes to ReachPlanService: As part of a code refactoring, we moved the youtube_select_lineups field from the ReachPlanService.ListPlannableProducts service. Lineups are now available within the youtube_select_lineup_targeting field. YouTube Select Lineups are reservation products for eligible clients to target among the top 1% of popular channels on YouTube with the most passionate audiences in a given market. Learn more.

Changes to ContentCreatorInsightsService: As part of a code refactoring, we removed the is_brand_connect_creator field from the ContentCreatorInsightsService.GenerateCreatorInsights and ContentCreatorInsightsService.GenerateTrendingInsights services.
Users should instead look for a creator to have the CREATOR_PARTNERSHIPS option available instead in partnership_opportunities. The YouTube Creator Partnerships in Google Ads is the space where you can find YouTube creators to partner with on sponsored content and help you efficiently manage your creator partnerships. Learn more.

Changes to KeywordPlanIdeaService: To provide a more streamlined and reliable experience, we have unified our forecasting infrastructure. Google Ads API v24 introduces an updated GenerateKeywordForecastMetrics method that simplifies the planning process by focusing on the metrics that most directly impact your performance. We will share a more detailed blog post about this change in the coming days.

Changes to campaign_budget resource: We removed the ad_sub_network_type segment for the campaign_budget resource because it is incompatible with this view.

Changes to asset views: We removed the click_type segment from the ad_group_asset, campaign_asset, and customer_asset views. This change aligns with a recent product change that removed this segment from the Google Ads to avoid misrepresentation of data. You can use the click_type segmentation from the ad_group_ad resource to get details on the ad performance and the asset it was served with.

Changes to video responsive ad: VideoResponsiveAdInfo is now mutable. As part of this change, we have marked videos, business_name and logo_images as required fields in both the DemandGenVideoResponsiveAdInfo and VideoResponsiveAdInfo objects.

Changes to ShareablePreviewService: Updated ShareablePreviewService.GenerateShareablePreviews to not use partial failure anymore. Requests will throw an error if they fail for any ID. Learn more.

The following resources can help you get started:

For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

- Anash P. Oommen, Google Ads API Team

Multi-factor authentication requirement for the Google Ads API

2026-04-17T06:41:00.000-07:00

As part of improving security for Google Ads accounts, the Google Ads API will start requiring Multi-factor authentication (MFA) for Google Ads API users. These important security updates will start rolling out from April 21, 2026, and will be enabled for all users over the next few weeks.

What is MFA?

MFA, also known as 2-step verification or 2SV, is an important security measure. In addition to your password, MFA requires another proof of identity, known as an authentication factor, to successfully sign in to an account. By requiring the second factor, you’re making it significantly harder for unauthorized users to breach your account, and a compromised password alone is not enough to gain access.

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 challenged with a second factor for authentication in addition to a username and password.

If you don’t have 2-step verification enabled, you will be prompted to add a 2-step verification method.

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 with a second factor for authentication in addition to a username and password.

What other platforms are affected by this change?

If you use Google Ads Editor, Google Ads Scripts, BigQuery Data Transfer Service or Data Studio to manage Google Ads, you will start getting challenged with a second factor for authentication in addition to a username and password. If you don’t have 2-step verification enabled, you will be prompted to add a 2-step verification method.

How can users check and enable MFA?

Users can check whether MFA is enabled for their account by opening the Security tab of their Google Account settings page. The 2-Step Verification setting is displayed in the How you sign in to Google section. If MFA isn’t enabled, follow the on-screen steps displayed in this section.

If you don't see the 2-Step Verification option for your account, your administrator might have disabled it. Contact your administrator for assistance.

Troubleshooting

Q: When I navigate to the Google Account settings page, I don’t see the 2-Step Verification option for my account.

A: If you don't see the 2-Step Verification option for your account, your administrator might have disabled it. Contact your administrator for assistance.

Q: I don’t have a 2-step verification option enabled for my account. When I attempt to sign in, I get an error that "Google couldn’t verify this account belongs to you." and I am prompted to Recover account instead of prompting me to add a 2-step verification.

A: In certain situations, Google needs additional verification before letting you add a second factor to your account. To fix the issue, navigate to the Security tab of your Google Account settings page. The 2-Step Verification setting is displayed in the How you sign in to Google section. If 2-Step Verification isn’t enabled, follow the on-screen steps displayed in this section. Wait for a few minutes and attempt signing into the Google Ads API application again.

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

- Anash P. Oommen, Google Ads API Team

Ads DevCast E3: Improving your Advertising Workflows

2026-04-16T09:51:00.000-07:00

Improving your Advertising Workflows

It’s an incredible time to be a developer in the advertising space. Innovation is moving at a breakneck pace, and we’re shifting from incremental API integrations to fundamental improvements in how technical users interact with our platforms. In the latest episode of Ads DevCast, I sat down with my colleague Matt Landers to discuss how AI is moving from "hype" to "utility," decreasing friction in development and delivering tangible business results.

The Power of Multi-Product Insights

One of the most exciting developments we’re seeing is the value of Advertising MCPs (Model Context Protocol) servers showing up. These open-standard tools allow your AI agents to interact directly with the Google Ads and Google Analytics APIs.

Historically, solving a problem like "why is my high-CTR ad not converting?" meant a lot of manual data joining between Ads and Analytics. By combining the Google Ads and Analytics MCPs, you can now perform this analysis in seconds using natural language. You can verify engagement rates, identify content mismatches on landing pages, and even suggest ROI improvements in the time it takes to brew a cup of coffee.

Efficiency and Speed with Natural Language

We’re also seeing AI make technical tasks more accessible. A great example is the recent update to our Sheets Report Builder add-on for Google Analytics 4. Previously, creating complex reports required manually adding dimensions, metrics, and filters in the UI. Now, with Gemini integrated directly into Sheets, you can simply ask, "What's my highest converting landing page?" and the tool automatically sets all the parameters in the UI, sends the API request, and imports the data for you.

The Senior Pair Programmer in Your CLI

For developers deep in the code, the Google Ads API Developer Assistant is a game-changer. Think of it as a senior pair programmer that has memorized the entire API schema and every possible error code. Whether you’re troubleshooting conversion uploads or finding hidden problems in your account, the assistant doesn’t just explain what’s wrong—it can generate, debug, and even run the fix directly in your environment.

Health, Diagnostics, and Seamless Migrations

Beyond AI-driven insights, we’re focused on improving the underlying health of your technical systems. The Data Manager API will soon feature integrated diagnostics in the UI, allowing you to track what went wrong with your integrations. Last but not least, for publishers, we’ve released a new migration skill for the AdMob SDK to help you transition between versions with the help of your coding agent.

Experiment, Fail Fast, and Build Great Things

The barrier to entry for building sophisticated, data-driven advertising solutions is dropping. By automating the busy work, you’re freed up to focus on high-impact projects that drive real business growth.

Ready to dive deeper?

Watch the full episode: goo.gle/watchadsdevcast

Listen on the go: goo.gle/listenadsdevcast

Take our Episode 3 Survey: goo.gle/adc-survey-e3

Join our Discord Community: goo.gle/ads-and-measurement-discord

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Merchant API is coming to Google Ads scripts starting April 22, 2026

2026-04-09T11:31:00.000-07:00

The Content API for Shopping will sunset on August 18, 2026, to be replaced by the Merchant API. This migration provides a shift toward more robust, scalable, and feature-rich integrations. For Google Ads scripts users, the Google Ads scripts editor will begin rolling out Merchant API support on April 22, 2026. While the Content API for Shopping will remain available until its sunset, here’s what to expect from the Merchant API.

Understanding the Merchant API

The Merchant API offers important changes and improvements over the Content API for Shopping:

Modular Design: The Merchant API is broken down into sub-APIs. This allows for:
- Faster access to new features and updates.
- Easier versioning and maintenance.
- Reduced disruption, as changes in one sub-API are less likely to impact others.
New Features & Capabilities:
- Google Product Studio API: Leverage generative AI features.
- Reviews APIs: Upload and manage product and store reviews.
- Notifications API: Enable notifications for changes.
- Expanded Data Source Management: Create and manage various data source types, including:
Omnichannel Support: Designed with Omnichannel in mind, though it provides backward compatibility for legacy separate online/local offer structures using the legacy_local flag.

Take a look at the Merchant API migration guide for more detail on the changes between APIs.

How to get started

The Merchant API will be available as an Advanced API in the Google Ads scripts editor, just as the Content API is.

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.

- Dora Sun - Google Ads API Team

New Data Manager API channels on Discord

2026-04-07T09:41:00.000-07:00

We're excited to announce the addition of new channels for the Data Manager API on our “Google Advertising and Measurement Community” Discord server. To join, just click this invite link and follow the onboarding guide.

Our team will be on this server regularly to interact with the Data Manager API community, answering questions and gathering feedback in the #data-manager-api channel. We’ll also keep you up to date on the latest Data Manager API news in the #announce-data-manager-api channel.

If you have any questions or want to discuss this post, please reach out to us on the “Google Advertising and Measurement Community” Discord server. We look forward to seeing you there and hearing your thoughts on how we can continue to improve the Data Manager API!

- Josh Radcliff, Data Manager API Team

Introducing the Google Advertising and Measurement Developers Hub!

2026-04-06T13:57:00.000-07:00

We're excited to announce the launch of the new Google Advertising and Measurement Developers Hub!

Come see the new site!

Whether you're looking to automate campaigns, analyze performance, manage tags, or monetize your apps, the new hub is designed to make it easier to find the right tools and information.

We've launched a new technical-user focused site to make it easier than ever for you to find the tools, resources, and support you need to build and innovate with Google's advertising and measurement products.

What's New?

We have created a one-stop shop where you can easily find the resources you need, connect with our team and the community, and get support. Here are some key features:

At-a-glance homepage: A clear starting point highlighting how we can help, with quick links to our blog, Discord, and information about our team.
Meet the team: Learn more about the Developer Relations team dedicated to supporting your success.
Products: A comprehensive directory of the developer products we cover, from the Google Ads API and Google Analytics APIs to Publisher Tools like AdMob and Ad Manager, linking directly to their official documentation. You can browse by categories like Advertising Platforms, Tagging, Measurement & Analytics, and Publisher Tools.
Connect with us: A streamlined page to help you find the best way to engage:
- Join our vibrant Discord community.
- Find links to product or technical support.
- Download open source projects on GitHub.
Media and podcast: A new home for our multimedia content, including the Ads DevCast playlist embedded directly on the page.

We're excited to make this the place for you to learn, build, and connect.

Please explore the new site and use the Send Feedback button located at the bottom of each page to share your thoughts!

If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Happy Building!

- Aalap Shastri, Google Ads API Team