Google has added call-conversion support to its Data Manager API, alongside more precise diagnostics for uploaded records. For businesses that win work over the phone, the useful question is whether a worthwhile call outcome reaches Google Ads correctly, rather than whether an upload simply says it was accepted.
The official announcement, published on 4 November, is mainly aimed at developers and integration providers. A local business owner does not need to build an API connection to benefit from asking a few better questions about an existing one.
What has changed?
The Data Manager API is a software connection for sending information to Google’s advertising and measurement products. Its new call-conversion support lets an integration send events describing valuable customer actions arising from phone calls to Google Ads.
Google’s guide requires the time the call started, the time the conversion happened and an identifier for the caller. The conversion time cannot precede the call’s start time. The caller’s number must be formatted internationally, hashed using SHA-256 and encoded as specified. Hashing transforms the formatted number into a fixed-length value; it is a technical requirement, not a substitute for checking privacy obligations.
The announcement also adds record-level information to processing diagnostics. An integration can identify which individual records had errors or warnings, rather than investigating an undifferentiated batch. That distinction matters when most of an upload worked but a few important outcomes did not.
Why a phone-led business should care
Imagine a Somerset home-improvement firm receiving ten calls after people see its adverts. Some are unsuitable enquiries, some need a quotation and one becomes a booked job. This is an illustration, not a reported result. Counting every call equally would tell a different story from recording the outcomes the business actually values.
A reliable connection between call records and advertising measurement can help the team understand that difference. It does not guarantee that every call will be attributed, that bidding will improve or that revenue will rise. The definitions, matching information and handling of duplicates still need care.
This is part of the practical work behind Google Ads management for Bath businesses: agreeing what a worthwhile enquiry means and checking whether the reporting reflects it. The same question applies to firms across Bristol, Wiltshire and the wider South West that qualify customers by phone.
Accepted is only the first checkpoint
Google’s diagnostics documentation makes an important distinction. A successful ingestion response means the request was accepted for processing. It does not prove that every record was processed successfully. Processing happens afterwards, and a destination can finish with success, partial success or failure.
The new diagnostics identify affected records by their position in the original request. An error means a record was rejected; a warning means it was processed but some information was ignored. Even a successful destination can have warnings worth investigating.
For a business owner, the useful request to a supplier is straightforward: show the final processing result, explain rejected records and warnings, and reconcile them with the original call outcomes. An initial upload confirmation is useful evidence, but it is only one part of that check.
Five questions for your tracking supplier
- Does this apply to our setup? Ask whether call outcomes are uploaded, which connection handles them and whether this release changes anything. A working setup is not automatically due for replacement.
- What counts as a conversion? Distinguish an initial call from a qualified enquiry or a booked job. Document which outcome is sent and how repeated updates are handled.
- Are the records prepared correctly? Ask who checks caller-number formatting, hashing, timestamps and the intended conversion destination.
- Who checks the final result? Confirm that someone retains the request reference, follows processing through and investigates individual errors and warnings.
- How are corrections controlled? Google’s guidance says to send only corrected records when resolving processing problems, rather than replaying records that already succeeded. Ask how the integration prevents duplicates.
Keep the limits in view
The same release allows lead identifiers to be included with conversion events, but Google says attribution using the new lead ID and existing match ID is not available yet. Sending an identifier should therefore not be presented as proof that attribution is working.
Before changing any data sharing, check the business’s privacy information, permissions and supplier arrangements with whoever is responsible. This technical release does not decide those questions for you. If your current call reporting works, start with a documented review. Better evidence about what arrived and what failed is a sensible improvement; a hurried rebuild is not a requirement of this announcement.
