Wednesday, November 4, 2026


The
[latest release](https://developers.google.com/data-manager/api/reference.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-changelog#2026-11-04_v19)
of the Data Manager API adds support for Google Ads call conversions. It also
adds row-level details to diagnostics to help you find and fix the exact
records that had problems during processing.

## Send call conversions to Google Ads

<br />


You can now use the Data Manager API to
[send call conversions to Google Ads](https://developers.google.com/data-manager/api/devguides/events/google-ads/call.md.txt). Call conversions track when your ads lead to phone calls and when those
calls lead to valuable customer actions.


To send a call conversion, set the new
`call_info`
field on the event. Its `start_timestamp` holds the time the phone
call started. Identify the caller with a hashed phone number in
`user_data`.

## Row-level errors and warnings in diagnostics


A successful ingestion request doesn't guarantee that every record was
processed. The Data Manager API now tells you which records had problems
during processing. When you
[check request status and diagnostics](https://developers.google.com/data-manager/api/devguides/diagnostics.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-diagnostics-guide)
for a request, each
`ErrorCount`
and
`WarningCount`
now includes a `record_indices` field. This field lists the 0-based
positions of the affected records in your original request.


For example, a `record_indices` value of `[0, 3]` on an
`ErrorCount` with reason
`PROCESSING_ERROR_REASON_CLICK_NOT_FOUND` means the first and
fourth events in your request failed for that reason. Use these indexes with
the error reason to correct the failed records and resend them. Records with
warnings weren't rejected, but some of their data was ignored, so fix the
cause of the warning in future requests.

## Send lead IDs with your conversions


Use the new
`lead_id`
field in `ad_identifiers` to send the Google-generated ID that's
issued when a user submits a lead form. You can include
`lead_id` and the existing `match_id` field as event
identifiers for offline and multi-source events sent to Google Ads,
Floodlight, and Google Analytics destinations.


Attribution using `lead_id` and `match_id` isn't
available yet. Until it is, include other identifiers to ensure events are
attributed.

## Get started

- Start sending call conversions:
  - [Send call conversions](https://developers.google.com/data-manager/api/devguides/events/google-ads/call/send-events.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-sendcall-guide)
  - [Upgrade call conversions from the Google Ads API](https://developers.google.com/data-manager/api/devguides/events/google-ads/call/upgrade.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-callupgrade-guide)
- See [Check affected records](https://developers.google.com/data-manager/api/devguides/diagnostics.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-recordindices-guide#record_indices) in the diagnostics guide to learn how to use `record_indices`.
- Review the [release notes](https://developers.google.com/data-manager/api/reference.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-changelog#2026-11-04_v19) for the full list of changes.


**Building with AI coding tools?** Explore the
[Data Manager API agent skills](https://developers.google.com/data-manager/api/devguides/quickstart/agent-skills.md.txt?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=learnmore-agentskills-guide)
to get more accurate, efficient guidance directly in your AI-assisted coding
environment.


If you have any questions or want to discuss this post, reach out to us on our
[Google Advertising and Measurement Community Discord server](https://goo.gle/ads-and-measurement-discord). You can also contact us through the
[support page](https://developers.google.com/data-manager/api/support/contact?utm_campaign=adr-dm-api-r8&utm_source=googleblog-adsdevs&utm_medium=blog&utm_content=contact-support)
if you have an issue or need help with the API.


If you're interested in becoming a data partner, please fill out the
[Partner Interest Form](https://docs.google.com/forms/d/e/1FAIpQLScFEkLVqElsjYJ21h7z0mSUk8Tj1M3TEMwouFPQb7qyM-oI5w/viewform?utm_source=googleblog-adsdevs&utm_medium=blog&utm_campaign=adr-dm-api-r8&utm_content=contact-partner-interest-form).

![Portrait of the author](https://developers.google.com/static/ads/blog/images/AVvXsEiChe_g1JujivrmFreqOSiiJVG79VFlvDXoigneV-ZD8m1fDd6MfMyi3dGgc4PYhLKJrzb_QxVMM7jqCfqNpWk3CxmsvDxSvdiGwgqUlPZ0NIhAGdRJXiNeWj77GTFI3bAdcnNr8VamYJEFSi1GdAzq4UuiY3w5EZpXQzHWQDHTI8Hf-9aU3rI3Q_Vdutc.jpg) - Lindsey Volta, on behalf of the Data Manager API Team

**Labels:**

[conversions](https://developers.google.com/ads/blog/feeds/labels/conversions.md.txt),

[data-manager-api](https://developers.google.com/ads/blog/feeds/labels/data-manager-api.md.txt),

[release](https://developers.google.com/ads/blog/feeds/labels/release.md.txt)