Google Data Manager API 支持 Google Ads 通话转化与行级诊断
Data Manager API now supports Google Ads call conversions and row-level diagnostics
Google Data Manager API 最新版本正式支持 Google Ads 通话转化回传与行级诊断功能。开发者可通过新增的 `call_info` 字段与哈希电话号码记录通话转化事件，并通过诊断返回的 `record_indices` 索引精确排查和重发失败记录；此外，API 新增了表单线索 `lead_id` 字段，但该标识符的归因支持目前尚未正式上线。
更新补充了行级报错索引和通话转化字段，开发者可据此直接精确定位数据接入异常并补齐离线追踪链路。
The latest release 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
You can now use the Data Manager API to send call conversions to Google Ads. 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
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:
-
See
Check affected records
in the diagnostics guide to learn how to use
record_indices. - Review the release notes for the full list of changes.
Building with AI coding tools? Explore the Data Manager API agent skills 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. You can also contact us through the support page 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.
来源：Google Ads Developer Blog · ads-developers.googleblog.com