The End of Fragmentation: Google Consolidates Enhanced Conversions Infrastructure

In a definitive move to simplify its ad-tech ecosystem, Google has announced the full consolidation of its "Enhanced Conversions" infrastructure. By collapsing the long-standing distinction between "Enhanced Conversions for Web" and "Enhanced Conversions for Leads" into a single, unified toggle, the search giant is signaling a shift toward a more streamlined, backend-agnostic approach to conversion tracking.

This transition, which reached a critical milestone on June 15, 2026, marks the end of an era where advertisers were forced to navigate two distinct, often confusing, implementation pathways. Simultaneously, Google is mandating a migration to its Data Manager API, effectively sunsetting legacy pathways within the Google Ads API for offline conversion uploads.

The Evolution of Tracking: What is Changing?

For years, digital marketers have operated under a bifurcated framework. Enhanced Conversions for Web was designed to capture first-party data directly from browser-side tags, while Enhanced Conversions for Leads focused on bridging the gap between CRM-stored lead data and offline conversion events.

Starting in June 2026, these two product silos are being dismantled. According to Google’s updated documentation, advertisers no longer need to choose a specific product path. Instead, the Google Ads interface will feature a single "on/off" setting. When activated, the system will ingest hashed user data from all connected sources—whether from the Google tag, Google Tag Manager, or the Data Manager API—and reconcile those inputs automatically.

A Two-Phase Rollout

The transition was executed in two strategic phases:

• Phase One (April 2026): Google Ads began simultaneously accepting user-provided data from all three primary channels (website tags, Data Manager, and API connections). This eliminated the need for advertisers to designate a single channel for data ingestion.
• Phase Two (June 2026): The interface distinction between web and lead-based enhanced conversions disappeared. Both are now managed under a single, unified configuration setting located within the "Customer data use" panel of the Google Ads account and at the individual conversion action level.

The API Deadline: Why the Data Manager API Matters

While the interface changes simplify the experience for UI-based users, the most significant impact is reserved for developers. As of June 15, 2026, Google has blocked offline conversion imports and lead-based conversion uploads via the legacy Google Ads API.

Developers who did not utilize the legacy path between January and June 2026 were excluded from "allowlisting," effectively forcing a hard migration to the Data Manager API. Teams that attempt to call the ConversionUploadService.UploadClickConversions method without migrating will now receive a standard error, marking the finality of this infrastructure shift.

Chronology of the Transition

To understand the speed of this consolidation, one must look at the rapid sequence of events leading to the June 15 deadline:

• March 2022: Google launches Enhanced Conversions for Leads, formalizing the two-product divide.
• December 9, 2025: The Data Manager API is launched, providing a centralized ingestion point for first-party data.
• February 2, 2026: Google ceases support for new implementations of session attributes and IP address data in conversion imports.
• April 1, 2026: Customer Match uploads via the Google Ads API are officially deprecated.
• April 10, 2026: Google announces the collapse of Enhanced Conversions into a single toggle.
• May 2026: Google introduces version 1.6 of the Data Manager API, adding store sales measurement.
• May 28, 2026: Version 1.7 launches, extending ingestion capabilities to Campaign Manager 360 and Search Ads 360.
• June 15, 2026: The enforcement deadline arrives; legacy API pathways are officially blocked.

Supporting Data and Technical Architecture

The core philosophy driving this shift is "schema unification." Under the old architecture, a field like "transaction ID" or "hashed email" often carried different requirements or naming conventions depending on whether it was sent to Google Ads, Google Marketing Platform, or Google Analytics.

The Data Manager API enforces a single, standardized schema across all Google products. This consistency allows technical teams to build an endpoint once and utilize it for multiple measurement objectives—from offline conversion adjustments to enhanced web tracking—without rebuilding logic for each specific tool.

Operational Capacity

For engineering teams managing the transition, the Data Manager API offers significant scale. Each Google Cloud project is currently capped at 100,000 requests per day, with a rate limit of 300 requests per minute. Each individual request is capable of batching up to 2,000 conversion events, with up to 10 user identifiers per record. This represents a robust increase in efficiency compared to the fragmented, smaller-batch processes of the past.

Official Responses and Strategic Rationale

Google’s documentation emphasizes that the primary goal is "improved conversion tracking accuracy" and the optimization of "Smart Bidding signal quality." By allowing the system to ingest data from multiple sources simultaneously, the matching algorithm has a larger, more diverse pool of hashed signals to compare against signed-in Google accounts.

In a recent technical brief, Google’s product management team noted that the previous fragmented system was a primary source of "implementation friction." By routing all data through the Data Manager API, Google is essentially creating a "single source of truth" for first-party data. This aligns with their broader mission to move toward server-side ingestion as the primary method for high-accuracy measurement in a cookieless future.

Implications for Advertisers and Developers

The implications of this shift are profound for both agency-side operations and internal engineering teams.

For B2B Advertisers

For those managing lead-generation campaigns, the complexity of choosing between "web" or "leads" tracking is gone. Advertisers no longer need to worry about whether they have chosen the "correct" product for their CRM-heavy workflows. The system is now intelligent enough to reconcile data regardless of the entry point, which should theoretically lead to higher match rates and more stable bidding signals for high-value offline leads.

For Developers and Data Engineers

The transition to the Data Manager API is not merely a name change; it requires a new authentication flow. The API uses OAuth 2.0 with a specific datamanager scope, which is entirely distinct from the scopes used by the Google Ads API. Teams that were previously reliant on the Google Ads API for CRM integration must now configure new credential flows and update their underlying architecture to support the REST or gRPC protocols required by the new API.

However, the payoff is significant. Early adopters like Treasure Data reported an 80 percent reduction in engineering overhead after moving their disparate Google integrations—such as Customer Match and audience management—into the unified Data Manager architecture.

Conclusion: A New Era of Measurement

The consolidation of Enhanced Conversions is part of a larger, predictable pattern in Google’s ecosystem. By establishing a capability in a new, centralized product (the Data Manager API) and then systematically deprecating the old pathways, Google is forcing a level of standardization that was previously impossible.

For most advertisers, the shift is a net positive. It reduces the "three-pipeline headache" and simplifies the UI for non-technical users. For developers, while the June 15 deadline created a brief period of operational intensity, the result is a cleaner, more efficient, and more reliable data pipeline. As Google continues to push its "Data Manager" vision, it is clear that the future of ad measurement will be built on centralized, standardized, and high-quality first-party data streams.