Most of My Customers Phone Me: How Do I Track Calls From Google Ads?

Your phone rings all week, yet Google Ads reports a few form fills. Most of your customers call, so your bidding is learning from the minority who never do. A click-to-call tag looks like the fix, but it counts taps, not conversations.
To track phone calls from Google Ads, start with Google's free forwarding numbers. Set the minimum call length from your own call data, not a borrowed figure, and add dynamic number insertion only when you need calls from the rest of your website. Once the phone is where sales are decided, stop counting minutes and import outcomes instead.
How do you set up Google Ads call tracking?
The native setup is free and takes about a dozen clicks. First, turn on call reporting in your account settings. This lets Google swap your number for a Google forwarding number. Next, create a phone call conversion under Goals → Summary and choose calls from ads, calls from website visits or calls via uploads. Finally, set a minimum call length and make the action a primary goal so bidding actually uses it. The full walkthrough, including the tag install for website calls, is in how to set up call conversions in Google Ads.
There are a few prerequisites. You need at least one call asset or location asset with a verified number, and a business in a country where forwarding numbers are available. If the setup screen behaves strangely, one of those is usually missing.
Measured calls, estimated calls and taps
"Call tracking" covers three different kinds of measurement, and the difference decides whether your data is safe to bid on. Google's documentation on phone call conversion tracking lists five ways to count phone call conversions. They fall into these groups:
- Measured calls. Calls from ads and calls to the number on your website both run through forwarding numbers. Google knows a call connected and how long it lasted. It counts the call only if it reaches the minimum length you set.
- Estimated calls. Clicks on call ads and call assets count based on Google's estimate of whether a meaningful call followed the click. No forwarding number is involved, and Google doesn't explain how the estimate is produced.
- Taps. When someone taps your number on your mobile site, Google states that it can only track the click, not the phone call itself.
- Imported calls. You track calls in a CRM or call tracking system and send back only the ones that mattered, with sale values attached.
Only the forwarding-number methods and imports record an actual call. If call reporting is off, what looks like call data is Google's inference that a call probably happened.
Taps deserve the most caution. They are cheap to collect and easy to mistake for leads. Keep them as a secondary action if you want them in your reports, but don't let them drive bids.
Three settings that quietly break it
The default action. Once call reporting is on, Google may already be counting calls under a default "Calls from ads" action in your Conversions column. Check what it counts before you build a second action next to it, or you'll count the same calls twice.
Primary versus secondary. Secondary actions show up in reporting but don't feed automated bidding. If Smart Bidding seems to ignore calls you can plainly see in your reports, this setting is the usual reason.
Count. "Every" counts each call. "One" counts at most one conversion per ad click. For most lead-generation businesses "One" is the honest choice, because a prospect who calls back three times about the same quote is one lead.
Then verify before you trust the numbers. The call action's status should read "Recording conversions." For the first week, compare the Call details report against your own phone system's log. A large gap usually means one of two things. Either the number on your site doesn't match the one you entered character for character, or the tag isn't firing on a page where the number appears.
How do you track calls from your website too?
Google's website call tracking has a limit built into its design. The forwarding number appears only to visitors who arrived by clicking one of your ads. Everyone else sees your normal number and calls it untracked. That includes the person who searched your brand, read a service page from organic results, or came back three days later by typing your URL.
To see those calls, you need dynamic number insertion (DNI) from a call tracking provider. You rent a pool of numbers, and a script on your site works out how each visitor arrived. It then swaps the visible number, including click-to-call links, for one tied to that source. Every number forwards to your real line, so callers notice nothing. The mechanics and trade-offs are covered in how to track calls from your website, not just your ads.
When is Google's free version enough?
If your question is which keywords, ads and campaigns make the phone ring, Google's own tool answers it at no cost. Use it whether or not you add anything else. It has two practical constraints. The snippet must sit on every page where your number appears. And by default, Google's website call setup tracks only one number per page, so a multi-location site needs a manual install.
DNI earns its cost when the question changes. You might want to know whether SEO produces calls, or which service page persuades people to pick up the phone. DNI comes in several levels of detail:
- Source-level assigns one number per channel: organic, paid, direct and referral.
- Session-level gives each browsing session its own number. This is where landing-page and keyword data comes from.
- Visitor-level follows one person across several visits.
- Campaign-level gives a fixed number to a single campaign, often an offline one such as a flyer.
For call tracking for small business, source-level usually answers the real question cheaply. Session-level and visitor-level tracking need a larger number pool. Size it to your peak number of visitors on the site at the same time, not your daily total. If the pool is too small, numbers get reused mid-session and calls are credited to the wrong source.
Where the setup advice conflicts
The two halves of this cluster pull in different directions on one point, and it's worth resolving before you install anything.
The native setup is often done through Google Tag Manager, using the Calls from Website Conversion tag. Google, however, advises against deploying its phone snippet through Tag Manager on sites that also run DNI or third-party call tracking. Both pieces of advice hold, depending on your site. If Google's swap is the only one on the page, Tag Manager is fine. If a DNI script is also rewriting numbers, install Google's tag manually. Then test that neither script overwrites the other.
Click-to-call events in GA4 are the other common shortcut. You set a Tag Manager trigger on any link starting with `tel:`. That tells you which pages prompt people to tap your number. It misses the desktop visitor who types your number into their phone, and it can't say whether the call connected. Treat it as a hint about page behavior while you decide on a provider, not as a count of calls.
Two last guardrails apply to DNI:
- Keep your real number everywhere off-site. Your Google Business Profile and directory citations should all show your primary number. Local search depends on consistent name, address and phone details, and tracking numbers should exist only in the visitor's browser on your own pages.
- Treat tracked calls as a floor. DNI misses anyone who saved your number on an earlier visit or found it in a directory. Your tracked total will always be lower than your real one.
How long should a call last to count?
Google doesn't recommend a duration. You choose the minimum, and every call lasting at least that long counts as a conversion. The right threshold is the shortest call in which your team can genuinely qualify a caller, and you read it from your own data, not from a forum or a pre-filled field. The reasoning, and a method for finding your number, are in how long a call should last to count as a lead.
Why the threshold matters more than it looks
Duration is a stand-in for what you actually want to count, which is a qualified conversation. How long qualification takes depends on what you sell. An emergency plumber's dispatcher can qualify a caller in moments. A firm selling a complex B2B service needs a proper discovery call. One threshold applied to both would undercount the first business and overcount the second.
The businesses with the most at stake don't agree on a figure either. In pay-per-call, a qualified call is the thing a buyer pays for, yet each campaign defines its own payable event. Duration usually sits alongside intent screening, geography and staffed hours. If people who pay by the call can't settle on a number, no general rule will hold for your account.
What the threshold does decide is which way your errors run:
- Too low. Misdials and instant hang-ups count as leads, and conversion-based bidding goes looking for more auctions that produce them. Your cost per conversion looks healthy while your pipeline stays flat.
- Too high. Genuine short calls disappear, such as a returning customer booking a slot. Your bidding gets less signal, and your reports understate what Google Ads contributes.
Of the two, counting too much is usually the more expensive mistake. The bidding doesn't just record the noise. It actively optimizes toward it.
Finding the break in your own calls
- Pull call durations from the Call details report in the Report Editor.
- Mark a recent stretch of calls against what each one became: booked, quoted, existing customer, spam or wrong number.
- Sort the calls by length. Most accounts show a band of short calls that are almost all noise, then a point where real enquiries start to dominate.
- Set the threshold just above that noise band, not at the length of a typical good call. A threshold at the typical good call throws away every genuine call shorter than it.
Recheck whenever your call handling changes. A new recorded greeting or phone menu adds seconds to every call without making any of them more qualified. If good calls and junk calls overlap heavily in length, that tells you something too: duration is a weak proxy for your business, and further tuning won't fix it.
When to stop counting minutes
Duration measures how long someone stayed on the line, not whether they became a customer. If the phone is where your sale happens, that gap matters more than any threshold you set.
The import method closes the gap. You send back only the calls that produced a sale, with the value attached, and bidding can then optimize toward revenue rather than airtime. Imported call conversions still rely on Google forwarding numbers, so the country limits from the setup stage still apply. The cost is operational. Your CRM has to record calls reliably and match them back to Google Ads.
Keep a duration-based action counting while the import beds in. Once outcomes flow reliably, make the imported action primary. To judge whether your old threshold ever tracked real leads, you have to put ad data and CRM data side by side. SproutMe Companion answers that kind of question from Google Ads and HubSpot data held in one place, so the comparison doesn't depend on a spreadsheet rebuilt every month.
Conclusion
Tracking calls from Google Ads is less a setup problem than a definition problem. Turning on forwarding numbers is the easy part. The decisions that matter are what counts, and how much of your traffic you can see. So, in order:
- Measure real calls rather than taps or estimates.
- Set the minimum length from your own call data.
- Extend coverage with DNI only when the question moves beyond your ads.
- Once the phone is where revenue is decided, move from duration to imported outcomes.
Each step makes the signal your bidding learns from a little closer to what actually pays the bills.
See how SproutMe Execute adjusts bids and budgets continuously from the call conversions you define, within spend limits a human sets.
Frequently Asked Questions
They can, but only when three conditions are met. Your Google Ads account must be linked to your Google Business Profile, call history must be turned on in the profile, and call reporting must be enabled in Google Ads. Calls that meet all three are reported under "Calls from ads." If any one is missing, those calls won't appear in your conversion data.
No. Google recommends it but doesn't require it. With recording on, Google can analyze recordings to identify high-quality leads. As of Google's 2026 documentation, that only applies when both parties are in the US or Canada. Without recording, Google counts calls longer than your minimum duration, so the threshold you set does all the qualifying work.
Yes, with care. Install Google's phone snippet manually, not through Tag Manager, because Google advises against Tag Manager on sites running DNI. Google can't scan a DNI site to verify your number, so verify domain ownership by linking Google Search Console to Google Ads. That link takes about 24 hours, and call assets then need resubmitting to avoid disapprovals.
Get a complimentary audit to uncover AI opportunities hidden in your data.
Put these strategies to work


