Optional default consent settings for events in the request. You can override this value for an individual event by setting the consent field of Event.
No equivalent
encoding
Required: Set to the Encoding used for UserIdentifier values.
No equivalent
encryption_info
Set if the request contains encrypted values. See Encryption for details.
job_id
No equivalent
Use the request_id returned in the response to retrieve diagnostics.
partial_failure
No equivalent
The Data Manager API doesn't support partial failure. If any field of an IngestEventsRequest fails validation, the Data Manager API rejects the entire request.
The Google Ads API requires the developer-token request header, and you set the
login-customer-id and linked-customer-idrequest headers for different authentication scenarios.
The Data Manager API doesn't require a developer token, and you specify login and
linked customer information using fields of a Destination instead of request
headers. Check out Configure destinations for more
information about destinations.
Here's how to map the Google Ads API fields for a single conversion_action
to the equivalent fields in a Destination:
A developer token is not required for the Data Manager API.
login-customer-id request header
login_account
Set the account_id to the customer ID of the login account. Set account_type to GOOGLE_ADS if the login account is a Google Ads account, or DATA_PARTNER if the login account is a data partner account.
linked-customer-id request header
linked_account
Set the account_id to the customer ID of the linked account. Set account_type to DATA_PARTNER.
conversion_action of a ClickConversion
product_destination_id
Set to the numeric ID of the conversion action. Don't use the resource name of the ConversionAction.
Both APIs use a similar Consent object (ad_user_data, ad_personalization).
For the Data Manager API, you can also set consent for all events in
a request by setting the request-level consent field.
The Google Ads API requires separate requests per conversion action. The Data Manager API supports sending conversions for multiple conversion actions in a single request, as well as using this destination_references field to indicate which destinations should receive a specific custom variable.
conversion_custom_variable
variable
Set to the name of the variable instead of a resource name.
Neither API supports these identifiers for offline conversions or enhanced conversions for leads,
and the Data Manager API doesn't support these identifiers when sending conversion events as an additional data source.
Use the request_id returned in the response to retrieve diagnostics.
partial_failure_error
No equivalent
The Data Manager API doesn't support partial failure. If any field of an IngestEventsRequest fails validation, the Data Manager API rejects the entire request.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2026-02-12 UTC."],[],[]]