Observed Signal · Mar 4, 2026 · Policy Update · Source: https://www.blogger.com/feeds/7815614485808579332/posts/default?category=google_ads_api&orderby=published · Impact: 5/5 · Sentiment: Negative
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.
Major platform (Google) policy/API change affecting identity and user-data ingestion workflows; requires developers to migrate to Data Manager API and will impact integrations and onboarding for Customer Match.
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.
Key Takeaways & Evidence Grounding
- Google Ads API will not accept new adopters of Customer Match starting April 1, 2026.
- Google recommends new adopters integrate with the Data Manager API as their primary user-data import API.
- Developers who have not adopted Customer Match or not uploaded data between October 2025 and March 2026 will receive an error when attempting to upload to a Customer Match list.
- Non-allowlisted uploads to Customer Match via OfflineUserDataJobService or UserDataService will return error CUSTOMER_NOT_ALLOWLISTED_FOR_THIS_FEATURE.
- Developers will be allowlisted for Customer Match by their developer token; existing adopters can continue importing while integrating with Data Manager API.
Connected Companies & Entities
3 Entities mappedOntology Mapping & Concepts
Related Market Signals & Shifts
Recent verified developments and strategic activity across this market segment.
Google Ads API Ends New Offline Conversion Imports
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.
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.
Data Manager API: GMP Events and IP Ingestion
Google’s Data Manager API has added support for sending offline conversion events to Google Marketing Platform products — Campaign Manager 360, Search Ads 360, and Display & Video 360 — using an expanded AdIdentifiers object (now including dclid, impressionId, matchId and encryptedUserIds). The API also introduces a CompositeData field that enables IP address ingestion (with observation timestamps) for Google Ads Customer Match uploads; Google says providing IP + timestamp will help drive higher match rates beginning in Q3 2026. Google recommends upgrading from the older Campaign Manager 360 conversion upload API to Data Manager API for a unified schema, encrypted user identifiers, and multi-destination routing. User_data continues to be supported, but composite_data is recommended to prepare integrations for future features.
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.