Upgrade your 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 conversions.
| Data Manager API | Google Ads API | |
|---|---|---|
| Support for sending offline conversions and enhanced conversions for leads | Supported. | Supported. |
| Support for sending Google Ads tag conversions as an additional data source for your tag conversions, to maximize ad interaction signals and strengthen your data and overall performance | Supported. | Not supported. |
| Data model | Unified data model across all Google Ads conversion use cases and all Google advertising products. | Data model is only for Google Ads use cases, and differs for each use case. |
| Encryption | Supports encryption. | Not supported. |
| Developer token | Not required. | Required. |
| Support for uploading session attributes and IP addresses for events | Available to all API users. | Only available to specific API users. |
| Quotas and limits | Project-based quotas and per-request limits. | Developer token-based quotas and per-request limits. |
| Error model | Uses a fast-fail model. | Uses a partial failure model. |
Difference in destination account requirements
In the Data Manager API, the operating_account of the
destination must be the
Google Ads conversion customer. This differs from the Google Ads API.
The Google Ads API supports sending conversions for a Google Ads account using the
customer_id of either:
The Google Ads conversion customer.
The Data Manager API supports this approach.
Any account that is a parent or descendant of the Google Ads conversion customer.
The Data Manager API doesn't support this approach. If you're utilizing this behavior in the Google Ads API, change the
operating_accountof each destination to the owner of the conversion action. This may differ from thecustomer_idyou use in your Google Ads API requests.