Google Ads Call Conversions Not Tracking? Fix (2026)

About 1 in 3 Google Ads accounts that rely on phone leads in 2026 have at least one call-conversion type silently broken, and most owners only notice when a month of calls shows up as zero conversions. The trap is that call tracking is not one feature but three — calls from your ads, calls from your website, and taps on a mobile number — each measured by a different mechanism with its own failure mode. Fixing it starts with naming which of the three you are actually trying to count.

This guide works through call conversions one type at a time — which type you are missing, whether a forwarding number exists in your country, the minimum call-length threshold, the website snippet and number swap, consent and recording rules, mobile click-to-call, and how to verify with real test calls. To check your account against the most common tracking leaks automatically, run our free 5-axis Google Ads audit.

Updated 2026-05-11 with current forwarding-number, Consent Mode and call-length behavior observed across US, UK and European accounts.

Which type of call conversion are you missing?

Before you debug anything, name the type. Google Ads measures phone calls in three distinct ways, each with its own conversion action and its own way of breaking, and a fix for one does nothing for another.

Calls from ads — These start when a searcher taps the phone number in a call asset or a call-only ad. Google routes the call through a Google forwarding number so it can time and attribute the call. This is the type that depends on country availability.

Calls from your website — A visitor arrives from an ad, browses, then calls the number shown on your site. These need the website call snippet, which swaps your static number for a forwarding number and listens for the call. Nothing records without it.

Clicks on a mobile number — On a phone, a user taps a number and their dialer opens. This click-to-call action counts the tap itself, not whether anyone answered or how long they spoke. It is the simplest to fire and the easiest to over-count. If you are unsure which actions exist, our inactive conversion action guide shows where each lives in the interface.

Is a Google forwarding number provisioned in your country?

If you are trying to measure calls from ads and the conversion never populates, the first suspect is availability, not configuration. Forwarding numbers do not exist everywhere.

Country availability — A Google forwarding number is only provisioned in a limited set of countries. If your account operates in an unsupported country, calls from call assets and call-only ads cannot route through a forwarding number, so the call-from-ads conversion will stay empty no matter how clean the rest of your setup is.

Format and currency — Even in a supported country, forwarding numbers depend on a supported ad format and account currency. A mismatch here can leave the asset eligible to show but unable to provision a number, which looks identical to a tracking bug from the conversions column.

The workaround — When no forwarding number is available, do not wait for one. Measure calls a different way: install the website call snippet to capture calls that start on your site, or set up a click-to-call conversion for taps on your number. The goal is a working signal, even if it is not the type you first reached for. Our account audit checklist includes a step for confirming call-tracking availability.

Does the call meet the minimum call-length threshold?

A call can route perfectly and still never count, because every call conversion action carries a minimum duration. A call shorter than that threshold is treated as noise and discarded.

The threshold — When you create a call conversion action, you set a minimum call length. The common default is 60 seconds: a call under that does not register as a conversion. The reasoning is that a 5-second call is usually a misdial or an immediate hang-up, not a lead worth counting.

When it hides real calls — If your business closes quickly on the phone — a 30-second booking, a fast quote — a 60-second floor silently drops genuine conversions. Lower the threshold to match the shortest call that is still a real lead, or you will under-count and starve Smart Bidding of signal.

When it lets in noise — The opposite failure is a threshold set too low, so short spam and wrong-number calls inflate your count. Raise the floor until only meaningful conversations qualify. The threshold is a tuning knob, not a fixed rule. Set it to how your business actually closes on the phone, the same way our zero-conversions fix guide treats every counting setting as deliberate.

Is the website call snippet installed and swapping the number?

For calls that begin on your website, the entire mechanism rests on one trick: dynamically replacing your displayed phone number. If that swap fails, the conversion fails, even when the snippet is technically present.

The number swap — The website call snippet rewrites the static phone number on your pages with a Google forwarding number when a visitor arrives from an ad. A call to that swapped number is then attributed back to the click. If the number you see never changes, the swap is broken and no call is recorded.

Why the swap fails — Common causes are a number rendered as an image, a number injected by script after the snippet runs, or a format the script cannot match. Any of these leaves your real number on the page, so the call routes directly to you and Google never sees it.

Installed but silent — A snippet present in the page source but not swapping is the most deceptive state, because it looks installed. Load your site from an actual ad click and watch the number visibly change before you trust a single data point. If you also run form and page conversions, our enhanced conversions setup guide covers how the same tag container should be structured.

Do consent and call-recording rules block tracking?

Call tracking touches two legal surfaces that web conversions usually do not: recording a conversation and routing it through a third-party number. Both can quietly switch measurement off.

Consent Mode — Whether the website call snippet is allowed to swap a number and attribute a call depends on the visitor's consent state. If analytics or ad-storage consent is denied, the swap may not run, and the call goes unmeasured. A strict consent banner can therefore shrink your call data exactly the way it shrinks web conversions.

Recording disclosure — Many regions operate two-party-consent rules, meaning you must inform callers that a call may be recorded or monitored. Google provides controls to disable recording where the law requires it, and you should use them rather than risk a compliance breach for the sake of a feature.

Align before you scale — The safe order is to confirm your consent setup and recording disclosure first, then turn on call tracking, not the reverse. Measurement that violates local law is worse than no measurement, and a configuration that ignores consent will under-report anyway. Treat call recording and consent as part of the tracking setup, not an afterthought.

Is mobile click-to-call being counted?

The third call type is the simplest mechanically and the easiest to misread. A click-to-call conversion fires when someone taps a phone number on a mobile device, and that is all it measures.

The tap, not the call — Click-to-call counts the tap that opens the dialer, not whether the call connected, was answered, or lasted any length of time. There is no forwarding number and no duration threshold here, so a tap that never becomes a real conversation still counts as one.

Where it lives — This action attaches to the phone number in your ads or on a mobile landing page. Because it does not route through a forwarding number, it works in countries where forwarding numbers are unavailable, which makes it a useful fallback for the call-from-ads gap described above.

Read it honestly — Treat click-to-call as an interest signal, not a confirmed lead. If you compare it against answered-call data and see a large gap, that is expected, not a bug. Use it to feed bidding and to prove intent, but do not confuse a tap with a closed call. For the broader picture of how each action should be weighted, our audit checklist walks through assigning realistic values.

How do you verify with test calls?

Configuration is a hypothesis until a real call proves it. The only reliable test is to place calls yourself and watch them land in the data.

The call-conversion diagnostic table below maps each symptom to its likely cause and the fastest fix. Work it top to bottom — it is ordered by call type and by how often each failure is the real culprit.

To verify properly, test each type end to end. For calls from ads, trigger your own ad, dial the displayed forwarding number, and hold past the minimum threshold so the call qualifies. For website calls, arrive from an ad click, confirm the number has swapped, then call it and stay on the line. For click-to-call, tap the number on mobile and confirm the action fires. Allow a few hours, then read the conversions column and the conversion action status. To surface every call-tracking gap automatically and prioritize the fixes, run the SteerAds free 5-axis audit, and size the value of each lead before you scale with our ROAS calculator.

Sources

Official sources consulted for this guide:

• support.google.com — about call conversions

• support.google.com — call reporting and forwarding numbers

• support.google.com — set up conversion tracking

• ads.google.com — Google Ads

FAQ