← Back to Blog

Google Ads API Blocks New Offline Conversion Imports June 15

Starting June 15 2026, the Google Ads API will reject UploadClickConversions requests from any developer token that hasn’t imported offline conversions between December 2025 and May 2026. WooCommerce stores and tracking plugins that built custom integrations against this endpoint must migrate to the Data Manager API — Google’s unified first-party data ingestion layer launched December 9 2025 with eleven partners. Stores already importing conversions get a transition window. New implementations are blocked entirely after the deadline.

Contents

What Google Is Actually Cutting Off

The June 15 deadline targets one specific API method, not all offline conversion tracking — but it’s the method most custom WooCommerce integrations depend on.

Google announced on May 15 2026 that the UploadClickConversions request in the Google Ads API will stop working after June 15 for developer tokens that can’t demonstrate recent usage. The announcement came from Ben Karl on behalf of the Google Ads API Team. It’s not a vague deprecation warning. It’s a hard cutoff with a specific mechanism: if your developer token hasn’t sent offline conversion data in the past 180 days, the endpoint returns an error.

This matters because offline conversion imports are how businesses track sales that happen after the website session ends. Phone calls that close deals. CRM updates that mark a lead as qualified. Sales-rep interactions that convert a browser into a buyer. Without this data flowing back into Google Ads, Smart Bidding optimizes toward form fills instead of revenue.

The deprecation isn’t theoretical. Google’s own documentation now includes a warning banner: “Starting June 15, 2026, UploadClickConversion requests will fail if the developer token hasn’t previously sent requests to upload offline conversions or enhanced conversions for leads.”

You may be interested in: Microsoft Brand Agents Just Shipped to WooCommerce — and GA4 Can’t See Them

The 180-Day Inactivity Rule

Google draws the line at December 2025 to May 2026 — if your token wasn’t active in that window, access is revoked permanently on the Ads API side.

The cutoff uses a 180-day lookback window. Developer tokens that uploaded offline conversions or enhanced conversions for leads between December 2025 and May 2026 retain access temporarily while they migrate. Tokens with no uploads during that six-month window lose access to UploadClickConversions permanently on June 15.

This is the same pattern Google applied to Customer Match. On April 1 2026, Google disabled Customer Match uploads through the Google Ads API for any developer token that hadn’t been used for Customer Match in the preceding 180 days. No extensions. No appeals process mentioned in the documentation. The offline conversion cutoff follows the identical enforcement mechanism.

After June 15 2026, any developer token that hasn’t uploaded offline conversions via the Google Ads API in the past 180 days will be permanently blocked from using UploadClickConversions.

The distinction between “existing user with transition window” and “blocked entirely” is critical for WooCommerce stores. If you’ve been importing conversions regularly, you have time. If you haven’t started, or if your imports lapsed during a plugin change or developer handoff, the door closes in weeks.

Why WooCommerce Stores Are Exposed

The WooCommerce ecosystem’s reliance on client-side tracking plugins means most stores have never touched the Google Ads API directly — and that’s exactly the profile Google’s cutoff targets.

WooCommerce powers over 4.5 million active stores globally, holding a 33.4% market share by store count according to StoreLeads data from 2025. The vast majority of these stores run Google Ads conversion tracking through WordPress plugins — Pixel Manager for WooCommerce, Conversios, CustomerLabs, or custom GTM containers. Most of these implementations fire conversion pixels from the browser. They never call the Google Ads API server-side.

That matters because the June 15 cutoff specifically targets the server-side API endpoint. Stores that only use client-side pixel tracking aren’t directly affected by this change. But stores that built custom server-side integrations — or use plugins that call the API for offline conversion imports, enhanced conversions for leads, or CRM-to-Google-Ads pipelines — are squarely in the crosshairs.

Here’s the thing: the stores most likely to be affected are also the ones doing the most sophisticated tracking. If you invested in offline conversion imports, you probably did it because you understood that client-side pixels miss phone sales, CRM conversions, and cross-device journeys. Now that investment faces a forced migration, and the timeline is measured in days, not quarters.

