Reference
Field mapping: Google Ads API → Data Manager API
Every offline conversion field in the legacy Google Ads API and CSV template, mapped to its Data Manager API equivalent. This is the same mapping data the converter tool uses.
Verified against the official
Data Manager API upgrade guide.
Three changes cause most migration failures: the timestamp format (now RFC 3339),
the conversion action (now a request-level numeric ID, not a per-row name), and
click IDs moving into the nested ad_identifiers object.
Event fields (per conversion row)
| Legacy CSV column | Google Ads API field | Data Manager API field | Required | Notes |
|---|---|---|---|---|
Google Click ID | ClickConversion.gclid | events[].ad_identifiers.gclid | conditional | String click identifier from the ad click URL. At least one of gclid, gbraid, or wbraid is required per row. In the Data Manager API it moves into the nested ad_identifiers object. |
GBRAID | ClickConversion.gbraid | events[].ad_identifiers.gbraid | conditional | iOS campaign-level click identifier (App Tracking Transparency). Alternative to gclid for iOS traffic. Nested under ad_identifiers in the Data Manager API. |
WBRAID | ClickConversion.wbraid | events[].ad_identifiers.wbraid | conditional | iOS web-to-app click identifier (App Tracking Transparency). Alternative to gclid for iOS traffic. Nested under ad_identifiers in the Data Manager API. |
Conversion Name | ClickConversion.conversion_action (resource name) | destinations[].product_destination_id (numeric conversion action ID) | required | Legacy: the conversion action name, matched exactly. Data Manager API: the numeric conversion action ID. The biggest structural change: the conversion action moves from each row to the request-level destination, and it is identified by numeric ID instead of name. Find the ID in Google Ads under Goals > Conversions (ctId= in the URL). |
Conversion Time | ClickConversion.conversion_date_time | events[].event_timestamp | required | Legacy: "MM/dd/yyyy HH:mm:ss" or "yyyy-MM-dd HH:mm:ss", timezone via offset or Parameters:TimeZone. Data Manager API: RFC 3339, e.g. 2026-06-20T15:07:01Z. The timestamp format changed. RFC 3339 requires a T separator and an explicit offset (or Z for UTC). The legacy Parameters:TimeZone header row no longer exists — every timestamp carries its own timezone. |
Conversion Value | ClickConversion.conversion_value | events[].conversion_value | optional | Decimal currency value, e.g. 150.25. Unlike other Google Ads API money fields, this is the plain currency value — never micros (5.23, not 5230000). |
Conversion Currency | ClickConversion.currency_code | events[].currency | optional | Three-letter ISO 4217 code, e.g. USD. Field renamed from currency_code to currency. |
Order ID | ClickConversion.order_id | events[].transaction_id | optional | String identifier unique per conversion. Renamed to transaction_id. Used for deduplication across data sources. |
Request-level fields
These fields configure the upload itself. In the Google Ads API they were request parameters or
HTTP headers; in the Data Manager API most of them live in the destinations object.
| Google Ads API | Data Manager API | Notes |
|---|---|---|
UploadClickConversionsRequest.customer_id | destinations[].operating_account.account_id (account_type: GOOGLE_ADS) | Moves into the destination object with an explicit account_type. |
developer-token header | No equivalent | No longer needed. The Data Manager API does not require a developer token. |
UploadClickConversionsRequest.partial_failure | No equivalent | Not supported. The Data Manager API processes events asynchronously; use the returned request_id to retrieve diagnostics. |
UploadClickConversionsRequest.validate_only | validate_only | Same field name in both APIs. Useful for testing a payload without recording conversions. |
ClickConversion.conversion_environment | No equivalent | No Data Manager API equivalent. This data is dropped in migration. |
ClickConversion.external_attribution_data | No equivalent | No Data Manager API equivalent. If you rely on external attribution, review your setup before migrating. |
Convert a file now
The converter applies this mapping automatically and validates every row — entirely in your browser. See also the timestamp format cheatsheet and the full migration guide.