[go: up one dir, main page]

The latest release of the Data Manager API introduces features that simplify audience management, enhance ingestion workflows with field-level warnings, and enable more granular user-provided data for Google Analytics.

Remove all audience members

Use the new RemoveAllAudienceMembers method to clear all members from specified user lists in a single operation. The optional removeAsOfTime parameter lets you target only those members added before a specific timestamp.

This is particularly useful when you need to perform a full refresh (or "replace all") of your audience data, allowing you to clear the existing list and populate it with a new set of users.

Ingestion field warnings

Data Manager API ingestion responses now include detailed field-level warnings for validation issues on optional fields. If the API detects validation issues with optional fields, your ingestion request will succeed and the rest of your ingestion data will still be processed. Validation failures for required fields will continue to fail the entire request following the fast-fail model.

If any optional field you provide is invalid, the response from IngestEventsRequest or IngestAudienceMembersRequest includes a field_warnings field with a list of FieldWarning objects. Each warning provides a specific reason (WarningReason), a descriptive message, and the location of the field in the request where the issue occurred.

Additional address data for Google Analytics events

You can now provide additional user address information when ingesting events to Google Analytics destinations. Along with the given_name, family_name, region_code, and postal_code fields, AddressInfo resource now supports:

  • address_line (street address)
  • city
  • administrative_area (state or province)

Also, you can now use the existing user-provided data (user_data) field to meet the Identifiers requirement for multi-source events sent to web data streams. This gives you another option when you don't have the ad_identifiers.gclid, user_id, or client_id for a multi-source event.

Get started

Build faster with AI agent skills: We recently introduced new Data Manager API agent skills to help you speed up your integrations. Explore the new skills in the Google Skills GitHub repository to get more accurate, efficient guidance directly within your AI-assisted coding environment.

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.

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:

  1. Performance
  2. Privacy
  3. New Features
  4. 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.

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.

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

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.

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.

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

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.

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

  1. 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.
  2. 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.
  3. 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.
  4. 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:

Improving your Advertising Workflows

It’s an incredible time to be a developer in the advertising space. Innovation is moving at a breakneck pace, and we’re shifting from incremental API integrations to fundamental improvements in how technical users interact with our platforms. In the latest episode of Ads DevCast, I sat down with my colleague Matt Landers to discuss how AI is moving from "hype" to "utility," decreasing friction in development and delivering tangible business results.

The Power of Multi-Product Insights

One of the most exciting developments we’re seeing is the value of Advertising MCPs (Model Context Protocol) servers showing up. These open-standard tools allow your AI agents to interact directly with the Google Ads and Google Analytics APIs.

Historically, solving a problem like "why is my high-CTR ad not converting?" meant a lot of manual data joining between Ads and Analytics. By combining the Google Ads and Analytics MCPs, you can now perform this analysis in seconds using natural language. You can verify engagement rates, identify content mismatches on landing pages, and even suggest ROI improvements in the time it takes to brew a cup of coffee.

Efficiency and Speed with Natural Language

We’re also seeing AI make technical tasks more accessible. A great example is the recent update to our Sheets Report Builder add-on for Google Analytics 4. Previously, creating complex reports required manually adding dimensions, metrics, and filters in the UI. Now, with Gemini integrated directly into Sheets, you can simply ask, "What's my highest converting landing page?" and the tool automatically sets all the parameters in the UI, sends the API request, and imports the data for you.

The Senior Pair Programmer in Your CLI

For developers deep in the code, the Google Ads API Developer Assistant is a game-changer. Think of it as a senior pair programmer that has memorized the entire API schema and every possible error code. Whether you’re troubleshooting conversion uploads or finding hidden problems in your account, the assistant doesn’t just explain what’s wrong—it can generate, debug, and even run the fix directly in your environment.

Health, Diagnostics, and Seamless Migrations

