Google expands Data Manager API with GMP event ingestion

Introduction

The digital advertising ecosystem is undergoing one of its most significant structural shifts. With the ongoing phase-out of traditional tracking mechanisms, privacy regulations tightening globally, and platforms restricting cross-site tracking, advertisers are increasingly reliant on first-party data. To successfully navigate this transition, brands require robust, streamlined infrastructure to connect their offline data directly to their marketing suites.

Recognizing this need, Google has announced a major expansion of its Data Manager API. The update introduces Google Marketing Platform (GMP) offline conversion event ingestion, consolidating measurement and audience activation workflows across Google’s core advertising systems. By allowing advertisers to route offline conversions and first-party data to multiple destinations simultaneously, Google is positioning the Data Manager API as the definitive centralized pipeline for first-party data management.

This expansion simplifies complex technical workflows and introduces new capabilities for Google Ads Customer Match. Through advanced IP-based matching and unified schemas, modern marketers can look forward to more accurate attribution, reduced developer overhead, and improved audience match rates. Let us dive deep into what these updates entail, how they function, and what they mean for the future of your digital marketing strategies.

The Evolution of Google Data Manager

To understand the significance of this update, it is helpful to look at the role Google Data Manager plays within the broader Google Ads and Google Marketing Platform ecosystem. Historically, managing first-party data across multiple Google tools was a fragmented and resource-intensive process. If an advertiser wanted to send offline conversion data to Google Ads, Search Ads 360, and Campaign Manager 360, they often had to build and maintain separate API integrations, manage distinct data schemas, and coordinate multiple server-side pipelines.

Google Data Manager was introduced to solve this exact pain point. Acting as a simplified, user-friendly data preparation and ingestion layer, it bridges the gap between external data warehouses—such as BigQuery, Snowflake, and Salesforce—and Google’s advertising platforms. The latest updates to the Data Manager API represent a major step forward, transforming this tool from a basic connector into a powerful, automated data routing engine.

Consolidated Event Ingestion Across Google Marketing Platform

The headline feature of this update is the Data Manager API’s new support for offline conversion event uploads across Google Marketing Platform destinations. Specifically, advertisers can now seamlessly transmit data to:

• Campaign Manager 360 (CM360): The leading ad server and measurement system for tracking campaign performance across sites and networks.
• Search Ads 360 (SA360): The enterprise search management platform used to build, manage, and track campaigns across multiple search engines.
• Display & Video 360 (DV360): Google’s demand-side platform (DSP) designed for programmatic media buying across display, video, TV, audio, and other channels.

Rather than managing separate connections for each of these platforms, engineers and database administrators can now write to a single, unified API. This consolidated framework reduces the margin for error, minimizes api call volume, and drastically cuts down on custom development hours.

A Single Schema for Multi-Destination Routing

Previously, sending a single offline conversion—such as an in-store purchase, a phone call consultation, or a finalized insurance quote—to multiple Google tools required formatting that data differently for each system. Each platform had its own set of required fields, naming conventions, and payload expectations.

With the expanded Data Manager API, Google introduces a standardized schema. Advertisers format the offline event once, package it with the necessary user identifiers and transaction details, and send it to the API. Within a single API request, the system can route that conversion event to multiple destinations. This multi-destination routing ensures that your analytics, programmatic bidding, search campaigns, and ad serving platforms are all looking at the exact same source of truth in near real-time.

Prioritizing Data Privacy with Encrypted Identifiers

As privacy standards continue to elevate, protecting user identity during data transfers is non-negotiable. The Data Manager API supports secure, industry-standard hashing protocols. Advertisers can upload encrypted user identifiers, including hashed email addresses and phone numbers. This ensures that sensitive personally identifiable information (PII) is securely protected before it ever leaves the advertiser’s infrastructure, maintaining compliance with global privacy regulations while still enabling precise closed-loop attribution.

The Push to Migrate: Moving Away from Legacy Campaign Manager 360 APIs

For organizations currently relying on legacy tools like the Campaign Manager 360 API for offline conversion uploads, Google’s latest announcement serves as a clear call to action. The company is actively encouraging advertisers and technology partners to migrate their conversion pipelines over to the Data Manager API.

Why make the switch? Legacy APIs were often built around older data handling methodologies. They lack the flexibility, speed, and cross-platform synergy of modern cloud integrations. By transitioning to the Data Manager API, engineering teams can benefit from:

• Lower Maintenance Overhead: Maintaining a single API connection is substantially easier and more cost-effective than managing a web of legacy point-to-point connections.
• Greater Scalability: The Data Manager API is architected to handle the massive data volumes generated by enterprise-level first-party databases without performance degradation.
• Future-Proofing: Google is concentrating its engineering resources on the Data Manager suite. New measurement, modeling, and privacy features will be introduced natively here, rather than being retrofitted into legacy pipelines.

To help companies transition, Google offers detailed documentation outlining mapping practices, schema translations, and deployment guides, facilitating a smooth migration with minimal disruption to active advertising campaigns.

Enhancing Customer Match with IP-Based Ingestion

Beyond tracking conversions, first-party data is vital for finding and retaining high-value customers. Google Ads Customer Match is a foundational tool for this, allowing advertisers to upload their customer lists to target specific audiences, build lookalikes, or exclude existing buyers from acquisition campaigns.

