Google Ads Developer Blog

Accelerate Google Ads API Basic Access reviews with brand verification

2026-07-07T04:54:04.598-07:00

Today, we are launching a pilot process to expedite the Basic Access application review process. If you have a pending Basic Access application for your Google Ads API developer token, then you can complete brand verification for your Google Cloud project to expedite the reviews for your pending application. With this launch, we aim to reduce the review delays and better meet the significant interest from our developer community for Google Ads API access.

What is brand verification?

Brand verification provides a way for an application developer to verify that they accurately represent their identity and intent as specified by Google API Services User Data Policy. Brand verification is part of the OAuth App verification process, and is an automated self-service option for most developers.

How do I expedite the review process?

If you have a pending Basic Access application for your developer token, then follow these instructions to expedite the review process:

Associate your developer token to your Google Cloud project. This step is important; without it we won’t know which Google Cloud project to use as part of the review process.
Complete brand verification for your Google Cloud project. If you completed brand verification for your Google Cloud project in the past while using another Google API, you don’t need to repeat the process. If you have more than one Google Cloud project associated with your developer token, you need to complete brand verification only for one project.

Once your Google Cloud project is brand verified, your pending Basic Access application will be reviewed in the next few hours.

Is brand verification mandatory?

Currently, brand verification is optional and is used only as a signal for faster determination of Ads API Basic Access eligibility. This means that

You may complete the Brand verification process for your Google Cloud project to expedite the review process for your Basic Access application.
The Google Ads API Compliance team may request some developers with pending Basic Access applications to complete brand verification.

You don’t need to complete brand verification if you already have an approved developer token and aren’t newly applying for Basic Access level.

We will closely monitor the developer experience throughout pilot surveys and use that data to determine the future changes to the application review process for developer token access levels.

- Anash P. Oommen, Google Ads API Team

Announcing Google Mobile Ads Next-Gen SDK as the preferred SDK for Android

2026-07-06T14:14:52.625-07:00

Google Mobile Ads (GMA) Next-Gen SDK is now the preferred SDK for Android development with Google AdMob and Google Ad Manager. GMA Next-Gen SDK is a significant rewrite of Google Mobile Ads SDK that improves speed, stability, and the developer experience. Google Mobile Ads SDK for Android is now legacy.

We invite you to integrate GMA Next-Gen SDK and discover the performance and stability enhancements it can bring to your Android applications. To get started today, migrate to GMA Next-Gen SDK in AdMob and Ad Manager.

Deprecation of Google Mobile Ads SDK (legacy)

Google Mobile Ads SDK (legacy) versions 25.x.x are now considered outdated by GMA Next-Gen SDK. Version 25.x.x follows a similar deprecation schedule, as previous major versions. See the following timeline for support of Google Mobile Ads SDK (legacy) version 25.x.x:

Date	Google Mobile Ads SDK (legacy) status
July 1, 2026	Supported Ads continue to serve. Technical support is available through the contact us form.
June 30, 2027	Deprecated Ads continue to serve. Technical support is no longer available.
June 30, 2028	Sunset Ads are at risk of not serving. Google Mobile Ads SDK (legacy) is reported as outdated and prevents app releases.

For more information about the deprecation timelines and definitions, see the deprecation schedule.

Migrate with an AI skill

We recently introduced agent skills, including a google-mobile-ads-android-migrate-to-next-gen skill to help you migrate your app from Google Mobile Ads SDK (legacy) to GMA Next-Gen SDK.

For details about migrating to GMA Next-Gen SDK with AI, see Migrate with AI tools.

Additional Resources

Integration guide: The latest version and setup instructions are available in our Set up GMA Next-Gen SDK guide in AdMob and Ad Manager.
Migration guide: Instructions to migrate to GMA-Next Gen SDK in AdMob and Ad Manager.
Developer samples: Example applications are available in the gma-next-gen-sdk-android-examples GitHub repository.

If you have any questions or need additional help, contact SDK support. To discuss this post or engage in community discussion, join the GMA Next-Gen SDK channel on our Discord server to share your thoughts.

- Natalia Vargas-Caba, Mobile Ads Developer Relations

Deprecating Structured Data Files v9, v9.1, and v9.2

2026-06-29T10:13:44.257-07:00

Today we’re announcing the deprecation of Structured Data Files v9, v9.1, and v9.2. These three versions will all sunset on January 28, 2027.

Migrate to v10 or higher before the sunset date to avoid any interruption of service. Follow the steps in the SDF v10 Migration Guide to update your settings to use the new version. Use the enumerated schema differences between every deprecated version and v10 listed in the migration guide to update your integration.

