Google Ads Closed the API Door on IP and Session Data

The Migration Cascade: Three Cutoffs in Six Months

Google didn’t announce one API change — it executed three sequential cutoffs that together shift the entire conversion data pipeline away from the legacy Ads API infrastructure.

On January 7, 2026, Google announced that the Ads API would stop accepting new implementations of session attributes and IP address data in conversion imports, effective February 2. That gave advertisers less than four weeks to complete any in-progress integrations or begin migrating to the Data Manager API. It was the first domino in a cascade that has now closed three separate data pathways in six months.

From February 2, 2026, the Google Ads API stopped accepting new implementations of session attribute and IP address data in conversion imports.

The second cutoff hit on April 1, 2026, when the Ads API stopped functioning for Customer Match uploads via OfflineUserDataJobService and UserDataService. Google notified developer token holders of that deadline on March 4 — again, roughly four weeks of notice. The third cutoff arrived on June 15, 2026, when new offline conversion imports via the Ads API were blocked entirely.

The pattern is clear: every data ingestion pathway that ran through the legacy Ads API is being redirected to the Data Manager API, one category at a time. Developer tokens that haven’t sent a request between January and June 2026 won’t be allowlisted for legacy access at all — meaning dormant integrations lose the option to use the old pathway permanently.

You may be interested in: Chrome’s IP Protection Swaps Real IPs for Coarse Geo in Incognito

What Broke on February 2: IP and Session Data

The February cutoff specifically targeted session attributes and IP address data — two signals that advertisers used for geographic attribution and conversion validation.

Session attributes provide contextual data about the user’s browsing session: page URL, referrer, device type, and other signals that help Google match an imported conversion to the correct click. IP address data served a similar role, providing geographic validation and fraud-checking signals. Both fields enhanced Google’s ability to match offline conversions to the ad clicks that influenced them — and both are now blocked for new Ads API adopters.

Existing implementations — developer tokens that were already sending these fields before February 2 — can continue temporarily. Google created a two-tier system: legacy users with active implementations keep access while they migrate, but no new adopters can start using these fields through the Ads API. The concrete error for anyone who tries is CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in partial-failure responses.

Affected conversion imports return CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in partial-failure responses when using blocked data fields.

The migration path Google recommends is straightforward in theory: temporarily remove session attributes and IP addresses from Ads API conversion import requests, update the pipeline to send that data through the Data Manager API instead, then discontinue Ads API conversion imports once the Data Manager integration is working. In practice, for WooCommerce stores that built custom conversion pipelines, this requires re-engineering the data flow from the ground up.

The June 15 Block: Offline Conversions Join the Migration

The June 15 cutoff extends the migration mandate beyond session and IP data to offline conversion imports as a category.

Starting June 15, 2026, Google blocked new offline conversion imports and enhanced conversions for leads uploads through the Ads API entirely. The Data Manager API is the designated replacement. This is the third and broadest cutoff — it doesn’t just restrict specific data fields within conversion imports; it restricts the import pathway itself.

From June 15, 2026, Google blocked new offline conversion imports via the Ads API, completing the third sequential cutoff in six months.

For WooCommerce stores that import offline or CRM conversion data — order data from their backend, phone call conversions, or lead-qualification events — the June 15 cutoff means any new integration must use the Data Manager API from the start. The Ads API remains available for existing users during a transition period, but the direction is unambiguous: the Data Manager API is the long-term infrastructure for all first-party data ingestion.

Enhanced Conversions Merge: One Toggle to Rule Them All

The separate enhanced conversions products — web and leads — collapsed into a single feature in June 2026, simplifying the interface while obscuring whether the underlying data is actually working.

Before June 2026, enhanced conversions for web and enhanced conversions for leads were separate features with separate settings screens. Advertisers had to choose one implementation method per conversion action: the Google tag, Google Tag Manager, or the API. Starting in June, both products merged into a single on/off toggle, and the method selection screen disappeared entirely.

From April 2026, Google began accepting user-provided data through tags, Data Manager, and API connections simultaneously — eliminating the requirement to pick one method. The practical effect is that Google now ingests hashed user data from whichever source sends it first, which is simpler to configure but harder to audit.

For WooCommerce stores, the risk is specific. Seresa’s analysis found that 67% of first-implementation enhanced conversions setups on WooCommerce fail audit — the hashed user data that makes the feature work never reaches Google in a usable form. The toggle says “on.” The conversion action shows activity. But the actual data matching that improves conversion measurement is broken, and the merged interface no longer provides the diagnostic surfaces that used to reveal the problem.

The Data Manager API: Where Everything Is Going

The Data Manager API isn’t just a replacement for the Ads API’s conversion import functionality — it’s a unified data ingestion layer that spans Google Ads, Google Marketing Platform, and Google Analytics.

Google launched the Data Manager API on December 9, 2025. Unlike the Ads API, which was designed for campaign management with conversion tracking added incrementally over the years, the Data Manager API is built specifically for data ingestion. It supports asynchronous processing, batch validation, and a unified schema that works across Google’s entire measurement stack.