Beyond AI-driven insights, we’re focused on improving the underlying health of your technical systems. The Data Manager API will soon feature integrated diagnostics in the UI, allowing you to track what went wrong with your integrations. Last but not least, for publishers, we’ve released a new migration skill for the AdMob SDK to help you transition between versions with the help of your coding agent.

Experiment, Fail Fast, and Build Great Things

The barrier to entry for building sophisticated, data-driven advertising solutions is dropping. By automating the busy work, you’re freed up to focus on high-impact projects that drive real business growth.

Ready to dive deeper?

Watch the full episode: goo.gle/watchadsdevcast

Listen on the go: goo.gle/listenadsdevcast

Take our Episode 3 Survey: goo.gle/adc-survey-e3

Join our Discord Community: goo.gle/ads-and-measurement-discord

We're excited to announce the addition of new channels for the Data Manager API on our “Google Advertising and Measurement Community” Discord server. To join, just click this invite link and follow the onboarding guide.

Our team will be on this server regularly to interact with the Data Manager API community, answering questions and gathering feedback in the #data-manager-api channel. We’ll also keep you up to date on the latest Data Manager API news in the #announce-data-manager-api channel.

If you have any questions or want to discuss this post, please reach out to us on the “Google Advertising and Measurement Community” Discord server. We look forward to seeing you there and hearing your thoughts on how we can continue to improve the Data Manager API!

We're excited to announce the launch of the new Google Advertising and Measurement Developers Hub!

Come see the new site!

Whether you're looking to automate campaigns, analyze performance, manage tags, or monetize your apps, the new hub is designed to make it easier to find the right tools and information.

We've launched a new technical-user focused site to make it easier than ever for you to find the tools, resources, and support you need to build and innovate with Google's advertising and measurement products.

What's New?

We have created a one-stop shop where you can easily find the resources you need, connect with our team and the community, and get support. Here are some key features:

  • At-a-glance homepage: A clear starting point highlighting how we can help, with quick links to our blog, Discord, and information about our team.
  • Meet the team: Learn more about the Developer Relations team dedicated to supporting your success.
  • Products: A comprehensive directory of the developer products we cover, from the Google Ads API and Google Analytics APIs to Publisher Tools like AdMob and Ad Manager, linking directly to their official documentation. You can browse by categories like Advertising Platforms, Tagging, Measurement & Analytics, and Publisher Tools.
  • Connect with us: A streamlined page to help you find the best way to engage:
    • Join our vibrant Discord community.
    • Find links to product or technical support.
    • Download open source projects on GitHub.
  • Media and podcast: A new home for our multimedia content, including the Ads DevCast playlist embedded directly on the page.

We're excited to make this the place for you to learn, build, and connect.

Please explore the new site and use the Send Feedback button located at the bottom of each page to share your thoughts!

If you have any questions about this announcement or want to discuss it with our team and the community, please reach out to us on our "Google Advertising and Measurement Community" Discord server.

Happy Building!

A new podcast for the ads technical community

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

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

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

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

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

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

Getting Smarter with MCP Servers

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

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

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

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

Moving Faster with the Developer Assistant

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

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

Improving Accessibility

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

We want to hear from you

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

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

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

Starting on April 1, 2026, the Google Ads API will no longer accept new adopters of Customer Match. As with our recent announcement for the use of session attributes and IP address in click conversions in the Google Ads API, we’re recommending that new adopters of Customer Match integrate with the Data Manager API as their primary user data import API.

Developers who have not adopted Customer Match, or have not uploaded data to a Customer Match list between October 2025 and March 2026, will receive an error if they attempt to upload to a Customer Match list. Developers who have already adopted Customer Match can continue importing user data using the Google Ads API while they integrate with the Data Manager API.

Technical details

  • Developers will be allowlisted by their developer token.
  • Once this change is rolled out, users who are not on the allowlist will receive the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when attempting to upload user data to a Customer Match list using either the OfflineUserDataJobService or UserDataService.
  • See the documentation for integrating with the Data Manager API for Customer Match imports for Google Ads.

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.

