"The phone is ringing with inquiries, but Google Ads shows no call conversions." For businesses where the phone is the main result, this mismatch is serious. When calls that actually ring don't show up in the numbers, you can't tell which ad is generating calls — and your bidding and budget allocation fall back to guesswork.
Does any of this sound familiar?
- Phone inquiries are coming in, but conversions are still at zero
- The phone number on your site still shows the original number to visitors
- Only short calls aren't tracked, or nothing is counted at all
- Your CRM has the call logs, but nothing appears in the ad conversion column
The biggest reason call conversions don't track is treating "phone tracking" as a single mechanism. In reality there are several kinds, and each breaks in a different place. Start by sorting out which kind you're trying to measure.
First, get oriented: there are three kinds of call conversion
| Kind | What it measures | How it works |
|---|---|---|
| (a) Calls from ads | Calls to the number shown in the ad | Call assets / call-only ads. Google counts these automatically |
| (b) Calls to a number on your site | Calls to the number on your site | A Google forwarding number swaps in for the displayed number, and calls exceeding a length threshold are counted |
| (c) tel: link clicks | A number tap (intent to call) | The tel: link click is measured as a GA4 event |
The key point: (a), (b), and (c) are completely different wiring. (a) is the number shown in the ad, (b) is a script plus a forwarding number injected into your site, and (c) is a GA4 click event. Which one you use changes where you need to look. Below, we go kind by kind through the spots that trip people up.
Check 1: (b) Is the site's number swapping to a "forwarding number"?
In the (b) approach, once you place the Google Ads call conversion script (the snippet that swaps the displayed number) on your site, the phone number shown gets replaced with a Google forwarding number — but only for visitors who arrived via an ad. Only when this swap happens can calls to that number be counted as an ad conversion.
- If the script isn't on that page, the number stays original. No swap, no tracking
- If the number is shown as an image, or doesn't match the format the script expects (a text phone number), the script can't find what to swap
How to check: open your site from the ad's link and look at the phone number — is it still the original, or has it changed to an unfamiliar forwarding number? If it changed, the swap is working. If not, suspect a missing script, the number's format, or the blocking described later.
Common pitfall: "it swaps on the homepage but stays original on the other page where the number is listed" is a classic miss. Confirm the script takes effect on every page where you actually display the number.
Check 2: (b) Is the call passing the length "threshold"?
Not every call to the forwarding number becomes a conversion. Google Ads call conversions have a call-length threshold — "only count calls connected for at least N seconds." Short calls below the threshold aren't counted, even though the phone rang.
- If your operation is mostly short calls — voicemail, quick hang-ups, a first-touch callback — results can stall because they fall short of the threshold
- Conversely, an extremely short threshold picks up wrong numbers and silent calls, mixing in low-quality conversions
How to check: in the Google Ads call report, look for calls that were received but not counted as a "conversion." If short calls are being dropped at the threshold, review whether the threshold matches the actual length of your calls.
Common pitfall: when "the phone rings but conversions don't grow," you can have a two-stage cause — the number swap (Check 1) works, yet calls are dropped by the length threshold. Don't relax after checking only one.
Check 3: (c) Is the tel: click captured as a GA4 event?
For the common mobile pattern of "tap the number to call," you measure the (c) tel: link click as a GA4 event. This is separate from the (b) forwarding number, and it only measures the intent to call (the tap) — not whether the call actually connected.
- If the
tel:link has no click-event measurement attached, GA4 receives nothing even when it's tapped - Even when the event reaches GA4, it won't appear in the ad conversion column unless you register it as a "key event (conversion)" and import it into Google Ads
How to check: tap (click) the page's tel: link and, in DevTools or GA4 realtime, see whether the intended click event fires. If it arrives, next confirm the key-event registration and import to ads are in place on the GA4 side.
Common pitfall: when "the tel: click event shows in GA4 but not in ad conversions," a missing key-event registration or import is the prime suspect. Capturing the event and counting it in ads are two different stages.
Check 4: Call-only ads are deprecated — have you migrated?
As of February 2026, Google removed the ability to create new call-only ads. Existing call-only ads will stop serving in February 2027. The replacement is responsive search ads (RSAs) with call assets (formerly call extensions).
If you're still running call-only ads, this is relevant to your conversion tracking because:
- Call assets on RSAs track conversions the same way — Google forwarding numbers still apply
- RSAs give users both click-to-call and click-to-site options, which can change how calls are attributed
- Advertisers who migrated early report an average of 7% more conversions at similar cost, because RSAs can test more combinations and match more search queries
Action required: Check whether any of your campaigns still use the call-only ad format. If so, migrate to RSAs with call assets before February 2027 — and re-verify that call conversion tracking works on the new format, since the forwarding number behavior and conversion attribution may differ.
Check 5: Are you missing CRM / offline calls?
Phone results don't always complete on the site. If you manage calls in a CRM or logbook after answering, you need wiring to bring those calls and deals back to ad conversions (offline conversion import). The key to closing the loop is the click ID (gclid), which ties each call back to the ad that drove it.
- Even if calls are captured, when the CRM import is stopped or never set up, the ad side sees "no results"
- Operational gaps also cause this — the person answering doesn't log the call, or the record's key (click ID or phone number) isn't tied back to ads
Common pitfall: when "it feels like tons of calls are coming in on the floor, but the dashboard is quiet," it's often not a tag problem but an operational break — a missing CRM import.
Check 6: AI-qualified call leads — are you using call quality filtering?
Google introduced AI-qualified call leads in 2026, a feature that uses AI to evaluate call recordings and filter out non-qualified interactions — robocalls, spam, misdials, and hangups under 15 seconds — that previously met the call-duration threshold and were counted as conversions.
How it works:
- Google records calls from Google Ads forwarding numbers (recording is on by default for most advertisers)
- The recording is transcribed and run through an AI classifier
- Only calls classified as "qualified leads" are counted as conversions
- Call Details reports now include AI-generated summaries and intent tags (e.g.,
#HighIntent,#ConsultationScheduled)
Why it matters for conversion tracking:
- If you've noticed your call conversion counts drop after enabling this feature, it's working as intended — the removed conversions were likely spam or misdials
- Higher-quality conversion data improves Smart Bidding, because the algorithm optimizes for genuine leads instead of any call that lasted N seconds
- The feature is currently US and Canada only, and excluded for healthcare and financial services (due to call recording regulations)
How to check: In Google Ads → Goals → Conversions, look for the AI-qualified call conversion action. If it's available for your account, compare the qualified count against the raw call count to see how much noise was being included.
Third-party call tracking: when Google forwarding numbers aren't enough
Google's built-in forwarding number works for basic call tracking, but has limitations. Third-party call tracking platforms (CallRail, WhatConverts, Invoca, etc.) offer capabilities that Google's native tracking doesn't:
| Capability | Google forwarding number | Third-party call tracking |
|---|---|---|
| Call source attribution | Ad click → call | Ad click, organic, direct, referral → call |
| Call recording and transcription | Available (with AI-qualified leads) | Standard feature |
| AI lead scoring | AI-qualified leads (US/CA only) | Platform-dependent (CallRail CallScore, etc.) |
| Multi-channel attribution | Google Ads only | Cross-platform (Google, Meta, Bing, organic) |
| Dynamic number insertion (DNI) | Swaps for ad visitors only | Swaps for all traffic sources |
| CRM integration | Manual offline import | Native integrations with major CRMs |
When to consider third-party tracking:
- You need to track calls from all traffic sources, not just Google Ads
- You want automated CRM integration instead of manual offline conversion imports
- You need call tracking for multiple ad platforms (Google, Meta, Microsoft)
- You operate in a market where Google forwarding numbers aren't available (availability varies by country)
Integration note: Third-party platforms can feed call conversion data back into Google Ads via offline conversion import, so you don't lose bidding optimization. The setup is more complex, but the attribution picture is more complete.
Quick-reference by kind
A table that points you to the kind and check to suspect first, from the symptom.
| Symptom | Suspect first |
|---|---|
| The site's number stays original for visitors | Check 1 ((b) forwarding-number script placement / number format) |
| The phone rings but conversions don't grow | Check 2 ((b) call-length threshold) |
| Want to measure a mobile number tap / it's not showing | Check 3 ((c) tel: click GA4 event) |
| Still running call-only ads | Check 4 (deprecated format — migrate to RSA + call assets) |
| Shows in GA4 but not in ads | Check 3 & 5 (key-event registration / import) |
| Busy on the floor, quiet in the dashboard | Check 5 (CRM / offline gaps) |
| Conversion count includes spam / misdials | Check 6 (AI-qualified call leads) |
| Need to track calls from non-Google sources | Third-party call tracking |
If your problem isn't specific to calls but "conversions are stuck at zero" in general, see No Conversions in Google Ads? A Step-by-Step Diagnostic Guide for cross-kind isolation, and The Conversion Tracking Setup Guide for the overall map of settings. If the tag fires but the conversion still doesn't show up, Why Your Conversion Tag Fires but Isn't Recorded covers the full list of acceptance-stage causes.
What checking on your own machine can't tell you
Checks 1–6 are all useful, but verifying once on your own machine has two limits specific to call conversions.
- Your environment isn't your visitors' environment. The number swap (Check 1) depends on whether the visit came via an ad, whether the script is blocked, and the state of the device and browser. It can swap on your device yet stay original under real visitor conditions.
- Paths involving an ad click are hard to verify. To properly see whether (a) or (b) "really tracks via an ad," you'd need to click a live ad to recreate the path — which carries the risk of an ad-policy violation as a self-click.
Judging "I tapped it and it dialed, so it's fine" tends to miss the problem of the number swap or event send going missing on the real path your visitors take.
Frequently asked questions
Q. The phone number on my site still shows the original number to visitors. A. In the (b) forwarding-number approach, the script swaps the displayed number. If it doesn't swap, common causes are: ① the script isn't on that page, ② the number is written as an image or in a format the script doesn't expect, or ③ a browser extension is blocking the script (Check 1).
Q. The phone rings but conversions don't increase. A. Even if the number swap works, short calls below the call-length threshold may not be counted (Check 2). In the call report, check the length of calls that were received but didn't become conversions.
Q. How do I measure a number tap (tel:) on mobile?
A. Capture the tel: link click as a GA4 event, register that event as a key event (conversion), and import it into ads (Check 3). This measures the intent to call (the tap); it doesn't tell you whether the call connected.
Q. GA4 shows the phone event but Google Ads doesn't. A. Confirm the GA4 event is registered as a "key event (conversion)" and imported into ads (Check 3 & 4). Capturing the event and counting it in the ad conversion column are two different stages.
Q. I manage calls in a CRM after answering. Can that be tracked? A. Yes, but it needs offline conversion import wiring from the CRM (Check 4). If the setup that ties calls and deals back to ads by a key — such as a click ID or phone number — is stopped, the ad side can't see the results.
Conclusion: identify the kind, then verify on the real path
When call conversions aren't tracking, the starting point is to identify which you're trying to measure: (a) calls from ads, (b) calls to a number on your site, or (c) tel: clicks. From there, isolate the spot each kind gets stuck: for (b), the number swap (Check 1) and the call-length threshold (Check 2); for (c), the GA4 click event (Check 3); format-wise, the call-only ads deprecation (Check 4); operationally, the CRM import (Check 5); and for quality, AI-qualified call leads (Check 6). For step-by-step verification, pair this with The Conversion Tracking Verification Checklist. If you're using enhanced conversions to improve match rates for call leads, see How to Verify Enhanced Conversions.
But checks on your own machine have limits. Going further — confirming that, in production, the number swaps and the signal is sent on the real path your visitors take — is what "it's tracking" truly means.
ConversionOK runs your live page in an independent, isolated browser and intercepts the call conversion signals actually sent (the forwarding-number swap and the tel: click event), then verifies them — with no need to click your own ad and no interference from your office environment. Start with a free static check to confirm the entry point of your call measurement.