Google Ads Developer Blog

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

Kamis, 07 Mei 2026

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

Kamis, 07 Mei 2026

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

Selasa, 05 Mei 2026

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

Jumat, 01 Mei 2026

table#dataretensionmay2026{ border-collapse: collapse; } table#dataretensionmay2026 td { border: 1px solid grey; padding:5px; } 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

Kamis, 30 April 2026

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

Rabu, 29 April 2026

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:

Upgrade to the newest version

Release notes

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.

(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

Kamis, 23 April 2026

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

Ads Developer Blog