WooCommerce powers over 4.5 million active stores globally with a 33.4 percent market share by store count, and most use tracking plugins that rely on client-side or legacy API conversion workflows.

What the Data Manager API Replaces

Google’s Data Manager API isn’t just a new endpoint — it’s a consolidation of five separate data workflows into a single integration surface.

Google launched the Data Manager API on December 9 2025 as a unified first-party data ingestion layer across Google Ads, Google Analytics, and Display & Video 360. Before this, developers maintained separate integrations for Customer Match uploads, offline conversion imports, enhanced conversions for leads, store sales data, and mobile device identifiers. Each had its own API surface, authentication flow, error handling, and rate limits.

The consolidation is real. The Data Manager API operates via both REST and gRPC protocols with OAuth 2.0 authentication using a dedicated datamanager scope. One endpoint handles all five data categories that previously required separate pipelines.

Capability Legacy Google Ads API Data Manager API
Offline conversion imports UploadClickConversions (blocked June 15 for new tokens) Unified conversion endpoint
Customer Match OfflineUserDataJobService (blocked April 1 2026) Unified audience endpoint
Enhanced conversions for leads Same as offline conversions (shared deadline) Unified conversion endpoint
Platform coverage Google Ads only Google Ads + GA4 + DV360
Authentication Standard Google Ads API OAuth Dedicated datamanager OAuth scope
Confidential matching Not available Supported
Encryption Not available Supported

Treasure Data, one of eleven launch partners, reported an 80% reduction in engineering effort and twice-as-fast advertiser onboarding after consolidating their three separate Google API integrations into the single Data Manager API. That 80% figure isn’t marketing — it’s the result of eliminating three separate maintenance burdens: different error formats, different rate limits, different authentication flows.

You may be interested in: Best Buy Activated Offer Highlights Eight Feed Attributes WooCommerce Misses

Migration Paths for WooCommerce Stores

Your migration complexity depends entirely on how your store currently sends conversion data to Google Ads — client-side pixel, plugin API call, or custom server-side pipeline.

If your store uses only client-side pixel tracking (standard Google Ads conversion tag, GTM container, or a WooCommerce plugin that fires JavaScript on the thank-you page), this API change doesn’t directly affect your current setup. Your conversion tracking keeps working. But you’re also missing offline conversions entirely, which means Smart Bidding is optimizing on incomplete data.

If your store uses a CDP or martech platform with a Data Manager API connector — Hightouch, Tealium, Treasure Data, Zapier, CustomerLabs, or one of the other launch partners — migration is a connector swap. The platform handles the API change on their side. Budget a week of engineering time for testing and validation.

If your store built a custom server-side pipeline that calls UploadClickConversions directly, you’re looking at a more significant rebuild. The Data Manager API requires a new Google Cloud project with the API enabled, a dedicated OAuth scope, and different request formatting. Budget a month of development time, and start this week if you haven’t already — June 15 is 19 days away.

Google launched with eleven integration partners on day one: AdSwerve, CustomerLabs, Datahash, Fifty-Five, Hightouch, Jellyfish, Lytics, Tealium, Treasure Data, and Zapier. If your tech stack includes any of these, the migration path is already documented.

The Timeline Pattern Google Is Following

Google isn’t deprecating features randomly. There’s a deliberate sequence: Customer Match first, offline conversions next, full legacy sunset in March 2027.

Zoom out and the pattern is clear. Google is systematically moving every data ingestion workflow from the fragmented legacy APIs to the Data Manager API on a fixed schedule:

December 9 2025: Data Manager API launches with eleven partners. Google positions it as the unified ingestion layer.

April 1 2026: Customer Match uploads via the Google Ads API disabled for inactive developer tokens. No extensions.

June 15 2026: Offline conversion imports and enhanced conversions for leads blocked for inactive tokens. Same 180-day enforcement.

March 2027: Full legacy API sunset for DV360 audience ingestion and remaining data partner integrations. Everyone migrates.

