Google Ads Developer Blog

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 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

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

Introducing Partial Structured Data File Upload

2026-05-05T11:04:00.000-07:00

Today we’re introducing Partial Structured Data File Upload to Display & Video 360! This new capability allows you to upload Line Item Structured Data Files (SDFs) that only include certain subsets of columns.

Standard Line Item Structured Data Files require the inclusion of over 120 columns to support a wide breadth of Display & Video 360 settings. Partial SDFs let you only include settings that you want to update, making the files smaller and easier to manage. The reduced size of partial SDFs enables:

A higher overall resource limit for a single file.
Faster file uploads and resource updates.
Reduced risk of unintended changes to other line item settings.

Partial SDFs are uploaded using the Display & Video 360 UI, the same as you would upload a standard SDF. No additional enrollment or configuration is required. See the Partial SDF Upload guide to learn which SDF columns are currently supported and download sample files to get started.

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.

- Trevor Mulchay, Display & Video 360 API 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

April 2026 update to Display & Video 360 API

2026-04-14T09:42:00.000-07:00

Today we’re announcing the April 2026 update to the Display & Video 360 API. This update includes the following:

Support for additional Exchange and ThirdPartyVendor values.
AdAsset identifier fields in objects used in AdGroupAd resources.
Beta support for Demand Gen resource management.

While Demand Gen campaign support is in beta, it is only available to allowlisted customers. See our guide for detailed instructions on how to create a Demand Gen ad campaign. If your partner is allowlisted:

Demand Gen line items, ad groups, and the relevant targeting will be included in relevant get and list requests.
Demand Gen line items, ad groups, ads, and the relevant targeting can be created, deleted, and updated.

We aim to launch full Demand Gen support for the Display & Video 360 API in general availability later this year. This will be announced with a future release.

For a complete list of new features in this update, see the Display & Video 360 API release notes. Before using these 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.

- Trevor Mulchay, Display & Video 360 API 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

Ads DevCast Episode 2: Audience Management

2026-04-02T08:10:00.000-07:00

Many to 1, Audience Management in Data Manager API

In today's fast-paced digital landscape, managing multiple data pipelines can feel overwhelming. If you're a developer navigating the complexities of audience management and conversion tracking, you might be wondering: how can I streamline my processes and reduce costs?

This week’s episode of Ads DevCast explores the new Data Manager API, which will transform the way you connect data across various Google ad platforms, making your workflows more efficient and cost-effective. This product solves many of the complexities developers and agencies have had to juggle across multiple APIs—each with its own schema, maintenance requirements, and learning curve.

Click here to watch the episode: https://youtu.be/Z4mAR98cizQ

About our Guest

In this episode we sit down with Melissa Ng, Product Manager for Data Manager API, to discuss how Google is streamlining these processes and what it means for your development workflow.

Melissa is a seasoned Product Manager, specializing in ads measurement at Google for the past four years. Her deep understanding of customer needs and data management challenges drives her passion for creating innovative solutions like the Data Manager API.

What are we solving for?

Every advertising product has its own unique requirements that aren't necessarily interoperable. This fragmentation creates confusion, slows down onboarding, and drives up engineering costs. It also makes it difficult to build the kind of cohesive "Data Strength" needed to fuel modern advertising and maximize conversions.

In a joint case study, one of our advertisers reported spending over $1 million annually on maintenance alone. We needed to provide a unified ingestion point for conversions and audiences, effectively reducing confusion and simplifying data management.

Enter the Data Manager API

The Data Manager API is Google's answer to this complexity. It allows data partners, agencies, and advertisers to send first-party data to multiple Google advertising products—such as Google Ads, Display & Video 360, Campaign Manager 360, Google Analytics, and others—in a single call.

"This means that when you’re sending in a field for, say, 'transaction id', that field means the same thing in all of the downstream use cases across all of the Google advertising products," explains Melissa in the episode.

