Google Data Manager in 2026: What Changed, What Comes Next, and What Lead-Gen Advertisers Should Do

If you send CRM data to Google Ads, the door you send it through has changed. Data Manager is now that door, and Google is building most of its measurement around it.

What Data Manager is

Data Manager is Google's single way in for first-party data: the leads, sales and customer lists from your own systems. It comes in two forms. One is a screen inside Google Ads, and now Google Analytics and Display & Video 360, with ready-made connections to common tools. The other is the Data Manager API, for anything that sends data automatically.

One connection now carries what used to take several: customer lists for audiences, offline conversions, and enhanced conversions for leads. For a lead-gen advertiser, that means the route your closed deals and lead values take back to Google.

What has changed so far

• 9 December 2025. Google made the Data Manager API generally available, starting with a set of use cases across Google Ads, Google Analytics and Display & Video 360, with more to follow.
• 1 April 2026. Customer Match uploads through the old Google Ads API were restricted to projects with earlier Customer Match activity. New adopters go through Data Manager.
• May 2026, Google Marketing Live. Direct connections for Mailchimp, ActiveCampaign and Klaviyo, and a map view, announced as coming, of how data flows in from sources such as BigQuery, Google Drive, HubSpot and Shopify.
• 15 June 2026. Developer tokens with no offline conversion uploads between 17 December 2025 and 15 June 2026 can no longer import offline conversions through the Google Ads API, enhanced conversions for leads included. They get a CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error and are directed to the Data Manager API. Integrations that were already uploading can continue for now.
• 10 September 2026. Data Manager built into Google Analytics and Display & Video 360. Enhanced conversions expanded to both. The API adopted the IAB Tech Lab's Event and Conversion API standard (ECAPI), which Google, Meta and others helped write. Google also announced a Data Strength Uplift metric for Google Ads, which estimates the additional conversions your data setup recovers, and a Google Drive connection.

Google has not published a shutdown date for existing offline conversion uploads through the Google Ads API that we could verify. Its migration guide still describes both routes. The direction is clear, the date is not, so confirm the deadline that applies to you with Google or your provider.

What it means for lead-gen advertisers today

If your offline conversions already flow through the Google Ads API, check whether your integration kept access. If it was uploading before 15 June 2026, it most likely did, and nothing breaks today. Google is still steering every new integration to Data Manager, so ask your tool or agency for its migration plan rather than waiting for a deadline.

If you are starting now, start on Data Manager. A tool that offers you the old upload route is building on something Google is moving away from.

The core data is the same. The ad click ID (gclid, gbraid or wbraid), a hashed email or phone number, the conversion time, and the value and currency. Data Manager has its own format around them, with requirements of its own such as naming the event's source, so a migration is real work, not a new address.

Send the hashed email or phone, not just the click ID. With enhanced conversions for leads, they can match a lead to its ad even when the click ID was lost on the way, by a privacy browser or a form that dropped it.

Expect a different kind of reply. The old upload answered row by row. Data Manager accepts a batch and checks the detail afterwards (more on that below).

What we learned building on it

ValueBasedBidding.com sends lead values to Google, so we hit the change first-hand. Four things we saw in our own integration that the announcements do not spell out:

1. A new integration is refused completely. On 1 September 2026 our first upload through the Google Ads API created the conversion action, read the campaigns, and then refused all 466 leads with this message: "New integrations for uploading click conversions should use the Data Manager API. Usage of ConversionUploadService.UploadClickConversions is limited to existing users." Our developer token was new, so it had no uploads in the qualifying period, and no setting changes that. That is what happened to our integration; one that was already uploading would not see it.

2. At most 2,000 events per request. A larger send has to be split. Ours failed at 12,641 leads until it went in batches. Anyone uploading a backlog or a busy month will meet this limit.

3. One badly formed row can sink a request. A structural error or a missing required field in a single record can fail every lead sent with it. Other problems surface later, as processing errors on individual records, and a problem with an optional field may only produce a warning. The API has a validate-only mode that checks a request without recording anything. Use it before a large first send.

4. Accepted is not the same as processed. An accepted request returns a request ID, not a match count. Google's request diagnostics, checked from about half an hour later, then report success, partial success or failure, with the processing errors. Your Google Ads conversion reporting is where you see the conversions that were attributed and used for bidding. Check both.

