Data Manager API Call Conversions: What Changed in 2026

Google has added call conversions to the Data Manager API. Since November 4, 2026, developers, agencies and call tracking tools can send phone call outcomes to Google Ads through the Data Manager API instead of the Google Ads API.

The same release adds row-level diagnostics, so you can finally see exactly which records in an upload failed and why, plus a new lead ID field. For local service businesses whose best leads arrive by phone, this matters because those call outcomes feed Smart Bidding.

Here’s what changed, how it differs from the old Google Ads API method, and what to ask your developer or call tracking provider.

Key takeaways

  • You can now send Google Ads call conversions through the Data Manager API, announced November 4, 2026.
  • Calls are identified by a new call_info start time and a SHA-256 hashed caller phone number.
  • Row-level diagnostics now show which records in a request had errors or warnings.
  • Duplicate call conversions are accepted and deduplicated, instead of rejected.
  • No deadline has been announced for moving call conversion uploads off the Google Ads API.

What are Data Manager API call conversions?

A call conversion tells Google Ads that an ad led to a phone call, and ideally whether that call turned into something valuable, such as a booked appointment or a quote. Many local businesses import these from a call tracking tool or CRM so Smart Bidding can optimise for qualified calls instead of every ring.

The Data Manager API is Google’s newer API for sending first-party data (offline conversions, audience lists and more) to Google Ads, Floodlight and Google Analytics. Call conversions were one of the pieces still only available through the Google Ads API. That gap is now closed.

What changed and when

Google announced the release on the Google Ads Developer Blog on November 4, 2026. It includes three changes:

  • Call conversions for Google Ads: a new call_info field records when the phone call started, and the caller is identified by a hashed phone number in user_data.
  • Row-level diagnostics: each error and warning count now includes record_indices, listing the position of the affected records in your request. Errors mean the record failed and should be fixed and resent. Warnings mean it was accepted but some data was ignored.
  • Lead IDs: a new lead_id field carries the ID Google issues when someone submits a lead form. Google says attribution using this ID isn’t available yet, so keep sending other identifiers.

How it differs from the Google Ads API

  • Phone numbers: Data Manager uses SHA-256 hashed numbers. The Google Ads API used an unhashed caller ID.
  • Duplicates: Data Manager accepts them and Google Ads deduplicates later. The Google Ads API rejected them with an error.
  • Access: Data Manager doesn’t use developer tokens, and it needs credentials with a different scope.
  • Consent: you can set default consent once for a whole request, rather than on each conversion.

How to set it up

  1. Find out how call conversions reach your account today. In Google Ads, go to Goals > Conversions and check which call conversion actions are imports, and from which tool.
  2. Enable the Data Manager API in your Google Cloud project and create credentials with the Data Manager scope, following Google’s setup guide.
  3. Map your fields. Google’s upgrade guide maps each Google Ads API call conversion field to its Data Manager equivalent. Hash phone numbers with SHA-256 before sending.
  4. Send a small test batch and read the diagnostics. Use record_indices to fix and resend any failed rows.
  5. Verify in Google Ads. Check that the call conversion action is recording conversions as expected before switching fully.

If you use a call tracking platform’s built-in Google Ads integration, you usually don’t build this yourself. Ask the vendor which API they use and whether they plan to move.

What it means for local service businesses

For dentists, home service companies, lawyers and salons, phone calls are often the highest-value lead. Feeding only qualified calls (for example, calls over a minute that booked an appointment) back to Google Ads is one of the best ways to improve lead quality from Smart Bidding and Performance Max.

  • Dental practices: import “new patient booked” calls rather than all calls. See Google Ads for dentists.
  • Painters and home services: send calls that became estimates or jobs so bidding favours real buyers. See Google Ads for painting contractors.
  • Agencies: the row-level diagnostics make it much easier to debug uploads across many client accounts.

PPCTAG’s take

For most small businesses, this is a behind-the-scenes change, not something to act on this week. For agencies and in-house teams with custom uploads, it’s worth planning:

  • Don’t migrate without a reason. No deadline has been announced, and Google notes lead ID attribution isn’t ready yet. Plan the move, test it, then switch.
  • Use the diagnostics either way. Silent upload failures are a common reason call conversions look low in Google Ads.
  • Keep conversions meaningful. The API is just plumbing. What you send (qualified calls, booked jobs) matters more than how.
  • For reporting, see our guide to building a Google Ads and call tracking dashboard.

FAQs

What is the Data Manager API?

It is Google’s API for sending first-party data, such as offline conversions and audience lists, to Google products including Google Ads, Floodlight and Google Analytics. It is separate from the Google Ads API and doesn’t need a developer token.

Do I have to move call conversion uploads off the Google Ads API now?

Google’s announcement doesn’t give a deadline for call conversions. Google has published an upgrade guide, so it’s worth planning the move, especially if you already use the Data Manager API for other offline conversions.

Does the Data Manager API need the caller’s phone number in plain text?

No. It uses the caller’s phone number hashed with SHA-256 in the user data. The Google Ads API call conversion upload used an unhashed caller ID.

What happens if I upload the same call conversion twice?

The Data Manager API accepts duplicates without an error, and Google Ads removes duplicates after processing. The Google Ads API rejected them with a CALL_CONVERSION_ALREADY_EXISTS error.

I use a call tracking tool. Do I need to do anything?

If your call tracking tool or CRM uploads call outcomes to Google Ads, ask the vendor whether it uses the Google Ads API or the Data Manager API, and whether it plans to switch. Check that qualified calls still appear as conversions after any change.

Not sure your call conversions are feeding Google Ads correctly? We’ll audit your tracking and conversion setup.

Get Your Audit Report

About the author

Mohit Bannatwala is a Google Ads & Local Services Ads specialist. For 8+ years he has managed Google Ads, Performance Max and LSA campaigns for agencies and local service businesses, including dental practices, salons and home service companies. He shares lessons from real accounts on the PPCTAG blog.

Sources

Leave a Comment