While the primary motivation behind developing the Data Manager API was to address complexities associated with maintaining multiple APIs, there are other benefits as well:

Ease of Use and Efficiency at Scale: You can achieve significant savings in resources. Treasure Data, one of our early API integration partners, reported a 2x faster advertiser onboarding process and an 80% reduction in engineering efforts.

Privacy by Default: End-user privacy is non-negotiable. The Data Manager API features confidential matching right out of the box for audience solutions like Customer Match. This utilizes a Trusted Execution Environment (TEE) to ensure that no one—not even Google—can view the processed data. (Read more)

Future-Proofing Your Stack: The Data Manager API is the future of audience and conversion management. Any new features for audience or conversion management will be implemented in the Data Manager API going forward. (See our timelines)

Enhanced Diagnostics: For the first time, API stats and diagnostics will soon be available directly in the Ads UI, providing visibility into the health of your connections and downstream asynchronous errors, saving you countless hours of troubleshooting.

Tune In and Take Action

If you are managing audiences or conversions programmatically, this episode is a must-listen. It is packed with insights, roadmap updates, and advice on how to seamlessly migrate your existing systems.

Listen to the full episode of the Ads DevCast here!

Ready to get started with the Data Manager API?

Start your upgrade today: Dive into the step-by-step tutorials and upgrade guides.
Join the community: Connect with us and other developers on our Discord server.
Share your feedback: We want to hear from you! Let us know what features you want to see next by filling out our Episode Survey. Reminder, this show is a pilot, and your feedback is important so we can tailor our content to what is most useful for you.

Thanks for tuning in! We'll see you in two weeks for Episode 3.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

New Google Ad Manager API read-only scope

2026-03-27T13:55:00.000-07:00

The Ad Manager API now supports a read-only OAuth scope. This new scope, https://www.googleapis.com/auth/admanager.readonly, allows developers to request read-only access to their users' Ad Manager data.

This new scope is only available for the Ad Manager API. It is not supported by the legacy Ad Manager SOAP API, which will continue to require the full-access scope.

The read-only scope allows reading data and running reports, but does not grant permission to write or modify data. This provides an enhanced security layer for developers and users of read-only integrations, such as reporting dashboards or alerting tools.

No action is required for existing integrations. If your application does not require write access, we recommend migrating to the new read-only scope. For a refresher on how to configure OAuth, see Using Oauth 2.0 for Web Server Authentication.

As always, Ad Manager access controls, including User roles and Restrictions imposed by teams, are applied to all API requests regardless of the OAuth scope used.

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

- Chris Seeley, Ad Manager API Team

Increase in Batch Job Service Request Size

2026-03-27T10:57:00.000-07:00

Increased Request Limits for BatchJobService Enhance Large Asset Uploads

We're pleased to announce significant increases to the request size limits for the BatchJobService.AddBatchJobOperations method in the Google Ads API. These changes are designed to streamline workflows, particularly for developers uploading multiple large assets like images, by reducing the need to split uploads into numerous smaller requests.

The following limits have been increased:

Request Size Cap on AddBatchJobOperations: Increased from 10,484,488 bytes (approximately 10.48 MB) to 41,937,920 bytes (approximately 41.94 MB).

Single Mutate Operation Size: While the overall request can be larger, the size of a single mutate operation within the batch is capped at 10,484,488 bytes (approximately 10.48 MB).

What This Means for Developers:

This update allows you to include more operations, especially those containing sizable data like image assets, within a single AddBatchJobOperations request. This can simplify your client-side logic and potentially improve throughput by reducing the number of round trips required to add all operations to a batch job.

For example, when uploading multiple images, each of which can be up to 5,242,880 bytes (approximately 5.24 MB), you can now batch more of these into a single request, up to the new 41,937,920 bytes (approximately 41.94 MB) total request limit.

Important Notes:

While the request size limit has increased, other limitations such as the maximum number of operations per request (10,000) and per job (1 million) still apply. Please refer to the Best Practices and Limitations guide for full details.