Why Google is betting on it

Signal loss. Browsers, cookie limits and consent rules mean Google's own tags see a little less every year. The records a business keeps about its own customers are the part that keeps working. Data Manager is how Google gets them, alongside measures on the tag side such as Google tag gateway.

AI bidding needs outcomes. Smart Bidding, Performance Max and AI Max learn from whatever you count as a conversion. A form fill teaches them less than a qualified lead, and a qualified lead less than a closed deal. Getting CRM outcomes into Google is how Google's automation gets better, and how it earns a larger share of the budget.

Proving the value of data. The Data Strength Uplift metric is Google putting a number on what an advertiser's data setup is worth, in conversions recovered. Google also reports that advertisers connecting offline and app data through Data Manager see on average 26% higher incremental return on ad spend. That is Google's internal figure, not an independent result, and not something any one account can expect from connecting.

One standard. ECAPI gives Google, Meta and other platforms a shared starting point. Each platform still maps it to its own format, with its own event IDs, timestamps and consent fields, but the work of sending the same lead to several platforms gets smaller, so more advertisers will do it.

Where it is heading: my predictions

These are my reading of the direction, not anything Google has announced.

1. Data Manager becomes the only door. Every remaining upload route moves in: store sales, call conversions, customer lists, the lot. Within a couple of years I expect the old Google Ads API services for sending data to be gone.

2. Direct CRM connections multiply. HubSpot and Shopify are among the sources Google says its coming map view will show. I expect direct offline conversion connections from them, Salesforce and other large CRMs to follow, so a closed deal reaches Google without a tool in between.

3. Data strength becomes a score you are managed by. Like Quality Score and the optimisation score, a visible data score with recommendations attached: connect your CRM, add offline conversions, send values. Expect Google's account teams to push it.

4. Values matter more than counts. As more outcomes arrive through one door, bidding will lean harder on what each conversion is worth. Journey-aware bidding already reads pipeline stages. Advertisers who send a value for every lead will have an edge over those who send a count. The guide to value-based bidding for lead generation covers how to start.

What a connection cannot do

Data Manager moves what is in your CRM. It does not decide what a lead is worth. A connection that sends every lead as one identical conversion gives Google a cleaner pipe for the same thin signal.

The value on each lead still has to come from somewhere, and the most defensible source is your own history: how often each kind of lead closed, and what it closed for. That is the difference between telling Google that a lead arrived and telling it which leads are worth paying more for. The case for better value signals goes further into why.

A migration checklist

1. Find out how your offline conversions reach Google today: a tool, an agency, a file upload, or the old API.
2. If it is the Google Ads API, check that it kept access after 15 June 2026, and ask whoever runs it for their plan and date to move to Data Manager.
3. Capture the ad click ID into your CRM on every lead. The click ID guide covers where it gets lost.
4. Send a hashed email or phone as well, so enhanced conversions for leads can match the leads whose click ID went missing.
5. Send a value, not just a count. If you are not sure your CRM can support one, check your data first.
6. After any change, check the request diagnostics and, a day or two later, your Google Ads conversion reporting. Accepted does not mean processed.
7. Look for the Data Strength Uplift metric in your account as it rolls out.

Where ValueBasedBidding.com fits

ValueBasedBidding.com already sends through the Data Manager API. It reads your closed deals, works out what each kind of lead is worth from your own close rates and deal sizes, and sends that value with every new lead, so what goes through Google's new door is a number worth bidding on. The free analysis shows what your leads are worth before anything is sent.

Sources: Google's Data Manager API reference; Google's September 2026 measurement updates; Search Engine Journal on Data Manager's expansion and the uplift metric; martech.org on the IAB's Event and Conversion API; Google's Google Marketing Live 2026 announcements; PPC Land on the Data Manager API and the Data Strength Uplift metric; the Google Ads Developer Blog on changes to offline click conversion import and PPC Land on the 15 June cutoff; Google's request diagnostics guide. The 26% figure is Google's internal data and is not independently verified. The 466-lead refusal, the 2,000-event limit and the batch behaviour are from our own integration.