Google Data Manager API v1.9 Adds Call Conversions, Row-Level Diagnostics, and Lead IDs
On November 4, 2026, Google released version 1.9 of the Data Manager API. The release lets advertisers send call conversions to Google Ads, adds diagnostics that identify the individual records with errors or warnings, and adds the lead_id field to event identifiers for leads from Google lead forms. The Data Manager API team announced the changes on the Google Ads Developer Blog. The release notes and developer guides provide further details.
How Call Conversions Were Uploaded Before This Release
The Data Manager API provides a single way for advertisers to send first-party data to Google’s advertising products. Version 1.2, released in August 2025, added offline conversions and enhanced conversions for leads. Customer Match, store sales, and Google Analytics events followed.
Before version 1.9, teams uploaded call outcomes, such as orders or qualified leads, through the Google Ads API. Teams that had already moved their other uploads to the Data Manager API had to maintain a separate integration for calls.
How to Send Call Conversions Through the Data Manager API
Send call conversions to a Google Ads conversion action of type UPLOAD_CALLS. Google Ads displays Call from Ads as the source for this action. In the request, specify the Google Ads account that owns the conversion action as the operating account and identify the action by its numeric ID. Data partners send events on behalf of advertisers through a partner link using a DATA_PARTNER account. Each event requires three fields.
- call_info.start_timestamp records when the call started.
- event_timestamp records when the conversion happened. If it is earlier than the start of the call, the API returns CONVERSION_PRECEDES_CALL.
- user_data contains the caller’s phone number.
Optional data includes the event source (Google’s example uses PHONE), the conversion value, an ISO 4217 currency code, custom variables, and the ad_user_data and ad_personalization consent settings. Consent can be set once for the entire request. The validate_only flag checks the request for errors without uploading the data.
The release also added three call-related processing errors: PROCESSING_ERROR_REASON_TOO_RECENT_CALL, PROCESSING_ERROR_REASON_EXPIRED_CALL, and PROCESSING_ERROR_REASON_INVALID_CALL. Google does not specify the time thresholds for a call to be considered too recent or expired.
Phone Number Requirements
A technical difference between the two APIs is how they handle the caller’s number. The Google Ads API accepts the plain-text number in caller_id. For the Data Manager API, first normalize the number to E.164 format, for example +18005550199, then hash it with SHA-256 and encode it as hex or Base64. Set the corresponding encoding in the request-level encoding field.
This upload flow does not support encryption. Leave encryptionInfo unset, as supplying encryption information triggers ENCRYPTION_NOT_SUPPORTED. An invalid number format triggers the warning WARNING_REASON_INVALID_NUMBER_FORMAT.
Differences From Uploading Through the Google Ads API
Google’s migration guide compares the two APIs. Several differences affect how teams build their ingestion pipelines.
- Error handling. The Google Ads API supports partial failure, so valid rows go through and invalid rows are rejected individually. The Data Manager API uses fast-fail validation: if any event fails validation, the entire request is rejected.
- Duplicates. The Google Ads API rejects duplicate call conversions with CALL_CONVERSION_ALREADY_EXISTS. The Data Manager API accepts them without returning an error, and Google Ads deduplicates them after processing.
- Access and quotas. The Data Manager API requires credentials with a separate OAuth scope. A developer token and access-level approval are unnecessary. Quotas apply per project.
Row-Level Diagnostics With record_indices
The Data Manager API processes events asynchronously. A successful response means the request was accepted for processing. Check whether individual records were processed by calling RetrieveRequestStatus with the request_id. Previously, diagnostics showed how many records triggered each error or warning, without identifying the affected records.
In version 1.9, ErrorCount and WarningCount gained the record_indices field, which lists the zero-based positions of affected records in the original request. For example, [0, 3] for PROCESSING_ERROR_REASON_CLICK_NOT_FOUND means the first and fourth events failed for that reason. Indices are reported separately for each destination, and one record can appear under more than one reason.
Google recommends resending only corrected records that failed. Resending records that processed successfully can create duplicates. Records with warnings can still be processed, but some data is ignored. Correct the cause of a warning in future uploads. Google suggests checking the status for the first time 30 minutes after upload. Processing can take up to 24 hours.
The lead_id Field and Attribution Limits
The third change concerns leads from Google lead forms. The new lead_id field in ad_identifiers carries the identifier Google generates when a user submits a lead form. Advertisers can include lead_id and match_id, introduced in version 1.7, as event identifiers for offline and multisource events sent to Google Ads, Floodlight, and Google Analytics.
Attribution using lead_id or match_id is still unavailable, and Google has not announced a launch date. Google recommends sending other identifiers alongside them so events can be attributed. A lead_id alone cannot yet connect a conversion to an ad.
What This Means for Advertisers
Advertisers and data partners can now send Google Ads call conversions through the same integration they use for other offline data. This is particularly useful for businesses that close sales by phone, such as home services, legal, healthcare, and insurance companies, and for agencies that send offline conversions for clients.
Migration requires teams to normalize and hash phone numbers, account for fast-fail validation, and check processing results asynchronously. The record_indices field makes large uploads easier to correct because teams can resend only the affected records. The lead_id field can be sent today, with attribution support still pending.
Sources
- Google Ads Developer Blog, Data Manager API now supports Google Ads call conversions and row-level diagnostics, November 4, 2026
- Google for Developers, Data Manager API release notes, v1.9, November 4, 2026
- Google for Developers, Send events for Google Ads call conversions
- Google for Developers, Upgrade from the Google Ads API for call conversions
- Google for Developers, Check request status and diagnostics
- PPC Land, Google's Data Manager API accepts call conversions, but only hashed numbers, November 8, 2026