We believe this enhancement to the BatchJobService will offer greater flexibility and efficiency for managing bulk operations in the Google Ads API.

As always, please reach out to us via the forum or our other support channels if you have any questions or feedback.

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.

Bob Hancock, Google Ads API Team

Upcoming Improvements to Offline Conversion Imports

2026-03-26T09:25:00.000-07:00

Starting in April, 2026 the Google Ads API will benefit from a series of infrastructure changes designed to improve the Offline Conversion Import experience. These upgrades will not result in any breaking changes to the Google Ads API, however there may be minor fluctuations in attribution rates as the changes are rolled out.

Here is a breakdown of the rollout and the improvements you can expect:

Improved attribution and fallback recovery (April, 2026): We will implement changes allowing us to attribute some expired GCLIDs and clicks that occurred before a conversion. Once deployed, you may receive fewer EXPIRED_EVENT and CONVERSION_PRECEDES_EVENT errors in conversion upload responses, and you may notice higher attribution rates.
Flexible import requests (April - May, 2026): We will improve the authorization structure for conversion import requests to make it easier for manager or client accounts to import conversions on behalf of a different trafficking account. Once released, users should expect a reduction in UNAUTHORIZED_CUSTOMER and INVALID_CUSTOMER_FOR_CLICK errors in conversion import responses. This may also result in an increase in attribution.

Make sure to review our guidance on how to maximize the performance of your Google Ads conversion data. And take a look at the Data Manager API, including our migration guide for Google Ads API users.

Reach out to the Google Ads API support channel if you have any questions. And 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 v23.2 of the Google Ads API

2026-03-25T14:59:00.000-07:00

