The June 2026 Cutover: Google Moves Offline Conversions Out of the Ads API
Quick Answer: On June 15, 2026, Google blocks offline conversion imports and enhanced conversions for leads uploads in the Google Ads API, migrating them to the Data Manager API (Google Ads Help, 2026). Developer tokens inactive between January and June 2026 won’t receive legacy access. Customer Match already moved. Advertisers using first-party data alongside GCLIDs via the new path see a median 10% increase in conversions. This article covers what changes, what stays, and the single action store owners need to take before the deadline.
In this article
- What changes for offline conversions on June 15, 2026?
- What happens to inactive developer tokens?
- Did Customer Match move first?
- What combined in April 2026?
- Which Ads API operations keep working?
- What is the benefit of making the switch, not just the obligation?
- What does a store need to send for an offline conversion to match?
- What is the single action for a store owner before the deadline?
What changes for offline conversions on June 15, 2026?
From June 15, 2026, offline conversion imports and enhanced conversions for leads uploads are migrated to the Data Manager API and blocked in the Google Ads API (Google Ads Help, 2026). Any integration, plugin, or custom script still sending these events through the legacy Ads API endpoint will stop working on that date.
This isn’t a deprecation warning with a vague timeline. It’s a hard cutover — a specific date after which the old endpoint returns errors instead of processing your conversions. If your WooCommerce store sends offline or CRM conversions to Google Ads for attribution and Smart Bidding, those signals go dark unless you’ve switched to the Data Manager API path before the deadline.
The move is part of Google’s broader consolidation of first-party data ingestion. Rather than maintaining separate APIs for offline conversions, Customer Match, and enhanced conversions, Google is funnelling everything through the Data Manager API as a single ingestion layer. The Ads API remains for campaign management, bidding, and reporting — but the data-in door is moving.
June 15, 2026: offline conversion imports and enhanced conversions for leads uploads are blocked in the Google Ads API and migrated to the Data Manager API (Google Ads Help, 2026).
What happens to inactive developer tokens?
Developer tokens that have not sent a request between January 2026 and June 2026 will not be allowlisted for legacy access (Google Ads Help, 2026). If your token has been dormant during that six-month window, you’re out — there’s no grace period to claim legacy status after the cutover.
This matters for stores and agencies that built a custom integration years ago and left it running unattended. If that integration hasn’t actually sent an API request during the January–June 2026 window — maybe the store paused offline uploads, or the cron job broke silently — the token loses any legacy allowlisting it might otherwise have received. The only path forward is the Data Manager API.
Even tokens that do qualify for legacy access are on borrowed time. Google hasn’t published an end date for legacy allowlisting, but the direction is clear: the Data Manager API is the forward path, and the legacy window is a migration buffer, not a permanent alternative.
Did Customer Match move first?
Yes — Google began requiring the Data Manager API for new Customer Match setups before the offline-conversion cutover, as part of the same consolidation (Google for Developers, 2026). Customer Match was the canary: if you set up audience list uploads recently, you’ve already used the Data Manager API whether you realised it or not.
This sequencing tells you something about Google’s strategy. They didn’t move everything at once — they started with Customer Match, let the ecosystem adjust, and then announced the offline conversion cutover. Each migration follows the same pattern: the Data Manager API becomes the required path, the Ads API endpoint gets locked, and legacy access exists only as a temporary bridge for existing integrations.
For WooCommerce stores that already use Customer Match (uploading customer email lists for remarketing), the Data Manager API is already in the stack. The offline conversion migration adds a second operation to the same endpoint — same authentication, same API surface, different payload type.
What combined in April 2026?
From April 2026, enhanced conversions for web and leads became a single setting accepting data from website tags, Data Manager, and API connections simultaneously (Google Ads Help, 2026). Two previously separate configuration paths merged into one unified setup inside Google Ads.
Before April, you configured enhanced conversions for web (from your site’s tag) and enhanced conversions for leads (from CRM/offline uploads) as separate settings with separate verification steps. Now they’re one toggle that accepts data from all three sources: your website tag, the Data Manager API, and legacy API connections during the transition.
The practical effect: a single conversion action can now receive both online tag data and offline upload data. This means a lead that converts on your site and later closes in your CRM can be attributed through one unified conversion, not two separate ones. For WooCommerce stores with a sales cycle that spans online and offline touchpoints, this is the measurement model Google has been pushing toward.
| Timeline | Change | Impact |
|---|---|---|
| Before April 2026 | Web and leads enhanced conversions separate | Two configs, two verification flows |
| April 2026 | Merged into single setting | One toggle, three data sources |
| June 15, 2026 | Ads API blocked for offline imports | Data Manager API required |
Related: What is the Google Data Manager API?
Which Ads API operations keep working?
Only offline conversion imports and enhanced conversions for leads move to the Data Manager API; other Google Ads API operations continue functioning normally (Google for Developers, 2026). Campaign management, bidding, reporting, audience targeting, and every other Ads API function stays exactly where it is.
This is a surgical migration, not a wholesale API replacement. If your WooCommerce integration uses the Ads API to read campaign performance, adjust bids, or manage ad groups, none of that changes. The question isn’t “do I need to migrate everything” — the question is “do I send offline conversions or CRM data through the Ads API?”
If the answer is no — if all your conversion tracking runs through the website tag (gtag.js or GTM) — the June 15 cutover doesn’t directly affect you. Your tag fires on the thank-you page, Google receives the conversion, and the entire chain stays on the web-side path. The cutover applies specifically to server-side uploads of conversion data that happened outside the browser session.
Only offline conversion imports and enhanced conversions for leads move — campaign management, bidding, reporting, and all other Ads API operations continue unchanged (Google for Developers, 2026).
What is the benefit of making the switch, not just the obligation?
Advertisers using first-party data alongside GCLIDs via offline import saw a median 10% increase in conversions over standard offline imports (Google Ads Help, 2026). The Data Manager API isn’t just a new address for the same data — it’s a richer pipeline that feeds more signal into Google’s bidding models.
The improvement comes from the enhanced conversions for leads pathway, which sends hashed first-party identifiers (email, phone) alongside the traditional GCLID. Google uses those additional signals to match conversions even when the GCLID is missing or incomplete — which happens more often than most stores realise, thanks to cross-device journeys, cookie expiry, and browser privacy features.
Here’s the thing… most stores treat this migration as a chore — something forced on them by a deadline. But the stores that migrate early and send the full set of first-party identifiers don’t just maintain their attribution — they improve it. A 10% median increase in attributed conversions means Smart Bidding sees more of your actual customers, optimises more accurately, and allocates budget to the campaigns that actually drive revenue.
Related: Can I use Enhanced Conversions with offline conversions?
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
What does a store need to send for an offline conversion to match?
Each event needs a GCLID or hashed user-provided data such as email or phone, plus a conversion name and time, to match back to a click (Google Ads Help, 2026). The Data Manager API accepts the same data fields — the change is in which endpoint receives them, not what you send.
The minimum viable payload is a GCLID, a conversion action name, and a timestamp. But relying on GCLID alone is increasingly fragile — the click ID depends on the user’s browser passing it through from ad click to conversion, and any interruption (cross-device, ITP, cookie expiry) breaks the chain. Adding hashed email or phone gives Google a second matching path that survives those gaps.
For WooCommerce stores, all of these fields are available at checkout: the order email, the order phone, the GCLID captured from the landing-page URL, the conversion action name you define in Google Ads, and the order timestamp. The data is there — the question is whether your integration currently collects and forwards all of it, or only the GCLID.
For stores managing this through custom code or plugins that need updating, Transmute Engine routes offline and CRM conversions to Google through the supported Data Manager API path with GCLID and hashed first-party identifiers, so the cutover doesn’t strand your attribution — no plugin migration or custom integration work required.
What is the single action for a store owner before the deadline?
Confirm your offline or CRM conversion uploads route through the Data Manager API path well before June 15, 2026 (Google Ads Help, 2026), rather than the legacy Ads API. That’s it — one check, one action, one deadline.
If you use a WooCommerce plugin for offline conversion uploads, check whether the plugin developer has released an update that routes through the Data Manager API. If they haven’t, contact them — and have a backup plan. If you built a custom integration, your developer needs to switch the API endpoint and authentication from the Ads API to the Data Manager API.
If you don’t send offline conversions at all — if your conversion tracking runs entirely through the website tag — this cutover doesn’t apply to you. But it’s worth checking, because some plugins upload conversion data server-side without making it obvious in their settings UI. The simplest test: look in Google Ads under Tools → Conversions → your conversion action → Sources. If it shows “Import” as a source alongside “Website,” you have an offline import active — and it needs to be on the Data Manager API path before June 15.
LIFETIME LOCK on Harvest Annual Plan
Push your WordPress event data server-side seamlessly into BigQuery so AI can analyse it.
Key Takeaways
- Hard deadline, not a suggestion: June 15, 2026 — the Ads API stops accepting offline conversion imports and enhanced conversions for leads.
- Inactive tokens get no legacy access: developer tokens dormant between January and June 2026 won’t be allowlisted — Data Manager API is the only path.
- Customer Match already moved: the Data Manager API is already the required path for audience list uploads, establishing the pattern.
- 10% more conversions: advertisers sending first-party data via the new path see a median 10% increase over standard offline imports.
- One action: confirm your offline conversion upload path routes through Data Manager API, not the legacy Ads API, before the deadline.
From June 15, 2026, offline conversion imports and enhanced conversions for leads uploads are migrated to the Data Manager API and blocked in the Google Ads API. Any integration still using the legacy Ads API endpoint for these operations will stop working on that date.
Developer tokens that have not sent a request between January 2026 and June 2026 will not be allowlisted for legacy access. If your token has been dormant during that window, you must use the Data Manager API — there is no legacy fallback path for inactive tokens.
Yes — Google began requiring the Data Manager API for new Customer Match setups before the offline-conversion cutover, as part of the same consolidation. Customer Match was the first operation to migrate, establishing the Data Manager API as Google’s forward path for first-party data ingestion.
From April 2026, enhanced conversions for web and leads became a single setting accepting data from website tags, Data Manager, and API connections simultaneously. This merged two previously separate configuration paths into one unified setup inside Google Ads.
Only offline conversion imports and enhanced conversions for leads move to the Data Manager API. Other Google Ads API operations — campaign management, bidding, reporting, audience targeting — continue functioning normally through the Ads API.
Advertisers using first-party data alongside GCLIDs via offline import saw a median 10% increase in conversions over standard offline imports. The Data Manager API is designed for richer first-party data signals, which feed better into Google’s bidding models.
Each event needs a GCLID or hashed user-provided data such as email or phone, plus a conversion name and time, to match back to a click. The Data Manager API accepts the same data fields — the change is in which endpoint receives them, not what you send.
Confirm your offline or CRM conversion uploads route through the Data Manager API path well before June 15, 2026, rather than the legacy Ads API. If you use a plugin or integration, check whether its developer has released an update that routes through the Data Manager API.
References
- Google Ads Help (2026). About offline conversion imports. Source
- Google Ads Help (2026). Upgrade offline conversion import to enhanced conversions for leads. Source
- Google for Developers (2026). Data Manager API developer guides. Source
- Google for Developers (2026). Google Ads offline conversions (Data Manager API). Source