Call Extensions Won't Track as Conversions

TL;DR: Calls from call extensions and call-only ads never load a landing page, so CallRail's usual gclid snippet can't see them, and no CallRail setting changes that. The fix is Google's Call Details Forwarding, which sends call data to CallRail while Google itself tracks the conversion through a "Calls from ads" conversion action. Google's AI-Qualified Call Conversions can now judge call quality when recording is on, with minimum call duration as the fallback.

If real calls are coming in from a call extension or a call-only ad, and none of them are showing up as conversions in Google Ads even though CallRail is recording and logging them fine, the problem isn't a broken tag or a misconfigured integration. It's structural. Standard CallRail-to-Google-Ads conversion tracking depends on a landing page loading in a browser, and a call placed directly from an ad never loads one. There's nothing to fix on the CallRail side because CallRail's usual method was never going to see these calls in the first place.

I've walked more than one client through this exact confusion: real jobs booked, real calls answered, and a Google Ads account that looks like none of it happened. Here's the actual plumbing, and the pathway that does work.

Why CallRail's usual method can't catch these calls

CallRail's standard Google Ads conversion tracking works by capturing the Google click ID (gclid, and its newer variants wbraid/gbraid) with a JavaScript snippet installed on your website. When someone clicks your ad and lands on a page, that snippet grabs the click ID from the URL, matches it to the visitor's session, and later matches a call from that visitor back to it. Once the call happens, CallRail hands that gclid to Google Ads and the conversion posts. Per CallRail's own documentation, the snippet has to be installed on the page being tracked, that's the mechanism, full stop.

A call extension (Google now calls these call assets, more on the rename below) or a call-only ad skips that page entirely. Tapping the call button initiates the call directly, it doesn't route through your website first. Per Google's own documentation on call assets, "a click on call button will initiate a call directly to your business," regardless of whether a landing page URL is even attached to the ad. No page load means the JS snippet never fires, which means there's no gclid to capture, ever, for these calls, even for a completely genuine mobile tap from a real customer. This isn't a tracking gap that better configuration closes. It's a call that never touches the layer CallRail's method depends on.

Source: CallRail's own documentation on the Google Ads integration, and Google's own documentation on call assets.

The correct fix isn't on CallRail's side, it's a separate Google pathway

The raw assumption most people make (and I made this assumption myself the first time I ran into it) is that there must be some setting in CallRail that "turns on" call extension tracking. There isn't, because CallRail was never in a position to see these calls independently. The actual fix lives entirely inside Google's own systems: it's called Call Details Forwarding (CDF), and as of writing that's still its current name in Google's help center.

Here's what CDF actually does, per Google's own documentation:

Calls from call assets, call-only ads (while they still exist, more below), and location asset calls route through a Google forwarding number.
Google connects the call to your business and, in parallel, transmits attribution data, the campaign, ad group, and a click ID, in the SIP headers of the call itself.
If you've connected a supported third-party call tracking provider, that provider receives the call along with this attribution data in near real time (Google's documentation cites data landing roughly 15 seconds after the call connects), and only shares it with the provider you specifically connected.
CallRail is a listed supported provider. So are CallTrackingMetrics, Delacon, DialogTech, Infinity, Invoca, Jet Interactive, and Walmeric.

The critical detail, and this is the part worth sitting with: even when CallRail is connected via CDF, CallRail does not post the conversion to Google Ads. Per CallRail's own help article on this specific integration, Google tracks the conversion itself, according to whatever call conversion settings you've configured in Google Ads. CallRail's role in this pathway is receiving the call metadata for its own reporting and routing, keyword and campaign data, lead scoring, call routing rules, not deciding whether the call counts as a conversion. That decision sits entirely with Google's own "Calls from ads" conversion action, set up separately in Google Ads under Goals, not with anything CallRail does.

That's a genuinely different architecture from standard website call tracking, where CallRail is the one matching a gclid to a call and pushing the conversion. With CDF, Google owns the whole decision. CallRail is a downstream recipient of data, not the system deciding what counts.

Setting it up

