Google expands Data Manager API with GMP event ingestion
The digital advertising landscape is undergoing a massive transformation. As third-party cookies phase out and global privacy regulations tighten, enterprise advertisers must find new ways to measure performance, attribute conversions, and target audiences accurately. To solve these challenges, companies are increasingly relying on first-party data, particularly offline conversion events, to feed machine learning algorithms and ad platforms. To streamline this transition, Google has announced a major upgrade to its data infrastructure. The Google Data Manager API has been expanded to support event ingestion across the Google Marketing Platform (GMP). This consolidation represents a significant shift in how enterprise brands, agencies, and ad-tech developers route first-party offline conversions and manage audience matches across Google’s key advertising destinations. With this latest integration, Google is positioning the Data Manager API as the centralized, privacy-safe conduit for all customer data. Below, we explore the technical mechanics of this update, the strategic advantages of unified schemas, the introduction of IP-based matching for Customer Match, and what these changes mean for your marketing workflows. Understanding the Expanded Google Data Manager API Historically, managing offline conversion data within the Google ecosystem was a fragmented process. Advertisers pushing offline data—such as CRM updates, in-store purchases, phone call conversions, or lead status changes—had to build and maintain separate integration pipelines for different platforms. A developer might have had to write distinct codebases to feed conversions into Campaign Manager 360, Search Ads 360, and Google Ads. The updated Data Manager API solves this fragmentation by offering a single, consolidated ingestion layer. Developers can now send offline conversion event data to three critical Google Marketing Platform destinations through a unified interface: Campaign Manager 360 (CM360): Google’s ad server and management system for tracking cross-channel campaigns. Search Ads 360 (SA360): The search management platform used to design, manage, and optimize large-scale search campaigns across various engines. Display & Video 360 (DV360): Google’s demand-side platform (DSP) for programmatic media buying across display, video, audio, and connected TV. By bringing these systems under a single API umbrella, Google simplifies the technical overhead required to build and maintain modern marketing data pipelines. The Power of a Single, Unified Schema For data engineers and marketing technology teams, the introduction of a single schema is the most impactful technical improvement in this release. Previously, sending offline conversions to multiple platforms required mapping data fields to different formats, handling varied authentication protocols, and managing separate API rate limits. The expanded Data Manager API allows advertisers to format their offline conversion data once and route it to multiple destinations simultaneously. A single API call can now securely send conversion signals to Campaign Manager 360, Search Ads 360, and Display & Video 360. This multi-destination routing drastically reduces duplicate data transmission, minimizes the risk of API errors, and ensures that all measurement tools are working with the exact same conversion dataset. Additionally, the API natively supports encrypted user identifiers. Advertisers can safely transmit sensitive customer data—such as email addresses and phone numbers—by hashing them before or during the ingestion process. This ensures compliance with strict data security policies while preserving the ability to match offline actions to online ad exposures. Migrating from Legacy Campaign Manager 360 APIs With this announcement, Google is actively encouraging advertisers currently using the legacy Campaign Manager 360 API for offline conversion uploads to begin their migration to the Data Manager API. The transition is designed to provide greater flexibility, ease of implementation, and long-term support for advanced attribution use cases. Continuing to rely on older, single-purpose APIs introduces technical debt and leaves organizations unprepared for future privacy features. Moving to the Data Manager API ensures your measurement infrastructure is built on Google’s modern privacy-first framework. Advertisers can learn more about configuring their pipelines by visiting the Google Ads Developer documentation, which details the migration steps and payload structures. Upgrading Customer Match with IP-Based Ingestion In tandem with the GMP event ingestion expansion, Google is rolling out an update to Google Ads Customer Match. Advertisers will soon have access to IP-based ingestion support via a newly introduced data block known as the CompositeData field. Traditionally, Customer Match has allowed brands to upload lists of first-party contact information—like emails, phone numbers, and physical mailing addresses—to build custom target audiences across YouTube, Search, Gmail, and the Display Network. The new CompositeData field expands this capability by allowing advertisers to upload customer IP addresses alongside these traditional identifiers. Beginning in Q3 2026, Google will use these IP addresses, combined with corresponding observation timestamps, to improve match rates across Customer Match campaigns. This addition of IP addresses as an identifying signal acts as an extra layer of verification, helping Google’s systems match offline user profiles to active Google accounts with higher precision. How the CompositeData Field Works The CompositeData field acts as a container for advanced identifiers. When configuring your audience uploads, you can pass IP address data linked to specific user events alongside standard contact fields. To maintain user privacy, the API enforces strict protocols regarding how these IP addresses and timestamps are sent and processed. By preparing your CRM schemas to collect and store IP addresses alongside timestamps now, your organization will be ready to leverage the match-rate optimization immediately when it goes live in Q3 2026. Strategic Benefits for Enterprise Advertisers Consolidating your conversion and audience ingestion pipelines under the Data Manager API yields several long-term strategic advantages: 1. Unified Cross-Channel Attribution When different measurement tools receive data from separate pipelines, minor discrepancies in timestamps, deduplication rules, or data formatting can cause major attribution differences. By routing a single, consistent stream of offline events to CM360, SA360, and DV360, you ensure that your programmatic, search, and overall campaign reports remain synchronized. This consistency makes it easier to evaluate cross-channel performance and allocate budgets more accurately. 2. Reduced Engineering Overhead Maintaining separate API integrations for multiple ad platforms is a drain on engineering resources. Whenever an ad platform updates its API version or changes its data requirements, your development team has to adjust multiple codebases. Transitioning to