However, the efficacy of Customer Match relies entirely on the match rate—the percentage of uploaded customer records that Google can successfully pair with an active Google account. To boost these rates, Google is introducing IP address ingestion support for Customer Match via a new database field called CompositeData.

Understanding the CompositeData Field

The introduction of the CompositeData field allows advertisers to combine traditional first-party identifiers with newly supported network signals. Now, when uploading list updates via the Data Manager API, you can send IP addresses alongside:

• Email addresses (hashed)
• Phone numbers (hashed)
• Physical mailing addresses

By pairing physical and digital addresses with network identifiers, Google’s matching algorithms have more signals to confirm a user’s identity securely. This multi-layered approach to identity resolution is crucial in an era where single-point identifiers are increasingly restricted.

The Role of Observation Timestamps

To maintain accuracy and respect user privacy, IP addresses cannot be treated as permanent, static identifiers. Dynamic IP allocation means that an IP address associated with a user today might belong to a completely different household or device next week.

To address this, Google is requiring the inclusion of corresponding observation timestamps alongside IP address data. These timestamps pinpoint exactly when the interaction took place (e.g., when the user logged in, completed a form, or made a purchase). By using the timestamp, Google’s matching systems can accurately attribute the network signal to the correct user account during that specific window of time, ensuring high match accuracy while preventing false positives.

Timeline: Looking Ahead to Q3 2026

While the technical framework for IP address ingestion is rolling out now, Google has established a clear timeline for its optimization. Starting in Q3 2026, the inclusion of IP addresses paired with accurate observation timestamps will actively feed into and improve Customer Match rate calculations.

This gives development and marketing teams a generous integration window. Advertisers who adopt the new CompositeData schema early will have their data pipelines fully optimized, tested, and operational long before the Q3 2026 milestone, giving them a distinct competitive advantage in audience reach and targeting precision.

Why These Updates Matter to Advertisers and Marketers

The expansion of the Data Manager API is more than just a minor technical release; it represents a strategic shift in how enterprise marketing teams manage data workflows. Here is a look at why these updates are critical for modern marketing organizations.

1. Simplified Workflows and Reduced Operational Costs

For large brands, managing data pipelines is expensive. Data engineers often spend dozens of hours a week troubleshooting API connections, fixing broken data formats, and adjusting schemas across multiple ad platforms. By streamlining this process through the Data Manager API, companies can significantly reduce development and upkeep costs. A single integration services multiple downstream endpoints, freeing up valuable developer resources for higher-priority projects.

2. Improved Attribution and Multi-Touch Measurement

Accurate attribution is the holy grail of digital marketing. When offline sales, lead statuses, or phone inquiries are not properly linked back to initial ad clicks, campaigns look less effective than they actually are. By enabling simultaneous event routing to Campaign Manager 360, Search Ads 360, and Display & Video 360, the Data Manager API ensures that your entire Google tech stack operates with identical performance data. This consistency eliminates discrepancies, leading to cleaner conversion paths, more reliable attribution models, and smarter budget allocation.

3. Expanded Audience Reach and Targeting Precision

A higher Customer Match rate directly correlates to better campaign performance. If you upload a list of 100,000 high-value customers but Google can only match 40,000 of them, you lose out on 60% of your targeted audience. By integrating IP addresses and observation timestamps via the CompositeData field, advertisers can recover lost match opportunities, resulting in larger retargeting pools, more accurate exclusion lists, and higher-quality lookalike audiences.

4. Resilience in a Privacy-First Environment

As the industry moves away from third-party tracking, first-party data pipelines are no longer optional—they are the foundation of modern digital advertising. The Data Manager API provides a secure, compliant, and highly structured environment for managing this data. By building on Google’s recommended first-party infrastructure now, companies protect themselves against future platform disruptions and privacy policy updates.

Getting Started: Next Steps for Implementation

If you want to capitalize on these new capabilities, here is a roadmap to help your team get started:

1. Conduct a Data Audit: Evaluate your current offline conversion tracking and Customer Match upload workflows. Identify which legacy APIs or manual upload methods are currently in use.
2. Review the Technical Documentation: Have your development or data engineering team review the official Data Manager API as the central hub for conversion and audience data documentation to understand the schema requirements, especially the new CompositeData field configurations.
3. Map Your First-Party Data: Ensure your internal databases (CRM, ERP, or data warehouse) are configured to capture and export the required identifiers, including IP addresses and accurate UTC observation timestamps.
4. Build and Test a Pilot Integration: Set up a test pipeline to send offline conversions using the new unified schema to a single test destination. Once verified, expand routing to multiple GMP destinations.
5. Plan Your Migration Timeline: If your organization uses the Campaign Manager 360 API for conversion uploads, schedule a migration plan to deprecate the legacy setup and fully transition to the Data Manager API ahead of future deprecation schedules.

Conclusion

With the expansion of the Data Manager API, Google has delivered a powerful utility that addresses two of the biggest hurdles in modern digital advertising: fragmented data workflows and declining audience match rates. By unifying Google Marketing Platform event ingestion and introducing sophisticated IP-based matching capabilities, Google is paving a clear, simplified path forward for first-party data activation.

As the industry counts down to the strategic milestone in Q3 2026, early adoption of these tools is highly recommended. Marketers who prioritize unified, privacy-compliant, and technically optimized data pipelines today will be the ones driving the most efficient, high-performing campaigns tomorrow.