A call that lasts three minutes looks like a great lead in Google Ads. It might be a homeowner booking a full kitchen clean. It might also be a supplier, a job applicant or someone who wanted a service you do not offer. Native call tracking cannot tell the difference, because it only knows that a call happened and how long it lasted.
Importing qualified calls closes that gap. You record what happened on the call in a call-tracking tool or customer relationship management (CRM) system, then send the good outcomes back to Google Ads. This post covers how that works with CallRail and similar tools, how click IDs are captured, the import options and how enhanced conversions for leads fits in. For the basics of call tracking first, see my Google Ads call tracking overview.
Why import qualified calls instead of counting every call?
You import qualified calls because Smart Bidding optimises toward whatever you count as a conversion. If every call over 60 seconds counts equally, Google learns to find more long calls, including the wrong ones. If only booked jobs count, it learns which searches, times and audiences produce customers.
The difference shows up in three places:
- Bidding: Target CPA or Maximise conversions optimise for real leads, not call volume. Value-based strategies can favour bigger jobs when you import values.
- Reporting: Cost per conversion becomes cost per qualified lead or per booked job, which a business owner actually understands.
- Keyword decisions: You can see which search terms bring calls that never book and add them as negatives.
My post on Smart Bidding strategies explains how each strategy uses these signals.
How do call-tracking tools connect calls to Google Ads clicks?
Call-tracking tools connect calls to clicks by showing each website visitor a tracking number and remembering which ad click that visitor came from. When the visitor calls, the tool knows the source, the landing page and the click ID.
The click ID is usually the GCLID (Google Click Identifier), a parameter Google adds to your landing page URL when someone clicks an ad. On some iOS traffic you may also see gbraid or wbraid parameters instead. A tool such as CallRail captures these through its number-swap script, which is why that script must run on every landing page.
The typical flow:
- A visitor clicks your ad and lands with a GCLID in the URL.
- The call-tracking script stores the GCLID and shows a tracking number from its pool.
- The visitor calls. The tool records duration, recording (if enabled and legally disclosed) and source.
- Someone on the team, or an automated rule, qualifies the call.
- The tool or your CRM sends the qualified call to Google Ads with the GCLID, conversion time and value.
This is separate from Google forwarding numbers. If you use a third-party tool for website calls, do not also run Google's website call conversions on the same number, or the two swaps can conflict.
What are the ways to import call conversions?
There are four common routes, and the right one depends on where the call outcome is recorded and what identifier you have.
| Route | Identifier used | Best for |
|---|---|---|
| Native integration (CallRail and similar) | GCLID captured by the tool | Businesses that qualify calls inside the call-tracking tool |
| Offline conversion import from a CRM | GCLID saved on the CRM record | Businesses whose bookings and invoices live in a CRM |
| Call conversion import | Caller ID and call start time | Calls through Google forwarding numbers, qualified later |
| Enhanced conversions for leads | Hashed email or phone number | Leads where a GCLID was not stored or was lost |
Uploads can go through scheduled files such as Google Sheets, the Google Ads API, Google's Data Manager, or automation tools like Zapier and Make. Google has been consolidating these options, so check the current import documentation before choosing.
Native integrations
Most call-tracking platforms, CallRail included, offer a Google Ads integration that sends calls as conversions. Depending on the tool and plan, you can usually choose which calls to send, such as first-time callers, calls above a duration, or calls tagged as a lead. That tagging step is what turns raw call volume into qualified calls.
CRM imports with GCLID
If jobs are booked in a CRM such as GoHighLevel or HubSpot, the GCLID needs to reach the contact record. For calls, that usually means the call-tracking tool passes it through its CRM integration. For forms, a hidden field filled from a first-party cookie does the job. My guide to offline conversion tracking from your CRM covers the hidden field method in detail.
How should you qualify calls and set lead values?
You qualify calls by agreeing simple stages with the business, then importing the stage that best predicts revenue. Keep it practical; a receptionist will not fill in a ten-field form after every call.
A setup I use for local service businesses:
| Stage | Who marks it | Imported as |
|---|---|---|
| Answered call over threshold | Automatic | Secondary, for observation |
| Qualified lead (real service, in area) | Staff tag in call tool or CRM | Primary |
| Booked job | CRM stage change | Primary, with estimated value |
| Completed job | CRM or invoicing | Conversion adjustment or value update |
For values, start with an honest estimate of an average job, then move to real job values once they are recorded reliably. If you import both "qualified lead" and "booked job" as primary, the same caller counts twice; either pick one, or give each a value that reflects its worth and accept that conversion counts will include both stages.
Imports must arrive within the conversion action's click-through window, and daily uploads help bidding react sooner than weekly batches.
Where do enhanced conversions for leads fit?
Enhanced conversions for leads match conversions using hashed customer data, such as an email address or phone number, instead of relying only on a GCLID. When someone submits a form, the Google tag sends a hashed version of the details they entered. Later, you upload the qualified conversion with the same hashed details from your CRM, and Google matches the two.
It is useful when:
- A GCLID was stripped, never stored or not passed into the CRM.
- Leads start on a form and finish with a phone call to book.
- You want a more durable setup as browsers restrict cookies.
It works best for form leads. For phone-only callers you rarely have an email address, so matching relies on the phone number, and results depend on the data available. I walk through the enhanced conversions setup in my video above, and my written guide to enhanced conversions for Google Ads covers the web version. Hash data with SHA-256 after normalising it, follow Google's customer data policies and make sure your privacy policy covers the processing.
What should your import setup checklist include?
- Call-tracking script or GCLID capture on every landing page
- Auto-tagging enabled in Google Ads
- Clear qualification stages agreed with the team
- One import conversion action per stage, with primary or secondary set deliberately
- Values assigned, even if estimated
- Daily uploads, with failed rows checked
- Native call conversions reviewed so the same call is not primary twice
Final thoughts
Counting calls is a good start; counting the calls that turned into customers is what makes Smart Bidding useful. Start with one qualified stage, import it reliably and add values once the data is clean. If you want help connecting your call-tracking tool or CRM, see my advanced conversion tracking service or my CRM and marketing automation service.
