Google Ads Developer Blog

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

joi, 28 mai 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

joi, 28 mai 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

miercuri, 27 mai 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

miercuri, 27 mai 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

joi, 21 mai 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

vineri, 15 mai 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

joi, 14 mai 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

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

Etichete

Archive