After January 28, 2027, the following changes will apply to all users:

The default version of partners and advertisers that use v9, v9.1, or v9.2 will be updated to v10.
sdfdownloadtasks.create requests using SDF_VERSION_9, SDF_VERSION_9_1, or SDF_VERSION_9_2 in the request body will return a 400 error.

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

July 2026 changes for Display & Video 360 API and Structured Data Files

2026-06-26T09:41:18.452-07:00

Today we’re announcing two unversioned changes to the Display & Video 360 API and Structured Data Files that will take effect on July 13, 2026 and may impact your existing integrations.

The following changes have been fully detailed on our Announced Deprecations page:

The third-party vendor Nielsen will no longer be assignable as a third-party brand lift vendor.
If left unset, default business name and logo values will begin being inherited by Demand Gen and YouTube responsive ads.

If you believe any of these changes will impact your integrations, follow the recommended actions in the change description.

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

Unlocking Data Strength with Data Manager API: Ads DevCast E7

2026-06-26T08:26:33.112-07:00

We are thrilled to share the newest episode of Ads DevCast, the podcast series brought to you by Google’s Ads Developer Relations team.

This episode features a conversation with Data Manager PMs Xuezhu Li and Stephen Chang on unlocking data strength using the Data Manager API.

Watch it: goo.gle/watchadsdevcast

Hear it: goo.gle/listenadsdevcast

Streamlining Ingestion: Send Once, Fan Out Everywhere

Ingesting first-party signals into disparate advertising and measurement platforms has historically required building and maintaining separate, asynchronous ingestion pipelines. In this episode, Xuezhu explains how the Data Manager API introduces a "send once, fan out everywhere" architecture. You push your first-party data in one time, and the system seamlessly routes and distributes it across whichever destinations you choose, such as: CM360, DV360, SA360, and GA4.

Effortless Pipeline Monitoring with the Status API

For developers managing high-volume ingestion pipelines, tracking execution health is critical. The episode explores the new Status API — a dedicated request-tracking service that lets you monitor pipeline health using a simple request ID. Instead of digging through legacy multi-step offline queries, you get unified status checks with aggregated row-level error reporting.

Built-In Privacy & Confidential Compute

The Data Manager API is built from the ground up to keep sensitive user signals secure. That’s why it provides Confidential Match. Confidential Match relies on Confidential Compute, utilizing hardware-isolated Trusted Execution Environments (TEEs) to ensure your data remains completely locked down even during active processing.

Four Reasons to Adopt & Engineering Best Practices

Stephen and Xuezhu break down the four core reasons to adopt the Data Manager API today:

Performance
Privacy
New Features
Developer Experience

We Want to Hear From You

Your feedback is vital to help us tailor future episodes. Please take a minute to share your thoughts at our Episode Survey. Be sure to subscribe on YouTube and join our Discord community to keep the conversation going!

If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Developers Community” Discord server. Also follow our new Google Advertising and Measurement Developers” LinkedIn page.

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

Google Ads API v21 sunset reminder

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

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

Here are some resources to help you with the migration:

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

Open APIs & Services in the Google Cloud Console.
Click Google Ads API in the table.
On the Metrics subtab, you should see your recent requests plotted on each graph. You can see which methods you've sent requests to in the Methods table. The method name includes a Google Ads API version, a service, and a method name, such as
```
google.ads.googleads.v21.services.GoogleAdsService.Mutate.
```
(Optional) Choose the timeframe you want to view for your requests.

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

Ben Karl

Google’s Advertising and Measurement Developer Relations team

Multi-party approvals in the Google Ads API

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

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

What is changing?

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

Inviting a user

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

Updating or terminating a user’s access

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

How do I approve a multi-party approval request?

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

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

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

What do I need to do?

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

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

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

- Anash P. Oommen, Google Ads API Team

Announcing v24.2 of the Google Ads API

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

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

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

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord or our Ads Developers YouTube Live tomorrow (June 25th at 10a ET). This will also be recorded and posted on YouTube for those who can’t make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

New Features

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

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

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

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

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

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

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

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

Documentation updates

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

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

Getting Started

Google Ads API v24.2 is a drop-in upgrade for v24.1. If you use our client libraries, download the latest version of your client library to start using these features. For a full list of changes, please review the official release notes. For technical support issues, reach out to https://support.google.com/google-ads/contact/google_ads_api

- Anash P. Oommen, Google Ads API Team

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

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

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

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

