DV360 API v5 drops Customer Match uploads for Data Manager

Google released the beta of the Display & Video 360 API v5 on 22 October 2026. It removes the three methods that create, edit and fill Customer Match audiences. To keep uploading customer lists to DV360, you use the Data Manager API. With this release, both Google ad APIs that accepted Customer Match uploads point you to the same place.

What Google announced

The v5 release notes list the removed methods: firstPartyAndPartnerAudiences.create, editCustomerMatchMembers and patch. The contactInfoList and mobileDeviceIdList fields are removed too. You can still read audiences in v5, but you cannot create them or add members. Google’s migration guide says: “To continue managing Customer Match audiences, upgrade your workflows to use the Data Manager API.”

There is no deadline yet. v5 is a beta and can still change. The DV360 deprecation page lists no deprecation or sunset date for v4, so your v4 Customer Match code still works today. The deadline arrives when Google deprecates v4.

What we checked

We read every “upgrade from” guide in the Data Manager API documentation on 23 October and compared each one with the deprecation page of the API it replaces.

From	To the Data Manager API	Access cut
Google Ads API, Customer Match	audience uploads	1 April 2026, for developer tokens with no Customer Match calls from 1 Oct 2025 to 31 Mar 2026
Google Ads API, offline click conversions	conversion uploads	15 June 2026, for developer tokens with no uploads from 17 Dec 2025 to 15 Jun 2026
DV360 API, Customer Match	audience uploads	Methods removed in v5 (beta); v4 has no sunset date
Google Ads API, store sales	conversion uploads	None in the upgrade guide
Campaign Manager 360 API, offline conversions	conversion uploads	None in the upgrade guide
GA4 Measurement Protocol	server-side events	None in the upgrade guide

Six upgrade paths. Three have a cutoff or a removal, and the three cutoffs so far all hit audience and conversion uploads, the data that leaves your systems and reaches Google’s matching. Google’s Data Manager home page states the direction plainly: “All future functionalities, including encryption opportunities, and next-generation performance features will be launched exclusively on this platform.”

The read

This is one door for your first-party data. Customer lists, offline conversions, store sales, CM360 conversions and GA4 server events are all getting one ingestion API with one data model. For a team that runs audience syncs from a CRM or a CDP, that means one integration to maintain. It also means that one integration now decides what reaches Google’s matching, and so the match rate, in each product it feeds.

The move changes behaviour, not only endpoints. Three differences in Google’s own upgrade guides will change numbers if you migrate without testing:

• One bad record fails the whole request. The Data Manager API is fast-fail: if any record fails validation on a required field, nothing in that request is processed. The Google Ads and CM360 APIs used partial failure, so the valid rows went through. A Google Ads sync that used to land 9,990 of 10,000 members can now land none, and a job that does not read the error will not notice.
• Deduplication changes for CM360 conversions. CM360 deduplicated on the ordinal, per day, and accepted a constant ordinal. The Data Manager API deduplicates on Floodlight activity and transactionId. Reuse one transactionId for distinct sales and Google deduplicates them into one.
• The account you send to must own the conversion action. The Google Ads API accepted a manager or child account. The Data Manager API does not. An agency that uploads through its manager account must change the destination for each client.

DV360 uploads get a match rate for the first time. Google’s own comparison says the DV360 API “Provides no visibility besides the API request response”. The Data Manager API returns diagnostics for each request, with a match rate range when the request has enough records. Diagnostics are ready about 30 minutes after the upload. That is a data-quality signal DV360 users have never had, but only if someone reads it.

What to do

1. List every job that calls these APIs: CRM and CDP audience syncs, offline conversion uploads, Floodlight uploads, server-side GA4 events. Note the API each one uses and who maintains it, including vendor connectors.
2. Migrate the DV360 Customer Match job before v4 gets a date. The Data Manager API needs new credentials with its own OAuth scope, so start with access, not code.
3. Test the three behaviour changes before you switch. Send a batch with one bad record with validateOnly, send two distinct sales with one transactionId, and send to the account that owns the conversion action. Then read the diagnostics after 30 minutes and record the match rate range as your baseline.

A migration like this changes the pipe, so the same customer list or sale can arrive at Google formatted, hashed or keyed in a new way. Which fields does each ad platform expect, and how do you check what a tool actually sends before you trust its numbers? That test is the subject of switching ad trackers.