How to track phone call to sale for Google Ads
For a lot of businesses the phone is the conversion, and a website tag can see none of it. Getting this right needs two separate things: dynamic number insertion so the call carries a source at all, and a recorded outcome so a wrong number isn't worth the same as a booked job. Almost every implementation we open has the first and not the second. On Google Ads the specifics that matter are the click identifier (gclid, gbraid and wbraid), the import mechanism (Google's offline conversion import), and conversion actions deduplicate on their own counting setting rather than an event ID, so the setting matters more here than the payload. The chain only works end to end if the identifier is captured on landing and stored on the call record, joined to your job or CRM system — no cookie survives the gap between ad click and qualified calls sent back.
Free30 minutesNo obligation
Specific to Google Ads × Phone call → sale
Google Ads calls: import the sold job, keep raw calls secondary
On Google Ads, track phone call to sale by storing the gclid, gbraid or wbraid on the call record when the tracking number is served, then importing the sold job as an offline conversion with its job value from your CRM. Calls placed straight from a call asset have no gclid and need Google's own call reporting instead.
Google is the platform where the most calls never touch your website. A call asset or call-only ad lets the searcher dial from the results page, so no landing page loads, no tracking number is swapped and no gclid is stored. Those calls only exist inside Google's forwarding-number reporting. If a large share of your sold jobs start that way, check whether your account can import call conversions matched on caller ID and call start time, because your website capture will never see them.
For calls that do come through the site, the usual mistake is leaving the built-in 'Calls from ads' or website-call action as primary. It counts any call over a duration threshold, so bidding learns to buy the same short calls the spec warns about. Make the imported sale the primary action at real job value, demote the raw call action to secondary, and set counting to one per click so a customer who rings three times about the same job is still one sale.
Timing is usually comfortable. Most call-driven jobs close within days or a few weeks, well inside the 90-day import window, so the sold job can drive Maximize conversion value directly once you have a steady monthly volume. If sold jobs are too few for that, import qualified calls as a second action with a small value until volume builds.
Google Ads · Phone call → sale · what breaks
Where this funnel usually breaks — Google Ads · Phone call → sale
- 01
A hard-coded number insertion can't reach
A number in a header graphic, a footer or a sticky mobile bar can't be swapped, and those calls arrive with no source at all.
- 02
Every call counted equally
A thirty-second wrong number and a booked job teach bidding exactly the same thing.
- 03
Click-to-call firing no event
On mobile the customer taps the number. If the tel: link fires nothing, the highest-intent path is invisible.
Google Ads · Phone call → sale · the fix
What working looks like — Google Ads · Phone call → sale
Qualified calls sent back attributed to the click
Weeks later if necessary, because the identifier lives on the call record, joined to your job or CRM system rather than in a cookie.
Google Ads bidding fed the real outcome
Via offline conversion import, so it optimizes toward calls that turned into work rather than toward every ring.
A reconciliation that closes
Call records joined to a recorded sale outcome matched per record against what Google Ads reports, over a fully closed window.
Google Ads · Phone call → sale · architecture
The exact event sequence — Google Ads · Phone call → sale
Stage two is where most of the loss happens, and it's usually a phone number rendered inside an image.
- 1
Ad click
Identifier captured on landing, at the visit — not at the call, by which point the session context is gone.
- 2
Number swapped
Dynamic insertion across every template, including header images and the sticky mobile bar.
- 3
Call connected
The call platform records it against the session, which is how it carries a campaign.
- 4
Outcome recorded
Qualified, booked, sold. Duration is a proxy; the office's own disposition is the truth.
- 5
Qualified calls sent back
Only the ones that turned into work, so bidding stops buying wrong numbers.
Google Ads · Phone call → sale · diagnose
What's specific to Google Ads
- 01
Click identifier: gclid, gbraid and wbraid
Three parameters, not one. gclid is the long-standing identifier; gbraid and wbraid arrive on iOS traffic where privacy constraints prevent the usual one. Capture code that names only gclid loses a growing share, silently, and the loss is invisible until you audit how many records carry an identifier.
- 02
Import mechanism: offline conversion import
Uploaded against the click identifier, either through the Google Ads API or as a file. The upload is the easy part; what limits it is how many of your records carry an identifier at all. Verify the current column format against Google's own template — it has changed before.
- 03
Deduplication
There's no shared event ID mechanism like Meta's. What matters instead is the counting setting on each conversion action — 'one' for lead-type conversions so a repeat submitter doesn't count three times, 'every' for ecommerce where a second purchase is a second sale. This is the single most common misconfiguration we find in Google Ads accounts.
- 04
Window and timing
Google's offline import window is 90 days from the click. Anything older can't be matched, and rows outside it fail as unmatched without much explanation. Measure your median click-to-outcome time against that before designing anything.
- 05
The Google Ads gotcha
A conversion action that stops receiving hits is flagged as inactive 30 days later — by which point a month of budget has already run against a missing signal. Check the last-received date on every action monthly; it takes two minutes and it's the cheapest monitoring available.
Google Ads · Phone call → sale · prove
How to prove the chain works — Google Ads · Phone call → sale
Source of truth
call records joined to a recorded sale outcome
- The same identifier confirmed on the call record, joined to your job or CRM system after a full real journey through every step.
- Qualified calls sent back confirmed arriving at Google Ads, verified by the match rate on the upload, not the success message.
- Call records joined to a recorded sale outcome reconciled against Google Ads per record over a fully closed window.
Google Ads · Phone call → sale · free audit
What we check in the free audit
- Click identifier: gclid, gbraid and wbraid
- Import mechanism: offline conversion import
- Deduplication
- Window and timing
- The Google Ads gotcha
Checked against
call records joined to a recorded sale outcome
Free30 minutesNo obligation
Google Ads · Phone call → sale · when not to buy
When this doesn't apply to you — Google Ads · Phone call → sale
- If your calls come overwhelmingly from a Google Business Profile listing rather than from paid clicks, those aren't ad conversions and shouldn't be uploaded as any. Track them separately.
- If you're running Performance Max exclusively and haven't separated your conversion actions, the import will work and the reporting won't tell you much. Worth sorting the account structure first.
- If your cycle from click to qualified calls sent back regularly exceeds the import window, the final event can't drive bidding whatever you build. Optimize toward a qualified call by duration instead and use the later data for budget decisions rather than for bidding.
- If almost none of your call records carry a click identifier today, that's the whole project.
Google Ads · Phone call → sale · what we deliver
The implementation, on Google Ads
Capture gclid, gbraid and wbraid on landing
Auto-tagging appends the identifier. Confirm it's enabled in every account — it gets switched off for cleaner analytics URLs more often than you'd expect, and that single setting removes conversion attribution, Enhanced Conversions and offline import in one go.
Persist it to the call record, joined to your job or CRM system
Store it against the call record at the moment the number is served, so the call and the click are joined before anyone picks up.
Send qualified calls sent back from the record
The call platform's webhook fires with the outcome once the office has dispositioned it, referencing the identifier captured at the visit. Dispatched to Google Ads through Google's offline conversion import.
Deduplicate and reverse
Conversion actions deduplicate on their own counting setting rather than an event id, so the setting matters more here than the payload. A job later cancelled should be adjusted, particularly where you're uploading at the booked stage rather than the completed one.
FAQ
Google Ads · Phone call → sale questions, answered
Not if you can import sales. It counts any call over a minimum duration, so keep it as secondary for reporting and make the imported sold-job action primary.
Yes. Most calls come from iPhones, and iOS clicks often arrive with gbraid or wbraid instead of gclid, so a number pool that only stores gclid loses a large share of mobile callers.
Because call volume and call quality are barely related. A channel producing lots of short unqualified calls looks excellent to bidding optimized on rings.
It doesn't, as a cookie — the gap is too long. It has to be written onto the call record, joined to your job or CRM system at the point of ad click, where it lives as a field rather than as browser storage.
A click identifier inside the 90-day window, a conversion action name that matches one configured in the account, a conversion timestamp for when the outcome happened, and a value. Read the match rate after uploading — a file can upload perfectly and match nothing.
Two to four days for the implementation, plus a closed reconciliation window before we'd call it verified. Capture and persistence are the fiddly parts; the import itself is usually an afternoon.
Yes, and the reference pages on this site cover the mechanics. The part that's genuinely tedious rather than clever is keeping gclid, gbraid and wbraid alive through multi-step forms and a call that arrives days after the visit, which fails silently at every stage.
More on Google Ads · Phone call → sale
- Meta · Phone call → saleHow to track phone call to sale for Meta Ads
- TikTok · Phone call → saleHow to track phone call to sale for TikTok Ads
- Microsoft · Phone call → saleHow to track phone call to sale for Microsoft Ads
RELATED GUIDES
Funnels next to phone call to sale, and the checks that close it
- Google Ads · Directory listing → enquiryHow to track directory listing to enquiry for Google Ads
- Google Ads · Chat → qualified leadHow to track chat conversation to qualified lead for Google Ads
- Google Ads × Call RecordsHow to reconcile Google Ads against your call tracking records
- Google Ads · Immigration lawGoogle Ads conversion tracking for immigration law firms
- Google Ads · PoolsGoogle Ads conversion tracking for pool installation and service companies
- Invoca → Google AdsConnecting Invoca to Google Ads
- Filevine → Google AdsConnecting Filevine to Google Ads
- Google Ads · Referral → closed saleHow to track referral to closed sale for Google Ads
Free · 30 min
Get phone call to sale tracked properly on Google Ads
WhatsAppFree30 minutesNo obligation
