Upgrade your [Customer Match](https://developers.google.com/display-video/api/guides/audiences/upload-customer-match) audience management from the
[Display \& Video 360 API](https://developers.google.com/display-video/api) to the Data Manager API to gain access to future
improvements and features.

The Data Manager API supports the following Display \& Video 360 features:

- Create and manage [Customer Match audiences](https://support.google.com/displayvideo/answer/9539301).
- Upload user data to add and remove members from Customer Match audiences.

Here's a comparison between using the Data Manager API and the Display \& Video 360 API to manage
Customer Match audiences:

|   | Data Manager API | Display \& Video 360 API |
|---|---|---|
| Data model | Unified data model across all audience use cases and Google advertising products. | Data model is specific to the Display \& Video 360 use case. |
| Workflow visibility | Supports retrieval of [diagnostics](https://developers.google.com/data-manager/api/devguides/diagnostics) for each data ingestion, which includes [processing status](https://developers.google.com/data-manager/api/devguides/diagnostics#destination_status) and a [match rate range](https://developers.google.com/data-manager/api/reference/rest/v1/requestStatus/retrieve#IngestUserDataStatus.FIELDS.upload_match_rate_range). Yes | Provides no visibility besides the API request response. No |
| Support for [confidential matching](https://support.google.com/google-ads-data-manager/answer/14577185) | Supported. Yes | Not supported. No |
| Encryption | Supports [encryption](https://developers.google.com/data-manager/api/devguides/concepts/encryption). Yes | Not supported. No |
| Manage multiple audiences | Send data to [multiple audiences in the same request](https://developers.google.com/data-manager/api/devguides/audiences/send-audience-members#multiple-destinations). Yes | Separate offline jobs and requests required for each audience. No |
| Remove all audience members | Supports [removing all members with a single request](https://developers.google.com/data-manager/api/devguides/audiences/display-video/customer-match/remove-all-members) as well as removing individual members. Yes | Only supports removing each member individually. No |
| Full partner-level user list management | Supports full management and data ingestion for partner-level user lists. Yes | Supports only the retrieval of partner-level user lists. No |
| Future support | Will support new Customer Match features in the future. Yes | Will no longer be updated. No |
| Quotas and limits | Project-based [quotas and per-request limits](https://developers.google.com/data-manager/api/devguides/limits). | [Project and advertiser-based quotas](https://developers.google.com/display-video/api/limits) and per-request limits for [contact information](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#contactinfolist) and [mobile ID](https://developers.google.com/display-video/api/reference/rest/v4/firstPartyAndPartnerAudiences#mobiledeviceidlist) lists. |

## Difference in authentication requirements

In a Data Manager API request, a [destination](https://developers.google.com/data-manager/api/devguides/concepts/destinations#dv3-partner-access) specifies
the Display \& Video 360 resource that receives the provided data and the Display \& Video 360 user
access.

Users with advertiser-level access can only manage user lists under that
advertiser. Users with partner-level access can manage user lists under that
partner and under the advertisers within that partner. If you have partner-level
access and manage an audience under an advertiser, you must
[specify your partner-level access](https://developers.google.com/data-manager/api/devguides/concepts/destinations#dv3-partner-access)
in the `login_account` of the [destination](https://developers.google.com/data-manager/api/devguides/concepts/destinations#dv3-partner-access).