folder_open Analytics & Attribution

Data Manager API now takes call conversions (Nov 2026)

Martin Marinov Martin Marinov
11 min read
Topics google-adscall-trackingoffline-conversionsdata-manager-apiuk-trades

As of 4 November 2026, Google’s Data Manager API accepts Google Ads call conversions. That means a business can now tell Google which phone calls from its ads turned into real, paid work, using a direct connection instead of manual file uploads. If you run a UK trade business, this matters, because the phone is still how most of your customers book.

The problem it solves is simple. Most firms let Google count any call over a set length as a “conversion”. Google then bids harder for more calls like that, including the wrong-number calls, the “do you cover Leeds?” calls and the price shoppers who never book. A proper google ads call conversion import tells Google which calls became booked jobs, so it can chase more of those.

Below we cover what changed, what you need from your call log or CRM, and the exact steps to start sending booked-job outcomes back to Google Ads.

What Google changed in the Data Manager API

According to Google’s announcement of call conversion support in the Data Manager API, the update has three parts that matter to a trade business:

  • Call conversions. You can now send Google Ads call conversions through the Data Manager API. Each record uses a new field called call_info. It holds the time the call started and a hashed version of the caller’s phone number.
  • Row-level diagnostics. When you upload a batch of conversions, Google now shows which individual records failed or triggered warnings.
  • A lead_id field for lead form conversions. This was added for leads that come through Google’s lead forms. However, Google says attribution using lead_id and match_id is not available yet. Do not build anything that depends on it today.

“Hashed” means the phone number is converted into a fixed code before it leaves your system, so Google can compare it with its own records of who called. A hashed number can often be matched back to the original, so it is still personal data and needs the same care as the raw number.

Google Ads has accepted offline call conversion imports through file uploads and its own API for some time. What is new is that the Data Manager API, Google’s newer route for sending your first-party data, now handles calls too. For many firms that makes an automated connection from a CRM or call tracking system easier to set up and maintain.

Why bidding on “any call” quietly wastes your budget

Say a homeowner in Bristol searches for a boiler engineer on a Saturday, clicks your ad and rings you. The call lasts three minutes. Google records a conversion. On Monday, someone else clicks the same ad, rings to ask if you fit a brand of boiler you do not work with, and also stays on the line for a few minutes. Another conversion.

To Google, those two calls look identical. Only one became a paid job. If your account uses Smart Bidding, such as Maximize conversions or a target cost per acquisition, Google learns from both equally. Over time it can drift toward searches, times of day and areas that produce lots of calls but few bookings.

This is where phone lead tracking in Google Ads usually stops for trade firms. The call is counted, and nothing comes back afterward. Your office knows which calls turned into quotes and which quotes turned into work. Google does not.

Feeding offline call conversions back closes that gap. Instead of “a call happened”, Google hears “this call became a booked job”, and ideally “this job was worth this much”.

What a google ads call conversion import needs from your call log

Before anyone touches the API, check that the right information exists on your side. For each call you want to report, you need:

The call start time

Google matches your record against the call it logged. Your system must store when the call began, with the date, time and time zone. Watch the clocks changing in spring and fall. A call log that stores local time without a time zone can drift by an hour around those dates.

The caller’s phone number

This is the number the customer rang from, not your tracking number. Many UK CRMs store the same mobile in different ways, for example starting with 07 in one place and with +44 in another. Once hashed, those versions will not match each other. Your developer should follow Google’s formatting and hashing instructions exactly, and clean up numbers before they are hashed.

A clear outcome

Decide what counts. For most trades we suggest at least two stages: “quote booked” or “survey booked”, and “job won”. If you can, attach a job value to the won stage so Google can learn which calls bring bigger work, not just more work.

A record of the call on Google’s side

Google can only match a call it knows about. Make sure call reporting is switched on in your account, so calls from your ads and call assets are logged. If customers ring a number Google never saw, there is nothing to match your upload against.

Hashing does not make data anonymous. A hashed phone number is still personal data under UK GDPR, so every duty applies in full. You need a lawful basis for sharing customer data with advertising platforms, and your privacy notice should say that you do it.

Google’s own rules add another layer. Its EU user consent policy also covers users in the UK, and it requires consent when their personal data is used for ads measurement. That means you must collect and record appropriate consent from customers. Each Data Manager API upload also carries consent signals for ad user data and ad personalization. Your developer should set these from your own consent records for each customer, never default them to “granted”. If you are unsure, check with whoever handles your data protection before you switch anything on.

How to send booked-job outcomes back to Google Ads

