Google Data Manager API: GMP events & match

Google is expanding the Data Manager API with core capabilities for measurement and audience activation across its advertising ecosystem. Advertisers and partners can now send offline conversion events to multiple Google Marketing Platform destinations and improve Customer Match through IP-based matching. The update puts unified data ingestion at the center instead of isolated interfaces per product.

Offline conversions through a central API

The Data Manager API will support uploading offline conversion events to Campaign Manager 360, Search Ads 360, and Display & Video 360. The API is growing into a central ingestion layer for ad data within Google’s platforms. Advertisers benefit from fewer parallel integrations and clearer data flows between measurement, attribution, and activation.

Previously, teams often had to maintain separate workflows to transfer conversions into different Google products. That increased implementation effort and the risk of errors when schemas diverged. With the expanded feature set, Google addresses this fragmentation and signals a long-term standard for data-driven campaign management.

One schema for multiple destinations

A central schema makes it possible to send conversion data consistently to multiple Google products. Encrypted user identifiers such as email addresses and phone numbers are supported. Events can be routed to multiple destinations in a single request—a relevant lever for large first-party data programs with high transaction volume and complex customer journeys across online and offline channels.

• Unified conversion delivery instead of product-specific standalone integrations
• Support for encrypted identifiers for privacy-compliant transfers
• Routing multiple events to different GMP destinations in one API call
• Reduced interface maintenance as the Google stack product portfolio grows

Migration from the Campaign Manager 360 API

Google recommends that advertisers still using the Campaign Manager 360 API for conversion uploads move to the Data Manager API. The newer framework is intended to simplify implementation and offer more flexibility for measurement and attribution scenarios. For marketing and analytics teams, that means API migration roadmaps should be planned early, including tests for data quality, event mapping, and monitoring of upload success rates.

In practice, a phased rollout pays off: first validate critical offline events in a sandbox, then activate destinations step by step. That makes it easier to spot deviations in attribution reports before budget decisions rely on changed data.

IP ingestion for Customer Match

Another highlight is IP ingestion for Google Ads Customer Match through the new CompositeData field. In addition to classic identifiers—email, phone, postal address—IP addresses can be uploaded. Starting in Q3 2026, Google says that IP addresses with matching observation timestamps should improve Customer Match rates and thereby increase audience reach and match accuracy.

For performance marketers, this is especially relevant as cookie signals weaken and first-party data becomes more strategic. Higher match rates can directly affect remarketing, lookalikes, and cross-campaign activation—provided data quality and legal foundations are properly secured.

Impact on attribution and audience strategy

The changes make it easier to unify conversion measurement across Google’s ad products while strengthening matching capabilities. Companies with extensive CRM and offline data sources can model attribution more precisely and activate audiences more consistently. At the same time, pressure grows on clean data pipelines: faulty timestamps, duplicate events, or inconsistent identifiers have a stronger impact when central APIs become the standard.

What SEO and analytics leads should review now

Even though the focus is on paid media and GMP, the updates touch interfaces that SEO-adjacent teams often help shape: data quality, consent, CRM connectivity, and reporting coherence. Anyone running search, display, and video through Google stacks should work with AdOps and data engineering to decide which offline events will run centrally through the Data Manager API and which fields to prioritize for Customer Match.

Documentation, governance, and role clarity will be decisive: who maintains the event schema, who validates uploads, and how are discrepancies between platform reports resolved? The earlier these questions are answered, the more stable migration and scaling will be.

Technical requirements for implementation teams

Developers should clarify early which event types are captured offline, how hashes for email and phone are built, and whether observation timestamps per identifier stay consistent with internal CRM exports. Normalization errors lead to poor match rates faster than missing API features. Anyone addressing multiple Google destinations in parallel benefits from clearly documented mapping tables between internal field names and the Data Manager API’s central schema.

For agencies and in-house teams, a shared data glossary helps: which conversion counts as a qualified lead, which as a purchase, and how cancellations or returns are handled. The clearer these rules are before upload, the more reliable attribution and audience delivery become across Search Ads 360, Display & Video 360, and Campaign Manager 360.

At the same time, align with existing consent and privacy policies. IP addresses and personal identifiers face different requirements by market. Teams planning to use the Q3 2026 Customer Match extension should complete legal approval and technical pseudonymization before production rollout.

Google is positioning the Data Manager API as a hub for conversion and audience data. Advertisers get a more unified way to control measurement and Customer Match across ad platforms—with measurable potential for better attribution, higher match rates, and more efficient data processes across the online marketing setup.