Observed Signal · May 15, 2026 · Deprecation · Source: https://www.blogger.com/feeds/7815614485808579332/posts/default?category=google_ads_api&orderby=published · Impact: 4/5 · Sentiment: Negative

Google Ads API Ends New Offline Conversion Imports

Executive Signal Summary

On May 15, 2026 Google announced that starting June 15, 2026 the Google Ads API will stop accepting new adopters of offline conversion imports, including Enhanced Conversions for Leads. Google names the Data Manager API as the primary API for importing offline conversions and published a migration guide for Google Ads API users. Developers who have not adopted offline conversion imports or who did not import offline conversions between December 2025 and May 2026 will receive an error when attempting imports; existing adopters may continue using the Google Ads API while they integrate with the Data Manager API. Allowlisting will be managed by developer token and the specific error returned for blocked attempts is CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when calling ConversionUploadService.UploadClickConversions. The post is authored by Ben Karl on behalf of the Google Ads API Team.

Polaris7 AgentPolaris7 Strategic Assessment
High Confidence

A policy/technical support change from Google (a major platform) affecting offline conversion import workflows and developer integrations; requires migration to the Data Manager API and will impact measurement, attribution, and tooling across advertisers and vendors.

SIGNAL RADAR

Track Google Signals & Market Shifts in Real-Time

Polaris7 autonomous intelligence agents track regulatory filings, primary sources, executive changes, and deal flow 24/7. Create your free Explorer workspace to monitor these entities.

Start Free in Explorer
Free Explorer tierNo credit card requiredInstant watchlist setup

Key Takeaways & Evidence Grounding

  • Starting June 15, 2026 the Google Ads API will no longer accept new adopters of offline conversion imports, including Enhanced Conversions for Leads.
  • Google designates the Data Manager API as the primary API for importing offline conversions and published a migration guide for Google Ads API users.
  • Developers who have not adopted offline conversion imports or who did not import offline conversions between December 2025 and May 2026 will receive an error when attempting imports.
  • The error returned for blocked attempts is CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE when calling ConversionUploadService.UploadClickConversions.
  • Developers will be allowlisted by their developer token; existing adopters can continue importing via the Google Ads API while migrating to the Data Manager API.
Primary Source Grounding & Direct Attribution
Direct Origin Attribution
Original Coverage Title: “entry”

Related Market Signals & Shifts

Recent verified developments and strategic activity across this market segment.

Conversion Tracking & AttributionMar 26, 2026

Google Ads API Offline Conversion Import Improvements

Starting April 2026 Google is rolling out infrastructure upgrades to the Google Ads API to improve the Offline Conversion Import experience. The changes are non‑breaking but may cause minor attribution fluctuations during rollout. Key improvements include (1) improved attribution and fallback recovery to allow attribution for some expired GCLIDs and clicks that occurred before a conversion, reducing EXPIRED_EVENT and CONVERSION_PRECEDES_EVENT errors and potentially increasing attribution rates; and (2) a flexible import-request authorization model (April–May 2026) to make it easier for manager or client accounts to import conversions on behalf of different trafficking accounts, reducing UNAUTHORIZED_CUSTOMER and INVALID_CUSTOMER_FOR_CLICK errors. Google points users to guidance on maximizing conversion data performance, a Data Manager API migration guide for Google Ads API users, and Google Ads API support (and a community Discord) for questions. The post is authored by Ben Karl on behalf of the Google Ads API Team.

Read assessment
IdentityJan 7, 2026

Google Ads API Phasing Out IP and Session Data

Starting February 2, 2026, the Google Ads API will stop accepting new adopters of session attributes and IP address data in conversion imports. Developers who already include those fields may continue using the Google Ads API until they migrate. Google recommends moving conversion and user-data imports to the Data Manager API, which accepts session attributes and IP address values. Developers will be allowlisted by developer token; after rollout, conversion imports containing session attributes or IP address may return the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE in partial_failure responses. Google outlines remediation steps: temporarily remove those fields from Google Ads API imports, update code to use the Data Manager API, and discontinue Google Ads API imports once Data Manager imports are functioning. Support channels and a Google Advertising and Measurement Community Discord are provided for questions. The post is by Ben Karl on behalf of the Google Ads API Team.

Read assessment
IdentityMar 4, 2026

Google Ads API Phasing Out Customer Match by 2026

Starting April 1, 2026, the Google Ads API will stop accepting new adopters of Customer Match and recommends new adopters use the Data Manager API for user-data imports. Developers who have not adopted Customer Match, or who have not uploaded data to a Customer Match list between October 2025 and March 2026, will receive an error when attempting uploads. Existing Customer Match adopters may continue using the Google Ads API while they migrate to the Data Manager API. Google will allowlist developers by developer token; non-allowlisted uploads via OfflineUserDataJobService or UserDataService will return the error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE. Google points developers to Data Manager API documentation and support channels for questions.

Read assessment

Track Real-Time Market Signals & Shifts

Set up custom watchlists to receive automated, evidence-grounded executive digests whenever material signals or shifts occur across your tracked landscape.