To use CDF at all, you first need account-level call reporting turned on in Google Ads (this is also what powers Google's native call conversion tracking generally). From there:

Go to your Google Ads account settings and enable call reporting if it isn't already.
Under the call reporting settings, select your call tracking provider (CallRail, in most of the accounts I work on) and complete the authorization to enable CDF.
Separately, in Goals, create a "Calls from ads" conversion action if you don't already have one, this is where the actual conversion criteria live, covered below.
On CallRail's side, make sure the numbers receiving these calls are set as Google Ad Assets in your Number Insertion Options, per CallRail's setup documentation. You'll get click IDs and campaign IDs without a full CallRail-Google Ads account integration, but you need that integration active to also see keyword and campaign names, not just IDs.

What actually counts as a conversion here (and where the raw assumption needs correcting)

This is the part where I want to be precise, because the answer changed earlier in 2026 and the older assumption, that minimum call duration is the only lever available, is no longer accurate.

For years, "Calls from ads" conversion tracking worked on one signal: you set a minimum call duration in Google Ads, and any call that lasted at least that long counted as a conversion. That's still the fallback today. But Google published AI-Qualified Call Conversions in its help center in April 2026, and it changes the primary signal:

If call recording is turned on, Google's AI analyzes the recording itself to judge lead quality, looking for signals like a real service inquiry or a scheduled consultation, rather than just counting seconds. A long call from a robocall or a misdial can meet a duration threshold without being a real lead; this is Google's stated reason for adding the AI layer.
If call recording isn't available for a given call, the system falls back to your set minimum call duration, the older mechanic.
Call recording currently requires both the dialing and receiving numbers to be in the US or Canada, and per Google's documentation, call recording is now turned on by default for eligible accounts as of July 1, 2026, with exceptions carved out for healthcare and financial services categories.

So the honest, current answer is: minimum call duration is still in the system as a fallback, but it is not the only conversion criterion Google Ads offers for calls from ads anymore. There's no option to filter by caller area code or a specific number range that I could find documented anywhere in Google's help center, that part of the original assumption still holds. But "duration is the only lever" stopped being true once AI-qualified analysis rolled out as the primary signal wherever call recording is active.

One flag worth making explicit: rollout dates like "July 1, 2026" are exactly the kind of thing Google has delayed or adjusted before. If you're checking this for your own account, look at the actual call recording and conversion settings under Goals rather than assuming the timeline above still matches what you see.

Does this apply the same way to call extensions and call-only ads?

Mechanically, yes, tapping the call button on either format initiates a direct call the same way, no landing page in between. But there's a timing wrinkle worth flagging if call-only ads specifically are part of your account: Google has been phasing them out. Per Google's own documentation on the transition, creating new call ads was removed starting February 2026, and existing call-only ads are scheduled to stop serving entirely in February 2027. The replacement is responsive search ads with a call asset attached, which behaves the same way for this specific problem, tapping the call button still dials directly and still skips the landing page. If your account still has live call-only ads, that's worth migrating on its own timeline, separate from the tracking issue this post covers, but the underlying "no gclid ever" mechanic doesn't change either way.

The practical implication if you haven't set this up

If a meaningful share of your calls come through call assets or call-only ads and you haven't specifically enabled Call Details Forwarding, here's what's actually happening: CallRail is very likely tracking, recording, and logging those calls correctly on its own side. But Google Ads' bidding algorithm has no idea they exist. Smart Bidding optimizes toward whatever it can see as a conversion, and calls that skip the landing page entirely are invisible to it unless CDF (or Google's own native "Calls from ads" conversion action) is separately configured. You can have a CallRail dashboard full of real, qualified calls and a Google Ads conversions column that shows almost none of them, and both can be true at once without either platform being "wrong."

Worth distinguishing from Local Actions - Clicks to Call

If you've also seen a conversion goal called Local Actions - Clicks to Call in your account, that's a different mechanism entirely, not what this post covers. That one tracks taps on the "Call" button on your Google Business Profile listing on Maps or in local search results, and Google auto-generates it as a Google-hosted goal with no CallRail involvement at all. It also can't tell you whether the call connected or how long it lasted. Call extensions and call-only ads on Search ads are a separate surface, with the CallRail/CDF mechanics described above.

Frequently asked questions

Why doesn't CallRail's JavaScript snippet capture calls from my call extensions? Because that snippet only runs once a landing page loads in a browser, and calls placed directly from a call extension or call-only ad connect immediately without ever loading one. There's no gclid for CallRail's method to capture, structurally, not due to a misconfiguration.

What is Call Details Forwarding (CDF)? A separate Google Ads feature that routes calls from call assets, call-only ads, and location assets through a Google forwarding number, then transmits attribution data (campaign, ad group, click ID) directly to a connected third-party call tracking provider. CallRail is one of Google's listed supported providers.

If I set up CDF, does CallRail create the conversion in Google Ads? No. CallRail receives the call data for its own reporting and routing, but Google Ads tracks the conversion itself based on the call conversion settings configured directly in your account, not anything CallRail sends back.

Is minimum call duration the only way to define a call conversion in Google Ads? Not anymore. Since Google rolled out AI-Qualified Call Conversions in April 2026, calls with recording enabled are evaluated by Google's AI for lead quality first, and minimum duration is used as a fallback when recording isn't available. There's no documented option to filter by caller phone number or area code.

Does this same limitation apply to call-only ads, or just call extensions? Both, for the same reason, tapping the call button dials directly on either format. Worth noting separately that Google is retiring call-only ads, new ones stopped being creatable in February 2026 and existing ones are scheduled to stop serving in February 2027, with call assets on responsive search ads as the replacement.

If call extensions, call assets, or call-only ads are a real share of your call volume and you're not sure whether Call Details Forwarding is actually turned on in your account, that's a five-minute check worth getting right before you assume your bidding data is complete. CallRail integration and conversion tracking both cover this as part of making sure what Google Ads optimizes toward matches what's actually happening on your phones.