Here is the order we follow when we set this up for trade clients. Your web person or developer can work through it with you.

Steps

  1. Audit your current call conversions. In Google Ads, list every conversion action that counts calls. Note which ones are set as primary, meaning they drive bidding, and the minimum call length on each.
  2. Create a new conversion action for imported call outcomes. Name it clearly, for example "Phone - job booked". Set it to accept imported call conversions and decide whether it carries a value.
  3. Map your call log or CRM fields. Match call start time, caller phone number, outcome stage, job value and each customer's recorded consent to what the Data Manager API expects, including the new call_info field and the consent signals.
  4. Normalize and hash phone numbers. Clean every number into one consistent format first, then hash it following Google's instructions. Test with a handful of known calls.
  5. Connect your CRM or call system to the Data Manager API. Some systems can do this through an existing integration. Others need a small script that runs on a schedule, for example once a day.
  6. Send a test batch and read the diagnostics. Use the new row-level results to fix any failed records before you send history in bulk.
  7. Run the new action as secondary first. Let it collect data alongside your existing call conversion so you can compare them without changing how Google bids.
  8. Switch bidding to the booked-job signal. Once the new action is reporting reliably, make it primary and set the old "any call" action to secondary.
  9. Set an upload rhythm and an owner. Somebody in the office must mark outcomes in the CRM promptly.

If you want help with any of these steps, our offline conversion tracking setup for CRMs and call logs covers the full connection from call to booked job.

Budget planning changes too once you bid on booked jobs rather than raw calls. Our free Google Ads budget calculator is a quick way to sense-check spend against the number of jobs you actually want each month.

Reading the new row-level upload diagnostics

Most owners will overlook the diagnostics, but they may save you the most time.

Before, a batch upload could partly fail and you would see a vague error or a lower count than expected. Now Google shows which records failed and which triggered warnings. That turns “something is wrong” into “these specific calls did not go through”.

Common reasons a row fails or warns in a trade setup:

  • Phone number format. The number was not cleaned before hashing, so it cannot match.
  • Call time mismatch. The start time is off, often because of a time zone or a clock change.
  • No matching call on Google’s side. The customer rang a number Google never logged, such as the one on your van or your Google Business Profile, rather than a number from your ads.
  • Duplicates. The same booking was sent twice, often because the CRM fires on every edit to the job.

Ask your developer to save these results and flag repeat problems to you weekly. If the same kind of error shows up every week, the fix is usually in how your office records calls, not in Google Ads.

It also helps to look beyond the upload. If you want to see how ad clicks, calls and CRM records join up across your whole funnel, our page on ads-to-CRM attribution explains how we connect them.

Frequently asked questions

Do I need a developer to use the Data Manager API for call conversions? Usually yes, or at least someone comfortable with APIs. Some CRMs and call tracking tools may offer a built-in connection. If yours does not, a developer can write a small scheduled script. Your ongoing job is making sure your team marks booked jobs in the CRM.

Will this track calls to the number on my van or my website? Only if Google logged the call in the first place. The match relies on Google having its own record of the call, which normally means calls from your ads and call assets with call reporting turned on. Calls to a number Google never saw cannot be matched, even if the customer first found you through an ad.

Should I stop counting all calls as conversions straight away? No. Keep your existing call conversion running while the new imported action collects data as a secondary goal. Once you trust the booked-job numbers, make that the primary goal and demote the “any call” action to secondary. Switching too early can unsettle Smart Bidding.

Can I use the new lead_id field for my Google lead form inquiries now? The field exists, but Google says attribution using lead_id and match_id is not available yet. You can plan for it, but do not expect lead form conversions to attribute through it until Google confirms it works.

Is sending hashed caller numbers to Google allowed under UK GDPR? It can be, but only if you meet all of your UK GDPR duties. A hashed number is still personal data, so you need a lawful basis, a privacy notice that explains the sharing, recorded consent that meets Google’s EU user consent policy, and matching consent signals on every upload. Check with your data protection lead or advisor before going live.

What if most of my calls come through a call answering service? That can still work, as long as the service passes on the caller’s number and the call start time, and someone records the outcome. Ask your provider whether their logs include both, and agree how bookings get marked back in your CRM.

Your next step

This week, pull your last month of call records from your CRM or call tracking system and check two things: does every call have a start time with a time zone, and is every caller number stored in one consistent format? If either answer is no, fix that first, because no upload will match without it. When you are ready to connect booked jobs back to Google Ads, Chat with us on WhatsApp and we will walk through your setup with you.