Google already disabled Customer Match uploads through the Google Ads API on April 1 2026 for inactive developer tokens — the June 15 offline conversion cutoff follows the same 180-day inactivity pattern.

Translation: if you’re planning to migrate “eventually,” March 2027 is your hard wall. But the individual feature cutoffs mean you lose capabilities progressively along the way. Each missed deadline narrows what the old API can do, creating compounding integration debt.

For WooCommerce stores running Google Ads, the practical question isn’t whether to migrate. It’s whether you do it on your timeline or Google’s. The teams that treat this as a measurement upgrade — tightening identifier capture, adding enhanced conversions, improving data normalization — will come out ahead. The teams that scramble to replicate their existing setup on a new endpoint will get the same incomplete data through a different pipe.

Key Takeaways

  • June 15 2026 is a hard deadline: Developer tokens inactive on the Google Ads API UploadClickConversions endpoint since December 2025 will be blocked permanently. No extensions have been announced and none were granted for the identical Customer Match cutoff in April.
  • Client-side pixel tracking is unaffected but incomplete: If your WooCommerce store only fires JavaScript conversion pixels, this API change doesn’t break your current setup — but you’re already missing every conversion that happens after the browser session closes.
  • Data Manager API is the only path forward: Google launched it December 9 2025 as the unified ingestion layer for offline conversions, Customer Match, enhanced conversions for leads, and store sales across Google Ads, GA4, and DV360.
  • Migration timeline depends on your stack: CDP or martech platform with a connector means roughly one week. Custom server-side pipeline means roughly one month. Both require a new Google Cloud project with the Data Manager API enabled and a dedicated OAuth scope.
  • March 2027 is the full sunset: Even if you’re actively importing conversions today and have a transition window past June 15, the complete legacy API shutdown for all remaining endpoints lands in March 2027. The question is timing, not whether.
What exactly happens on June 15 2026 with Google Ads offline conversion imports?

Developer tokens that haven’t uploaded offline conversions or enhanced conversions for leads via the Google Ads API between December 2025 and May 2026 will receive errors when calling UploadClickConversions. Tokens with recent activity get a transition window to migrate to the Data Manager API. New implementations must use Data Manager API from day one.

Does this affect WooCommerce tracking plugins like Pixel Manager and Conversios?

It depends on how the plugin sends conversion data. Plugins using client-side pixels or Google Tag Manager are not directly affected by this API change. Plugins or custom integrations that call the Google Ads API UploadClickConversions endpoint for offline or enhanced lead conversions need to migrate that specific workflow to the Data Manager API before the deadline.

What is the Data Manager API and how is it different from the Google Ads API?

The Data Manager API is Google’s unified first-party data ingestion layer launched December 9 2025. It consolidates Customer Match uploads, offline conversion imports, enhanced conversions for leads, and store sales into a single REST and gRPC endpoint with OAuth 2.0 authentication. Unlike the Google Ads API which required separate implementations per product, Data Manager API serves Google Ads, Google Analytics, and Display and Video 360 through one integration.

How long does migration to the Data Manager API take for a WooCommerce store?

If your store uses a CDP or martech platform that already has a Data Manager API connector — like Treasure Data, Hightouch, Tealium, or Zapier — migration may take a week of engineering time. Custom-built pipelines that call the Google Ads API directly typically need a month of development work to rebuild against the new endpoint, authentication flow, and data format.

Is the June 15 deadline the final cutoff or will Google extend it?

Google’s pattern suggests they won’t extend. Customer Match uploads were blocked for inactive tokens on April 1 2026 with no extensions granted. The full legacy API sunset for DV360 and remaining endpoints is set for March 2027. Google is progressively narrowing the old API’s scope on a fixed schedule.

References

If your WooCommerce store’s conversion data flows through a custom Google Ads API integration, the migration clock is already running. Seresa builds server-side event pipelines that route conversion data where it needs to go — including the Data Manager API — without depending on browser pixels or legacy endpoints.