We're excited to announce the release of v1.5 of the Data Manager API, delivering a more comprehensive platform for data management. This update introduces powerful new capabilities for managing user lists alongside expanded options for audience member ingestion.

End to end user list management

The UserListService now allows you to oversee the lifecycle of your user lists entirely through the Data Manager API. It provides core resource management operations such as create, retrieve, update, and delete methods for UserLists, enabling full control over your audience management workflows.

Partner links

The introduction of the PartnerLinkService provides a secure way to manage connections between advertiser and data partner accounts across Google Ads and Display & Video 360.

Expanded audience member identifiers

The Data Manager API now supports additional user identifiers for audience ingestion. You can now upload User IDs, which can be used for Customer Match in Google Ads.

We’ve also integrated status reporting specific to User ID when you retrieve diagnostics for your ingestion requests. These updates make it easier to monitor User ID ingestion and quickly identify any issues.

Get started

If you have questions or need help, contact us through the support page.

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

Starting on February 2, 2026, the Google Ads API will no longer accept new adopters of session attributes or IP address data as part of conversion imports. To ensure a more robust and scalable experience for handling complex data, we recommend that Google Ads API developers transition to the Data Manager API - where session attributes and IP address are accepted - as their primary conversion and user data import API.

Developers who have already adopted session attributes or IP addresses in their click conversion imports can continue importing that data using the Google Ads API until they’ve moved their conversion imports over to the Data Manager API.

Technical details

  • Developers will be allowlisted by their developer token.
  • Once this change is rolled out, you may notice the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in the partial_failure responses of your conversion import requests. This error indicates that the associated conversion was rejected due to the presence of session attributes and/or IP address.
  • Resolve this error with these steps:
    • Temporarily remove session attributes and IP address from conversion import requests and continue importing conversions to the Google Ads API.
    • Update your code to use the Data Manager API with session attributes and IP address.
    • Discontinue conversion imports to the Google Ads API once you’re successfully making imports to the Data Manager API.

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.

The Data Manager API, a new solution for data ingestion across Google’s advertising platforms, is now generally available. This API is designed to streamline how advertisers, agencies, and data partners send and manage their first-party data, saving valuable time and resources while ensuring data is handled securely.

Simplification

The Data Manager API simplifies how you send data to audience lists and conversions used in your Google campaigns. Instead of building and maintaining multiple API integrations, you can now send data once and apply it to different Google ads solutions. For advertisers who prefer API connections, this provides a streamlined and scalable way to activate first-party data across multiple campaign types and platforms.

Our vision is universal activation and measurement i.e. bring your data and activate/measure across Google campaigns, GMP campaigns and Google Analytics. At launch use cases include:

Audiences Conversions
Populate audience lists for use in both Google Ads and Display & Video 360 (DV360), including the use of customer information, unique mobile device unique IDs, and Publisher Advertiser Identity Reconciliation (PAIR). Send conversion events that take place off your website directly to Google Ads, including offline conversion import and conversions with consented customer information to supplement imported offline conversion data to improve accuracy and bidding performance

Security and Privacy at the Core

The Data Manager API is also built with advanced, privacy-centric features. The API supports confidential matching for several use cases. This includes the option to encrypt data for audience and conversion events, allowing you to pass encrypted customer information (for example, an email address or phone number), which is processed in a trusted execution environment. This includes audience lists for Customer Match.

In the coming months, the Data Manager API will expand support to include additional use cases across Google Ads, Google Analytics, Display & Video 360, Search Ads 360, and Campaign Manager 360.

Get Started Today

Unlock a more efficient, scalable, and secure way to manage your data. The Data Manager API is available to all developers now. Head over to the developer documentation to get started. If you have any questions or need help, check out the Data Manager API support page for options.