The practical advantages for WooCommerce stores are real: the Data Manager API handles the data volumes generated by session attributes and IP-based signals more reliably than the Ads API’s synchronous processing could. It also enforces a single data schema, which means data sent through the Data Manager API is structured identically regardless of whether it’s consumed by Google Ads, GA4, or Google Marketing Platform.

The challenge is that migrating to the Data Manager API requires development resources that most WooCommerce stores don’t have in-house. The API documentation is aimed at developers building enterprise measurement stacks, not store owners installing WordPress plugins. This is where the gap between Google’s infrastructure consolidation and the WooCommerce ecosystem’s reality becomes acute.

What This Means for WooCommerce Stores Without a Developer

The cascade of API cutoffs is an enterprise-scale infrastructure change — but WooCommerce stores without dedicated development teams are the ones most affected.

The typical WooCommerce store doesn’t interact with the Google Ads API directly. It uses a plugin — Google Listings & Ads, a tracking plugin, or a custom integration — that handles the data pipeline behind the scenes. The problem is that many of these plugins were built on the Ads API’s conversion import infrastructure, and not all have migrated to the Data Manager API yet.

If your conversion tracking plugin sends data through the Ads API and includes session or IP fields, the February cutoff already broke that pathway for new installations. If the plugin uses offline conversion imports, the June cutoff blocked new implementations. The store owner sees the same dashboard, the same “active” status — but the data pipeline underneath may have been silently severed by an API change the store owner was never notified about.

Checking is straightforward: look at the plugin’s changelog or documentation for mentions of “Data Manager API” migration. If the plugin hasn’t updated to use the Data Manager API, your conversion data may not be reaching Google Ads at all — and Smart Bidding is optimizing against a progressively incomplete signal.

You may be interested in: Google Is Force-Upgrading Your DSA Campaigns to AI Max — and AI Max Amplifies Whatever Signal It Can See

Why Server-Side Tracking Already Solves This

Server-side tracking tools that send conversion data through their own pipelines bypass the Ads API entirely — and many already use the Data Manager API or Google’s tag infrastructure natively.

The API cutoff cascade affects a specific pathway: direct Ads API conversion imports. Server-side tracking systems that capture the conversion at the WooCommerce order hook and send it to Google Ads through server-side Google Tag Manager, the Measurement Protocol, or the Data Manager API are unaffected by the Ads API restrictions — because they never used that pathway in the first place.

The Transmute Engine™ captures the conversion event at the WooCommerce server layer and routes it through authenticated server-to-server API calls. The data reaches Google Ads, GA4, and other platforms through infrastructure that’s already aligned with Google’s Data Manager architecture — no migration required because the pipeline was built for the server-side-first model from the start.

For WooCommerce stores facing the choice between migrating a broken Ads API integration to the Data Manager API or implementing server-side tracking that routes around the problem entirely, the second option is typically faster, more resilient, and future-proof against whatever API consolidation Google announces next.

Key Takeaways

• Three cutoffs in six months: Google sequentially blocked IP/session data (Feb 2), Customer Match (April 1), and offline conversion imports (June 15) for new Ads API adopters — all redirecting to the Data Manager API.
• Check your tracking plugin: If your WooCommerce conversion tracking plugin sends data through the Ads API and hasn’t migrated to the Data Manager API, your conversion data may no longer be reaching Google Ads.
• Enhanced conversions merged silently: The June 2026 toggle merge auto-migrated setups, but 67% of first-implementation WooCommerce enhanced conversions setups fail audit — a broken setup that looked active before still looks active now.
• Dormant tokens lose access permanently: Developer tokens that didn’t send API requests between January and June 2026 won’t be allowlisted for legacy Ads API access.
• Server-side tracking bypasses the entire cascade: Conversion pipelines that route through server-side GTM, the Measurement Protocol, or the Data Manager API are unaffected by the Ads API cutoffs.

References

• Search Engine Land. (2026). Google Ads API tightens conversion data rules. https://searchengineland.com/google-ads-api-tightens-conversion-data-rules-467263
• PPC Land. (2026). Google shuts down session tracking for new advertisers in Ads API. https://ppc.land/google-shuts-down-session-tracking-for-new-advertisers-in-ads-api/
• PPC Land. (2026). Google blocks new offline conversion imports via Ads API from June 15. https://ppc.land/google-blocks-new-offline-conversion-imports-via-ads-api-from-june-15/
• PPC Land. (2026). Google Ads finally collapses enhanced conversions into a single toggle. https://ppc.land/google-ads-finally-collapses-enhanced-conversions-into-a-single-toggle/
• Google Ads Help. (2026). Updates to your enhanced conversions settings. https://support.google.com/google-ads/answer/16884284
• Search Engine Land. (2026). Google Ads simplifies enhanced conversions into a single switch. https://searchengineland.com/google-ads-simplifies-enhanced-conversions-into-a-single-switch-474101
• ALM Corp. (2026). Google Ads API Implements Stricter Conversion Data Requirements. https://almcorp.com/blog/google-ads-api-conversion-data-changes-2026/

If your WooCommerce store’s conversion pipeline runs through the Google Ads API, talk to Seresa about server-side tracking that routes around the API cascade and sends data where Google’s infrastructure is actually going.