If your B2B SaaS account feeds Google Ads anything more sophisticated than a form-fill tag — a CRM that pushes back qualified leads, sales-accepted opportunities, or closed-won revenue — there is a good chance a critical pipe quietly changed under you on June 15, 2026. Google deprecated the Google Ads API's UploadClickConversions request as a route for offline conversion imports. As Search Engine Land reported the change, "offline conversion imports using the UploadClickConversions request will stop working after June 15, for accounts that have not used the functionality in the last 180 days."
The deadline has now passed, so this is not a heads-up about something coming — it is a checklist for confirming whether your highest-value conversion signal is still flowing. The failure mode here is the dangerous kind: nothing in the Google Ads interface flashes red when an offline upload stops landing. Spend continues, the campaigns keep serving, and the only symptom is that Smart Bidding slowly drifts toward optimizing for the wrong outcome. This post explains exactly what changed, why it hits SaaS accounts harder than retail, the difference between the old request and the Data Manager API replacing it, and the concrete steps to confirm or restore your offline conversion flow.
What changed on June 15, 2026
For years, the standard way to import offline conversions into Google Ads programmatically was the UploadClickConversions method in the Google Ads API. You captured the Google Click ID (GCLID) at lead capture, stored it against the record in your CRM, and when that lead later became a qualified opportunity or a paying customer, you called the API to send the conversion back — tagged with the GCLID so Google could attribute it to the original click. That loop is what lets the bidder learn which clicks turn into revenue rather than which clicks turn into form submissions.
Google is not removing the capability; it is moving it. Per Search Engine Land, "advertisers and martech providers that rely on offline conversion imports, including enhanced conversions for leads, will need to migrate workflows to the Data Manager API to avoid disruptions." The 180-day grace clause matters: accounts that were actively uploading through the old request keep working for a transition period, but any account that had gone quiet — a paused integration, a seasonal campaign, a SaaS team that only uploads at quarter-end — is exactly the profile that stops working first. If you upload infrequently, assume you are affected and verify rather than wait for a silent gap to show up in a future board deck.
Why this hits B2B SaaS harder than retail
E-commerce advertisers mostly live on the website tag: the conversion — a purchase — happens on-site, in-session, and fires a pixel with a revenue value attached. Offline conversion imports are a nicety for them, not a backbone. B2B SaaS is the opposite. The event that actually matters — a sales-qualified lead, a won deal, an expansion — happens days or weeks after the click, inside a CRM, far from any browser the Google tag can see. The only way to teach the bidder about those events is to send them back, and the API upload was the most common machinery for doing it at scale.
That structural difference is why this deprecation is a SaaS problem first. When the offline pipe breaks, a retailer loses a refinement; a SaaS advertiser loses the entire connection between ad spend and revenue. The bidder reverts to optimizing for the loudest remaining signal, which is almost always top-of-funnel form fills — and as we argue in our guide to conversion tracking for SaaS, optimizing toward raw form volume is how accounts end up paying for leads that never become pipeline. Getting the offline loop back online is therefore not a developer-hygiene task; it is a direct lever on blended CAC.
UploadClickConversions versus the Data Manager API
The old model treated each ingestion path as its own integration: one for offline click conversions, another for enhanced conversions for leads, another for Customer Match audiences. Each had its own request shape, its own quirks, and its own maintenance burden. The Data Manager API consolidates these into a single front door for first-party and offline data. Google's stated direction is that website tags, the Data Manager interface, and API connections can all supply user-provided data at the same time, which improves match rates because the system can stitch identifiers across sources rather than relying on any one of them.
Practically, migration is not a config toggle — it is a rebuild of the code that talks to Google. The conversion logic in your CRM or middleware stays the same (capture the GCLID or first-party identifiers, detect the qualifying event, send it), but the endpoint, authentication, and request payload change. If a third-party connector or martech vendor handles your uploads, your job is mostly to confirm they have shipped Data Manager support and that your account is pointed at the new flow. If you built the integration in-house, a developer needs to port it. Either way, the work is finite and well-documented — the risk is not difficulty, it is assuming someone else already handled it.
The February rule you may have already tripped
The June deadline was not the first tightening of this API in 2026, and the two are easy to conflate. Earlier in the year Google narrowed what data you may attach to a conversion import. As Search Engine Land described it, "the Google Ads API will no longer accept new adopters of session attributes or IP address data in conversion imports starting Feb. 2nd." Imports that run afoul of the rule can return a CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE error inside a partial-failure response — the kind of thing that is invisible unless someone is actually reading the API responses rather than fire-and-forgetting the upload.
The distinction is worth holding clearly: February was about thecontents of the conversion (no new use of session attributes or raw IP), while June 15 was about the request method itself going away. A team that stood up a new integration this spring could have hit the February allowlist wall and then the June deprecation in the same quarter. If you are auditing a SaaS account and offline conversions look thin, check both: confirm the upload is using the Data Manager API, and confirm it is not relying on data types the API has stopped accepting. This is also a good moment to revisit how your consent and tagging setup feeds the whole system, which we cover in our breakdown of the June 2026 GA4 and Google Ads consent split.
How to migrate without losing Smart Bidding signal
Start by establishing whether you have a problem at all. Open your conversion actions, find the offline ones (qualified lead, opportunity, closed-won, or whatever your account names them), and look at the conversions recorded over the last few weeks against the same window a quarter ago. A sharp drop to near-zero on an offline action while website actions keep reporting is the signature of a broken upload. Cross-check against your CRM: if sales closed twenty deals last month and Google Ads recorded two offline conversions, the pipe is leaking regardless of what the bid strategy thinks.
Once you know the state, sequence the fix to protect the bidder. Migrate the integration to the Data Manager API (or confirm your vendor has), then backfill recent conversions where the API allows it so the model is not learning from a hole in the data. Keep the same conversion values you were sending — for SaaS, a closed customer should carry a value that reflects its worth, not a flat count, which is the whole premise behind choosing Maximize Conversion Value over Target CPA when revenue varies by deal. After the flow is restored, give Smart Bidding a couple of weeks to relearn before judging performance, and watch that your target-based strategies settle back toward the realized CAC you expect, as covered in our guide to bidding strategies for B2B SaaS.
A migration checklist for SaaS teams
Concretely, here is the sequence to run. First, inventory how offline conversions enter your account: a native CRM connector, a third-party martech tool, or custom code calling the Google Ads API. Native connectors and most reputable tools are handling the Data Manager migration for you, but confirm it in writing rather than assuming. Second, if anything custom callsUploadClickConversions, treat it as broken until proven otherwise and get a developer to port it to the Data Manager API. Third, verify your imports are not leaning on session attributes or raw IP data that the February change disallowed, since fixing the endpoint will not help if the payload is rejected.
Fourth, reconcile recorded offline conversions against your CRM's actual closed events for the same period — the numbers should be in the same ballpark, and a large gap is your signal to dig in. Fifth, once the flow is confirmed, fold an offline-conversion sanity check into your recurring account review so a future silent break gets caught in weeks, not quarters; our Google Ads optimization checklist is a good home for it. Conversion plumbing is unglamorous, but for a B2B SaaS account it is the difference between Smart Bidding chasing revenue and Smart Bidding chasing form fills. If you would rather have a second set of eyes confirm your offline pipeline survived the migration, our Google Ads audit covers exactly this kind of tracking and bidding review.