The modern digital advertising ecosystem is undergoing a massive shift. As third-party cookies continue to phase out and privacy regulations tighten globally, the reliance on first-party data has transformed from a strategic advantage into an absolute necessity. Advertisers need efficient, secure, and unified ways to feed their offline conversion and audience data back into ad platforms to optimize their campaigns.
Recognizing this critical market need, Google has announced a major expansion of its Data Manager API. This update consolidates measurement and audience activation workflows across Google Marketing Platform (GMP) and Google Ads, introducing robust new capabilities for offline conversion ingestion and customer matching. By unifying these data pipelines, Google is making it easier for enterprise advertisers to orchestrate their marketing campaigns from a single, centralized control point.
Consolidating the Google Marketing Platform Ecosystem
Historically, managing offline conversions across Google’s enterprise ad suite was a fragmented and resource-intensive endeavor. If an advertiser wanted to upload offline purchase events, lead statuses, or CRM modifications to optimize campaigns across multiple systems, they had to build and maintain separate data integrations for each tool.
With this latest update, the Data Manager API officially supports offline conversion event uploads directly to three of Google’s flagship enterprise advertising tools:
- Campaign Manager 360 (CM360)
- Search Ads 360 (SA360)
- Display & Video 360 (DV360)
This development establishes the Data Manager API as the centralized, primary data ingestion layer across the broader Google advertising ecosystem. Rather than writing unique codebases to communicate with legacy APIs for different platforms, developers can now deploy a single, unified pipeline to handle their organization’s entire offline event data flow.
Streamlined Workflows with Single-Schema Ingestion
The core benefit of this API expansion lies in its unified architecture. Google has introduced a single-schema structure for data ingestion. This means that regardless of where the data is ultimately headed—whether it is a search campaign in Search Ads 360 or a programmatic display deal in Display & Video 360—the data format remains consistent.
This single schema drastically reduces the engineering overhead traditionally associated with multi-platform campaign management. Instead of mapping customer data fields to multiple distinct specifications, data engineering teams can map their internal CRM or data warehouse fields to the Data Manager API schema once.
Multi-Destination Routing in a Single Request
Efficiency is further enhanced by the API’s new multi-destination routing capabilities. In previous iterations of Google’s advertising APIs, sending a single conversion event to multiple platforms required executing separate API calls for each destination. This process not only increased network latency and cloud computing costs but also introduced the potential for data discrepancies across platforms.
The upgraded Data Manager API solves this by allowing advertisers to route offline conversion events to multiple GMP destinations simultaneously within a single request. This ensures that attribution models in Search Ads 360 and bidding algorithms in Display & Video 360 are operating on the exact same, real-time data sets without requiring redundant integrations.
Privacy-First Data Protection and Encryption
As privacy compliance remains a top priority for developers and compliance teams, the Data Manager API is built with modern security protocols at its core. The API fully supports encrypted user identifiers. Advertisers can securely upload sensitive, first-party data points, including:
- Hashed email addresses
- Hashed phone numbers
- Mobile device IDs
By using industry-standard hashing protocols (such as SHA-256) before data transmission, advertisers can ensure that personally identifiable information (PII) is fully protected while still enabling precise attribution and conversion tracking across Google’s ad networks.
The Shift from Legacy APIs: Migration is Underway
Google is actively encouraging advertisers who currently rely on the legacy Campaign Manager 360 API for offline conversion uploads to begin their migration to the Data Manager API. The company emphasizes that the Data Manager API is not merely a replacement, but a modern framework designed to offer significantly greater flexibility, lower maintenance costs, and better integration with modern data stacks.
For organizations looking to plan their technical roadmap, reviewing the official Google Ads Developer documentation on the Data Manager API update is highly recommended. Transitioning early allows development teams to iron out data pipeline updates before any potential deprecation timelines are announced for legacy conversion ingestion endpoints.
Improving Customer Match Performance with IP-Based Matching
Beyond conversion tracking, Google is also introducing critical upgrades to its audience matching capabilities. Customer Match has long been a powerful tool for advertisers to re-engage past customers or build lookalike audiences using first-party lists. However, match rates have historically been limited by the availability of static contact details like email addresses or phone numbers.
To address this, Google has added IP ingestion support to Google Ads Customer Match through a newly introduced field known as CompositeData.
What is the CompositeData Field?
The CompositeData field allows advertisers to combine traditional first-party identifiers with IP address data during the ingestion process. Instead of treating IP addresses as isolated data points, the API links them with other hashed customer records to create a richer, more accurate profile for the matching engine.
Advertisers can now construct customer profiles using a combination of:
- IP addresses
- Hashed email addresses
- Hashed phone numbers
- Physical mailing addresses
This multi-layered approach to identity resolution gives Google’s matching algorithms more indicators to securely connect offline customer data to logged-in Google users, resulting in highly optimized match rates.
The Q3 2026 Milestone: IP Addresses and Timestamps
Looking to the future, Google has outlined a clear timeline for how IP address data will be utilized for matching. Beginning in Q3 2026, including IP addresses alongside corresponding observation timestamps will become highly critical for improving Customer Match rates.
The inclusion of timestamps is a key component of this update. Because IP addresses are often dynamic and change as users move between home networks, cellular networks, and offices, an IP address without a timestamp quickly loses its matching utility. By pairing an IP address with the exact timestamp of when the user interacted with the brand (e.g., when they made a purchase or filled out a form), Google can match the user with significantly higher accuracy.
Advertisers who start adapting their CRM systems to capture and store observation timestamps now will be uniquely positioned to maximize their audience reach and targeting accuracy when these changes fully take effect in late 2026.
Why This Matters for Enterprise Advertisers and Agencies
For enterprise brands and the digital agencies that support them, these updates represent a major milestone in cross-channel campaign management. Here is why this update demands immediate attention:
Improved Return on Ad Spend (ROAS)
When offline conversions are delayed or inaccurate, automated bidding strategies (such as Target CPA or Target ROAS) suffer. By using a faster, unified API to feed conversions directly into SA360, DV360, and CM360, machine learning models receive more accurate and timely signals. This allows bidding systems to optimize in real-time, reducing waste and driving higher conversions for every dollar spent.
Better Cross-Channel Attribution
In a world of complex buyer journeys, a customer might see a programmatic display ad via Display & Video 360, research the product via search and click an ad managed by Search Ads 360, and ultimately complete the purchase in-store or over the phone. By routing the single offline conversion event to all three platforms via the Data Manager API, marketers can accurately attribute the role of each channel in driving the final sale, avoiding double-counting and mismatched reports.
Streamlined Engineering Workloads
Marketing technology stacks have become notoriously complex. Reducing the number of unique APIs that engineering teams must support lowers the risk of code breakage, minimizes technical debt, and frees up development resources for other high-priority business intelligence projects.
Conclusion: The Future of Unified Data Management
With this expansion, Google is positioning the Data Manager API as the ultimate control room for customer data and offline conversion flows across its advertising suite. By simplifying schema management, enabling multi-destination routing, and introducing advanced matching signals like IP addresses with timestamps, Google is providing advertisers with the tools needed to succeed in a privacy-first, post-cookie digital landscape.
Now is the time for digital marketing teams, CRM administrators, and technical leads to audit their existing offline conversion workflows, explore the newly expanded capabilities, and establish a clear roadmap for migrating legacy systems to the modern Data Manager API framework.