Google Ads Developer Blog: tháng 5 2026

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

Thứ Năm, 28 tháng 5, 2026

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:

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

The “What” and “Why” on Meridian: Ads DevCast E6

Thứ Năm, 28 tháng 5, 2026

Measuring the true impact of your marketing spend is complex, especially when you look across channels and mediums. In Episode 6 of Google’s Ads DevCast, "The 'What' and 'Why' on Meridian," we sit down with Product Manager Katie Munro and Developer Relations Engineer Jeff Li to explore Meridian, Google's open-source Marketing Mix Modeling (MMM) framework, and how it helps advertisers make data-backed strategic budget decisions. Watch the full episode Hear the full episode Here is a summary of the talking points from our discussion on what Meridian is, how the math works, and the newly announced surfaces to help you implement it. What is Meridian? Meridian is Google's open-source Marketing Mix Modeling (MMM) framework. It provides a holistic, privacy-safe view of marketing ROI by analyzing aggregated historical data across all channels (digital, TV, print) alongside non-advertising factors (seasonality, economic conditions). It helps you determine the incremental lift of your marketing (sales caused by ads) versus baseline sales (sales that would have happened anyway). The Core Math: Hill Curves & Adstock Meridian uses statistical models to capture the real-world behavior of advertising:

Hill Curves: Models diminishing returns, showing where you have room to increase spend (headroom) and where you have saturated a channel.

Adstock: Models the lagged effect and decay of advertising over time, capturing the delay between seeing an ad and making a purchase.

The Measurement Trifecta Meridian completes the modern measurement framework:

Attribution (GA4): For day-to-day tactical campaign tweaks.

Incrementality Experiments (Meridian GeoX): To test specific hypotheses in the real world.

MMM (Meridian): For macro-level, strategic budget planning.

New Meridian Releases from GML 2026 We discuss three major additions designed to make MMM more accessible and accurate:

Meridian in GA360: A turnkey, integrated MMM solution within Google Analytics 360 that uses existing behavioral data to provide cross-channel ROI insights without requiring a data science background.

Meridian Studio: A Google Cloud-based enterprise platform to build and scale models, featuring native agentic AI to automate data quality checks, suggest model health improvements, and assist in scenario planning.

Meridian GeoX: An open-source geo-based incrementality solution that acts as a calibration engine, allowing you to run geographic experiments and feed "ground truth" causation data back into your Meridian model.

Next Steps:

Watch the full episode on YouTube (or listen to it)

Try Meridian: https://goo.gle/try-meridian

Try Meridian Studio: https://goo.gle/try-meridian-studio

Try Meridian GeoX: https://goo.gle/try-meridian-geox

Check out the Meridian Developers website to read the documentation.

Join our developer community on Discord to ask questions and discuss.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Display & Video 360 API will start supporting Demand Gen resources on June 10, 2026

Thứ Tư, 27 tháng 5, 2026

Today we’re announcing the upcoming rollout of Demand Gen resource support to all Display & Video 360 API users starting on June 10, 2026. This feature will be rolled out to Display & Video 360 partners over two weeks. By June 24, the feature will be available to all partners. Ahead of June 10, verify that your API integration can handle the additional Demand Gen line items and ad groups that will be included in list responses once the feature is rolled out to your partner. What’s changing? Originally launched in closed beta on April 14, 2026, Demand Gen resource support includes management and retrieval capabilities for Demand Gen resources and their targeting. Demand Gen resources include the following:

LineItem resources with a lineItemType field value of LINE_ITEM_TYPE_DEMAND_GEN.

AdGroup resources with an adGroupFormat field value of AD_GROUP_FORMAT_DEMAND_GEN.

AdGroupAd resources using any of the following fields: demandGenVideoAd, demandGenImageAd, demandGenCarouselAd, demandGenProductAd. Demand Gen AdGroupAd resources are retrievable using Display & Video 360 API currently, but these fields will not be included in the retrieved object until full support is rolled out to your partner.

After these features are rolled out to your partner, the API will support get, create, delete, and patch requests for these resources. In addition, these resources will be included in advertisers.lineItems.list and advertisers.adGroups.list responses, alongside the line items and ad groups that are already supported. What actions do I need to take? If you are currently retrieving LineItem and AdGroup resources using advertisers.lineItems.list and advertisers.adGroups.list, update your integration by June 10, 2026 to support the Demand Gen resources that will be included in responses once the features are rolled out to your partner. The other features included in this rollout add support for Demand Gen resources that are explicitly identified when using new or existing methods. These changes only impact requests that would have previously returned an error, so no changes should be needed beforehand to ensure the stability of your integration. Once the features are rolled out to all partners after June 24, 2026, you can start explicitly retrieving, creating, and updating Demand Gen resources. See our existing guide for step-by-step instructions on how to begin serving Demand Gen ads using the Display & Video 360 API. We will make another announcement once this rollout begins. 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

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

Thứ Tư, 27 tháng 5, 2026

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

Thứ Năm, 21 tháng 5, 2026

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

Thứ Sáu, 15 tháng 5, 2026

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

Thứ Năm, 14 tháng 5, 2026

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

Thứ Tư, 13 tháng 5, 2026

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:

Release Notes

Upgrade from a previous version

Guides

Reference

Diff between v24 and v23

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

Thứ Năm, 7 tháng 5, 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

Thứ Năm, 7 tháng 5, 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

Thứ Ba, 5 tháng 5, 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

Thứ Sáu, 1 tháng 5, 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

Ads Developer Blog

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

The “What” and “Why” on Meridian: Ads DevCast E6

Display & Video 360 API will start supporting Demand Gen resources on June 10, 2026

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

Ads DevCast: Google Marketing Live 2026 bonus episode

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

Announcing expanded experiment functionality in Google Ads API v24.1

Announcing v24.1 of the Google Ads API

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

Managing your integrations at scale: Ads DevCast E4

Introducing Partial Structured Data File Upload

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

Nhãn

Archive