Upgrade your store sales conversion uploads from the Google Ads API to the
Data Manager API to gain access to several improvements and features.

Here's a comparison between using the Data Manager API and the Google Ads API to manage
store sales conversions.

|   | Data Manager API | Google Ads API |
|---|---|---|
| Ingestion workflow complexity | Streamlined workflow consisting solely of ingestion requests. Yes <br /> No management of jobs is required. | Job workflow that requires creating, populating, running, and monitoring offline jobs. No |
| Encryption | Supports [encryption](https://developers.google.com/data-manager/api/devguides/concepts/encryption). Yes | Not supported. No |
| Support for [confidential matching](https://support.google.com/google-ads-data-manager/answer/14577185) | Supported. Yes | Not supported. No |
| Developer token | Not required. | Required. |
| Data model | Unified data model across all Google advertising products. | Data model is only for Google Ads use cases. |
| Multiple destinations | Supports sending events to [multiple destinations in a single request](https://developers.google.com/data-manager/api/devguides/events/google-ads/store-sales/send-events#multiple-destinations). Yes | Separate offline jobs are required to upload store sales conversions to multiple accounts. No |
| Multiple items | Supports sending multiple items in a single event using [`CartData`](https://developers.google.com/data-manager/api/reference/rpc/google.ads.datamanager.v1#cartdata). Yes | Supports only a single item per transaction. No |
| Error model | Uses a [fast-fail model](https://developers.google.com/data-manager/api/devguides/concepts/understand-errors#fast-fail). | Uses a [partial failure model](https://developers.google.com/google-ads/api/docs/best-practices/partial-failures). |