What are Agent Skills?

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

How do Agent Skills work?

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

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

Why Agent Skills?

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

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

Implement Google ads with core skills

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

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

How to install ads agent skills

You can discover and install these skills using npx:

npx skills add google/skills/skills/ads

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

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

npx skills update

Share your feedback

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

- Justin Malandruccolo, Mobile Ads Developer Relations

Changes to Support for Smart Campaigns in the Google Ads API

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

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

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

Technical details

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

For technical support issues, please reach out to Google Ads API Support. If you have any questions or want to discuss this post, please reach out to us on our “Google Advertising and Measurement Community” Discord server.

Ben Karl

Google’s Advertising and Measurement Developer Relations team

Updates to Smart Bidding Strategy Naming and Organization in Google Ads

2026-06-16T07:04:10.570-07:00

Starting in June 2026, Google Ads is updating how bidding strategies are labeled to offer greater clarity between volume-focused and target-focused goals.

As part of this update, we are decoupling Target CPA and Target ROAS from Maximize conversions and Maximize conversion value, reverting them to their previous, distinct standalone naming conventions

Information for Developers and Google Ads API Users

For developers managing Google Ads accounts programmatically using the Google Ads API, these changes align the UI experience with specific API strategy types.

API Strategy Types

Campaigns optimizing for a target will focus on achieving that stated target rather than maximizing volume by internally lowering bids when budgets become constrained. To support this distinction, standalone TARGET_CPA and TARGET_ROAS concepts are being prioritized over bundled Maximize strategies with optional targets for applicable campaign types (such as Search campaigns).

What you should do:

Review Integrations: Make sure your applications and custom dashboards correctly parse and display the standalone TARGET_CPA and TARGET_ROAS strategy designations.
Campaign Creation Logic: When you create new campaigns using the API, evaluate your logic for setting optional targets on MAXIMIZE_CONVERSIONS or MAXIMIZE_CONVERSION_VALUE versus using standalone target strategies where applicable.
Monitor Releases: Continue to monitor Google Ads API release notes and documentation. Specifically, look for updates on the BiddingStrategyType enum, the reintroduction and usage of standalone TargetCpa and TargetRoas messages, and any deprecation or changes to the optional target_cpa and target_roas fields within the MaximizeConversions and MaximizeConversionValue messages for Search campaigns.

What is changing?

The following bidding strategy labels are changing in the Google Ads user interface:

"Maximize conversions with a Target CPA" is changing to "Target CPA"
"Maximize conversion value with a Target ROAS" is changing to "Target ROAS"

Maximize Conversions and Maximize Conversion Value will remain available as distinct options for advertisers looking to maximize volume within a given budget without specifying a particular target.

What is NOT changing?

Note that the underlying bidding behavior remains exactly the same. This is strictly a labeling and organizational update.

There is no impact on campaign performance or bidding logic.
The transition requires no action in your accounts for campaigns to continue bidding as expected.

For more background on how these strategies operate and are managed, refer to the following resources:

If you have questions about these upcoming changes, please reach out via our developer forum or standard support channels.

- Aalap Shastri, Google Ads API Team

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

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

What is changing?

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

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

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

What is the DSA Migration?

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

Why is this changing?

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

How to Prepare

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

Step 1: Audit Your Accounts

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

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

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

Step 2: Begin Side-by-Side Testing

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

Step 3: Utilize Voluntary Upgrade Tools

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

The Updated Transition Timeline

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

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

Bob Hancock, Google Ads API Team

Introducing the Google Ads API Developer Assistant v3.0.0

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

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

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

What’s new in v3.0.0?

1. Powered by the Antigravity framework

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

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

2. A modular, skills-based architecture

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

Key updates in this modular transition include:

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

3. Enhanced consistency & rigor

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

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

4. Developer Experience (DX) improvements

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

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

Why should you upgrade?

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

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

Get started

First installation

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

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

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

Upgrade from v2.x

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

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

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

Bob Hancock, Google Ads API Team

June 2026 update to the Display & Video 360 API

2026-06-10T07:04:55.534-07:00

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

Support for Structured Data Files v10.
Introduction of new AudioContentType, Exchange, and GeoRegionType values.
Support for YouTube Channel Pack targeting, available only to Demand Gen resources.

This launch also marks the beginning of the Demand Gen support rollout to all Display & Video 360 API users. API support for Demand Gen resources will gradually rollout to all Display & Video 360 partners over the next two weeks. After June 24, 2026, all partners will be able to retrieve, create, and update Demand Gen resources. See our guide for step-by-step instructions on how to build Demand Gen campaigns once support is rolled out to your partner.

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

