Counting calls from Google Ads is easy. Knowing which of those calls turned into paying work is harder, and it's the number that should decide where your ad money goes. Some businesses close that gap by sending Google a list of the calls that became real jobs. That's called uploading call conversions.
On November 4, 2026, Google announced that its Data Manager API now accepts those Google Ads call conversions, and that it reports problems row by row. Here is what that means in plain terms, and what to ask whoever handles your tracking.
Who this is for
If you only use the call tracking built into Google Ads and never upload anything, this doesn't change your day. It matters if your CRM, a call tracking service or your agency sends call results back to Google. Until now that went through the Google Ads API. Google now recommends the Data Manager API for it instead.
Google's upgrade guide does not say the Google Ads API method is being retired, and it gives no deadline. So this is something to plan, not an emergency.
What gets sent for each call
According to Google's guide, each call conversion needs:
- The caller's phone number, written in international format (for example +1 and the 10 digits) and hashed before it leaves your system. The Google Ads API took the number as plain text; Data Manager does not.
- When the call started.
- When the conversion happened, which can't be earlier than the call start.
- The Google Ads account that owns the conversion action.
- The conversion action, which has to be the “Call from Ads” type.
A value and currency are optional. Notice what is not on the list: keyword, landing page or campaign. Google matches the call back to the ad itself. Your job is to send the right caller, the right times and the right conversion action.
What row-level diagnostics add
Google's post makes a point worth knowing: a batch being accepted does not mean every call in it was processed. The new diagnostics list which records had problems, by their position in the batch, along with the reason.
- Errors mean the record was rejected. Fix it and send it again.
- Warnings mean the record was accepted but some of its data was ignored. Fix the cause for future uploads.
Two other differences from the Google Ads API: Data Manager rejects the whole request if one record is invalid, so Google suggests a validation-only run first. And it accepts duplicate calls without an error, then removes them after processing, where the Google Ads API rejected them outright.
Questions to ask your agency or tracking provider
- Do we upload call conversions to Google Ads today, and from which system?
- Are you planning to move those uploads to the Data Manager API, and when?
- Which conversion action do the uploads use, and does it count only the calls we care about, like booked jobs?
- Who looks at rejected records and warnings, and how often?
- If one call is recorded in two places, which system is allowed to send it?
The last one matters even though Google now removes duplicates. You still want one system that owns each call, so your own reports match what Google shows.
The checklist
- Know whether anyone uploads your call conversions
- Know which system sends them
- Conversion action is the "Call from Ads" type
- Upload counts the calls that matter, not every ring
- Someone reviews rejected rows and warnings
- One system owns each call
Where the website comes in
Better call data tells you which ads bring in work. It can't fix a landing page that hides the phone number or loads slowly on a phone. If you want us to look at the pages your ads point to, send them over and we'll tell you what we'd fix first. For counting calls from AI search as well, see how to track calls from AI search.
Questions
Do I need to change anything right away?
No. Google recommends moving call conversion uploads from the Google Ads API to the Data Manager API, but its guide does not say the old method is going away or give a deadline. If your uploads work today, they keep working.
Does this matter if I only use Google's own call tracking?
Not much. This is for businesses that send call results back to Google themselves, usually through a CRM, a call tracking service or an agency. If you never upload calls, nothing changes for you.
What does a call conversion upload contain?
At minimum: the caller's phone number (hashed before it is sent), the time the call started, the time the conversion happened, the Google Ads account and the conversion action. The conversion action has to be the "Call from Ads" type.
What are row-level diagnostics?
When you send a batch of calls, Google now tells you which records had problems, by their position in the batch. Errors mean the record was rejected and needs fixing and resending. Warnings mean it was accepted but some data was ignored.
Sources
- Google Ads Developer Blog: Data Manager API now supports Google Ads call conversions (November 4, 2026)
- Data Manager API: Send call conversions
- Data Manager API: Upgrade call conversions from the Google Ads API
Drafted with AI assistance and checked against Google's announcement and guides on November 13, 2026.