Today, we’re announcing the v23.2 release of the Google Ads API. To use the new v23.2 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 or on our Ads Developers YouTube Live tomorrow (March 26th at 11a 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.

Here are some of the key features in this release:

Added the VideoEnhancement resource with enhancement-specific video ad information, such as whether it's Google-generated or advertiser-provided. See the About video enhancements to learn more.
Added the AppTopCombinationView read-only resource to provide insights into top-performing asset combinations in App campaigns.
Added HotelSettingInfo.disable_hotel_setting to allow disabling the hotel feed in Demand Gen campaigns.
Added the biddable_indirect_install_first_in_app_conversion_micros metric to Campaign, Customer, and AdGroup resources.
Added several enhancements to ContentCreatorInsightsService and ReachPlanService. Learn more.

Where can I learn more?

The following resources can help you get started:

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

- Anash P. Oommen, Google Ads API Team

Announcing new Display & Video 360 API Discord channels and a documentation update!

2026-03-23T10:04:00.000-07:00

Today we’re announcing two huge improvements for Display & Video 360 bulk tools.

First, we are launching support for Display & Video 360 API, Structured Data Files, and Bid Manager API products in the existing “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 Display & Video 360 community, answering questions and responding to feedback. We’ll also let you know what’s new with our products in the #announce-display-video-360 channel.

Second, we have made a significant update to the Display & Video 360 API and Structured Data Files documentation. The updated site is designed to make it easier to learn how to perform common tasks with Task guides, browse important conceptual information with Concept guides, and review reference material with updated navigation that highlights currently-supported versions and features of the API and Structured Data Files.

If you have feedback on these changes or the content of any of the guides, please click the Send Feedback button at the bottom of any page in the documentation.

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

- Trevor Mulchay, Display & Video 360 API Team

Introducing: Ads DevCast

2026-03-20T08:24:00.000-07:00

A new podcast for the ads technical community

We are thrilled to announce the launch of Ads DevCast, a new bi-weekly vodcast and podcast series brought to you by Google’s Advertising and Measurement Developer Relations team.

Hosted by Developer Relations Engineer Cory Liseno, this show is dedicated to deep dives into our latest technical updates, insights from the engineers building our tools, and expert discussions on products like Google Ads, Google Analytics, Display & Video 360, Meridian, and more.

While you might already be familiar with the Ads Decoded podcast — where Ginny Marvin does a fantastic job bridging the gap for marketing teams on campaign strategy — Ads DevCast is built specifically for builders and developers.

You can tune in on our Google Ads Developers YouTube channel or find the podcast on Google Ads Developers in YouTube Music.

Episode 1: MCPs, Agents, and Ads. Oh My!

In our premiere episode, we explore the "agentic shift" currently reshaping the advertising landscape. We’re seeing a world where agents, not just humans, are becoming primary consumers of our APIs. To help you stay ahead, we’ve released several tools designed to make your integrations smarter, faster, and more accessible.

Getting Smarter with MCP Servers

One of the covered topics is Model Context Protocol (MCP), and how it allows your agents like Gemini CLI to securely access your data.

We’ve recently released open source, self-hosted MCP servers for the Google Ads API and Google Analytics API. These tools allow you to ask natural language questions directly to your agent, such as:

"What are my active campaigns?"
"Which properties had the highest traffic yesterday?"
"What are my top-selling products over the last month?"

The real magic happens when you combine this data with generative power. In the episode, we discuss how you can use the Analytics MCP to not only pull reports but then ask Gemini to generate a data-justified marketing plan based on those specific results.

Moving Faster with the Developer Assistant

Technical speed is another major focus. To reduce the time spent digging through documentation, we’ve launched the Google Ads API Developer Assistant. This Gemini CLI extension allows you to use natural language to generate, debug, and even test-run integration code.

In one real-world test, we used the assistant to solve a complex reporting issue regarding policy disapprovals. What would normally take days of back-and-forth with email support was resolved by the assistant in minutes, providing the exact GAQL query needed to get the job done.

Improving Accessibility

AI tooling is also changing who can interact with our technical systems. We’re seeing a shift from the "Ads Developer Community" to a broader "Ads Technical Community." Marketing power users are now leveraging MCP servers to perform real-time data operations without waiting for a full development lifecycle. This frees up engineering teams to focus on high-impact "blue sky" projects while giving marketers the agility they need.

We want to hear from you

This show is a pilot, and your feedback is important so we can tailor our content to what is most useful for you. Please take a moment to fill out our Episode 1 Survey and let us know what topics you want us to cover next.

Be sure to also join our Discord Community where you can join the conversation with Googlers and fellow developers.

Thanks for tuning in! We'll see you in two weeks for Episode 2.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Upcoming changes to Lookalike user lists in the Google Ads API, starting April 30, 2026

2026-03-19T11:03:00.000-07:00

Google Ads is committed to providing a reliable and efficient environment for all advertisers. To ensure that our systems remain stable and that resources are allocated fairly, we are introducing a uniqueness check for Lookalike user lists that prevents the creation of duplicate lists. These changes primarily impact Demand Gen campaigns and will begin to be enforced starting on April 30, 2026.

A Lookalike user list is considered a duplicate if it shares all of the following attributes with an existing list:

Seed lists: The underlying source audiences used to build the Lookalike.
Expansion level: The degree of similarity to the seed lists.
Country targeting: The geographical reach of the Lookalike list.

If an advertiser attempts to create a duplicate list after April 30, 2026, the Google Ads API will return the error code DUPLICATE_LOOKALIKE for v24 and beyond. For earlier versions, the error will be RESOURCE_ALREADY_EXISTS.

What this means for you

For the majority of advertisers, these changes will go unnoticed, as most current usage falls well within these new boundaries. However, to ensure a smooth transition, we recommend the following:

Reuse audiences: Instead of creating a new, identical Lookalike list, verify if an existing one with the same configuration can be reused in your campaigns.
Update error handling: If you use the Google Ads API, ensure your integrations are prepared to handle the new error starting on April 30, 2026: v24 will return the DUPLICATE_LOOKALIKE error code and all previous versions will return RESOURCE_ALREADY_EXISTS.

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