Toggle on the Google Mobile Ads Next-Gen SDK in your Unity apps

2026-06-08T14:56:16.165-07:00

We are thrilled to announce the Google Mobile Ads (GMA) Next-Gen SDK for Android is now officially available for Unity developers.

Upgrading to GMA Next-Gen SDK for Android offers the following benefits:

Faster performance:
- Up to 27% faster ad request latency for banner ads than the previous version.
- Smaller size on device than the previous SDK.
- Starts in the background to minimize impact on app startup.
Enhanced stability: GMA Next-Gen SDK removes remote procedure calls (RPCs), which reduces latency and decreases crash risk due to process communication failures.
Supports all ad formats: Supports all existing Google Mobile Ads formats. For details, see Select an ad format.
The future of Android ads with AdMob: All new development for Android exclusively targets the Next-Gen SDK

One-click upgrade with GMA Unity plugin 11.1.0

GMA Unity plugin version 11.1.0 added a built-in setting to upgrade in GMA Next-Gen SDK instantly:

Navigate to Assets > Google Mobile Ads > Settings within the Unity Editor.
Locate the "Switch Google Mobile Ads Android architecture" setting and select "Upgrade to the GMA Next-Gen SDK".

That's all it takes! Your Android builds are now powered by the Next-Gen SDK.

To get started with the Next-Gen SDK, read the Install GMA Next-Gen SDK developer guide. To comment on this blog post or engage with fellow developers, join the "Google Advertising and Measurement Community" Discord server and share your thoughts on the #gma-next-gen-sdk channel.

- Nicholas Ventimiglia, Mobile Ads Developer Relations

Launching Structured Data Files v10

2026-06-02T12:45:40.810-07:00

Today we’re announcing the general availability of Structured Data Files v10. All users can now use v10 when downloading and uploading SDFs in the Display & Video 360 interface.

SDF v10 includes the following changes to file formats:

Support for CTV targeting in Line Item file entries and regional location list targeting for Ad Group file entries.
New and updated options for the Audio Content Type Targeting column in the Line Item file format.
Removal of Campaign and Insertion Order file targeting columns deprecated in January 2026.
Removal of three Line Item file columns only applicable to Video Sequence line item entries.

See the release notes for the details on the changes in v10 and follow the instructions in our migration guide to migrate to v10 from any available version.

In addition to v10, check out the new Partial Structured Data File Upload feature for an easier, more efficient way to upload Line Item files.

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

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

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

Google Marketing Platform event ingestion

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

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

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

Composite data & IP ingestion for Google Ads Customer Match

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

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

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

Get started

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

If you have any questions or want to discuss this post, please reach out to us on our "Google Advertising and Measurement Community" Discord server. You can also contact us through the support page if you have an issue or need help with the API.

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

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

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

2026-05-28T07:06:38.948-07:00

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

2026-05-27T12:35:52.672-07:00

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

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

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

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

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

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

Required actions

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

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

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

“Google Advertising and Measurement Community” Discord server.

Mattia Tommasone

Google’s Advertising and Measurement Developer Relations team

Ads DevCast: Google Marketing Live 2026 bonus episode

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

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

Watch it at goo.gle/watchadsdevcast

Hear it at goo.gle/listenadsdevcast

Key Highlights from the Episode

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

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

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

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

Cory Liseno

Google’s Advertising and Measurement Developer Relations team

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

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

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

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

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

Technical details

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

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

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

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

Announcing expanded experiment functionality in Google Ads API v24.1

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

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

Direct experiment reporting

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

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

New experiment types

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

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

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

Where can I learn more?

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

- Laura Chevalier, Google Ads API Team

Announcing v24.1 of the Google Ads API

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

Today, we’re announcing the v24.1 release of the Google Ads API. To use the new v24.1 features, you must upgrade your client libraries and client code. All the updated client libraries and code examples have been published.

Come join us for a live walkthrough of this release in our "Google Ads API Release Highlights" event on Discord, our Ads Developers YouTube Live, or our LinkedIn Live event tomorrow (May 14 at 10a ET). This will also be recorded and posted on YouTube for those who can’t make the live events. If you have any questions or want to discuss this post, reach out to us in the #ads-api channel on Discord.

New Features

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

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

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

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

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

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

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

The following resources can help you get started:

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

- Anash P. Oommen, Google Ads API Team

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

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

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

Store sales conversions

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

Google Analytics web and app events

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

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

Get started

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

Connect with us

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

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