Data Manager API: the standard Google adopted so conversions arrive complete

The Data Manager API is the single gateway Google created to receive conversion and audience data from companies, now built on ECAPI (short for Event and Conversions API, a standard maintained by the IAB Tech Lab, the body that organizes technical specifications for the digital advertising market). On September 10, 2026, Google confirmed this change in an official announcement, and it helps explain a problem that anyone managing paid media has felt for years: the conversion data that reaches Google almost always arrives incomplete.

Why the conversion reaches Google incomplete

Every Google Ads campaign depends on a signal coming back: someone clicked, and then converted. In practice, that signal gets lost at several points along the way. A form without a standardized phone field has no way to feed the email and phone match that Google uses to confirm the conversion. A click identifier such as the GCLID disappears when the lead switches devices or takes days to close a deal, and even when the data exists, it sometimes reaches Google too late to count within the campaign's attribution window.

The result is always the same: the bidding algorithm optimizes with less information than it should, and the results report shows fewer conversions than actually happened. The cause is not a Google failure, it is the way each company organizes, or fails to organize, its own data before sending it.

What Google changed in September 2026

Until recently, each Google product had its own way of receiving conversions: one route for Google Ads, another for Google Analytics, another for Display & Video 360. Companies operating on more than one front ended up building separate integrations to say, at bottom, the same thing: “this contact converted”.

The change announced on 09/10/2026 unifies this upload. The Data Manager API becomes the single path, and Google decided to build it on a market conversion standard, not on a proprietary specification. By adopting the IAB Tech Lab's ECAPI, Google joins a convention that other advertising platforms already recognize, which reduces the need to rewrite integrations every time a new requirement appears.

As part of the same announcement, Data Manager also began operating inside Google Analytics and Display & Video 360, and Google launched the Data Strength Uplift metric in Google Ads, to estimate the gain in conversions attributable to more complete first-party data. One caveat: the uplift numbers published by Google itself are the company's internal measurement, so they work as a reference, not as a market benchmark.

The old routes that have already gone (or are going) offline

Adopting the ECAPI standard is not the only movement under way. Google has been shutting down, in stages, the oldest routes for sending conversions through the Google Ads API:

• Customer Match through the legacy routes (OfflineUserDataJobService and UserDataService): shut down on 04/01/2026.
• Offline conversion import and Enhanced Conversions for Leads through the Google Ads API: shut down on 06/15/2026.

Those who still maintained these integrations had to migrate to the Data Manager API to keep sending these events. It is a recurring pattern in Google's behavior: first it concentrates data intake at a single point, then it shuts down the parallel doors.

What this changes for those who manage paid media

In practice, this is an operations problem before it is a tooling problem. A well-built conversion integration depends on three things that remain the responsibility of whoever runs the campaign, not Google: the form captures the right identifiers (phone, email, GCLID), the upload happens close to the moment the conversion actually happens, and there is some data hygiene routine to catch empty or duplicate fields before they turn into a lost conversion.

Without those three things resolved, migrating to the Data Manager API swaps the pipe for a more modern one, but does not fix the leak along the way, and it is precisely that leak that makes the operation's attribution model overestimate some channels and underestimate others, without anyone noticing where the distortion came from.

Frequently asked questions about the Data Manager API

Does the Data Manager API replace the Google Ads pixel? No. It is the server-side channel for sending conversion and audience events, complementary to the tracking that already exists on the site or in the CRM. What changes is the format and the standard used to send those events to Google.

Do you need to switch ad platforms to comply with ECAPI? No. Adoption happens on Google's side, in the way it receives the data. Whoever sends conversions today through the Data Manager API, or plans to migrate to it, is the one who needs to align the integration with the new standard.

What is left for the next article

This text stayed on the why: why the conversion arrives incomplete and why Google decided to standardize the intake of this data now. In the next text we show how this already works in practice, including the migration deadlines and what actually stops working for those who do not adapt in time. In the meantime, it is worth reviewing how your operation's data sending workflows look today, to find out at which point along the way the conversion is getting lost.

Official source: Google, “Data Strength Updates”, published on 09/10/2026.