Implementations / Call Tracking
Connect CallRail calls to GA4 and Google Ads.
A lot of home service and legal businesses live or die on the phone, and phone calls do not carry a click ID by themselves. CallRail swaps in a tracking number per visitor so a call can be tied back to the keyword, ad, and session that produced it. The same tracking number approach works whether the visit came from a search ad, a display ad, or an organic listing, since the swap happens the moment someone lands on the site.
- $0 setup. Month to month.
- 30-day guarantee, pay only if satisfied.
- Free proposal within one business day.
The workflow
From a ringing phone to a counted conversion.
The field map
CallRail's session snippet swaps a static number on your site for a tracking number tied to that visitor, then logs the source, keyword, landing page, and call duration once the phone rings. We map which of those fields becomes the conversion event. A missed call still logs in CallRail even without an answer, which matters if you also want to see how many calls never got picked up.
The identity match
The visitor's gclid is captured by CallRail's own tracking script the moment they land on your site, before the call happens. That is what lets a call three days later still get credited to the exact ad click that started the session. That captured gclid stays attached for as long as CallRail's own session window allows, which we confirm at setup rather than assume.
Where the data enters
CallRail has native connections in its Integrations settings for both Google Ads, which receives qualified calls as offline conversions, and GA4, which receives call events for wider funnel reporting. We turn those on and set the qualifying rule. Both connections can run at the same time without conflicting, since they read from the same underlying call log.
How failures surface
A call only counts as a marketing conversion once it is marked qualified, whether by CallRail's automatic call scoring or by someone on your team tagging it. An unmarked call sits in CallRail's log but never reaches Google Ads, so we set a default rule instead of leaving it silent. We start with a sensible duration threshold for automatic qualification, then adjust it once we see how your real calls run.
What makes this hold up over time.
Access we need first
Admin access to your CallRail account to configure the tracking script, plus your Google Ads login so the conversion action can be set up there. GA4 access if you want call data flowing there too. We do not touch your phone system itself, only the CallRail account managing the numbers.
What gets delivered
A working CallRail tracking number swap on your live site, both integrations turned on and mapped, and a written note on what counts as a qualified call so your front desk knows the rule too. We leave a short list of the exact settings changed, in case your own team reviews them later.
The acceptance test
We place a real test call from a tracked session, mark it qualified the way a real call would be handled, and confirm it appears in Google Ads' conversion action within CallRail's normal reporting window before calling it done. If the qualifying rule catches too many or too few calls once live, we adjust it at no extra charge.
What is out of scope
Whether front desk staff pick up every call, and how they score calls as qualified or not, is your team's process. We build the pipe and set a sane default. Call handling training is a separate service, one we can point you toward if you want it.
How the setup runs.
01
Audit
We check how many tracking numbers your CallRail plan needs, where the current static number appears on your site, and whether call scoring is already on or needs to be configured.
02
Build
We install or fix the dynamic number swap script, turn on the Google Ads and GA4 integrations inside CallRail, and set the rule for which calls count as qualified conversions.
03
Verify
We run a real test call through a tracked session, mark it qualified, and confirm it lands in both Google Ads and GA4 with the right source before we hand it back.
CallRail to GA4 and Google Ads FAQ.
Only once you turn on CallRail's Google Ads integration and mark a call qualified. Without that step, calls sit in CallRail's own dashboard as data but never reach your Google Ads account as a conversion.
That is a rule you set, not a fixed default. CallRail can score calls automatically by duration and keywords spoken, or a person can tag each call. We help you pick a rule that matches how your team actually answers the phone.
Yes, within CallRail's own attribution window for that session, which we confirm at setup since it can vary by plan. The identity match happens the moment they land on your site, not the moment they dial.
It can. If CallRail's script does not load, the number swap does not happen and that call falls back to your static number, which shows as unattributed rather than tied to an ad. We report that rate honestly instead of hiding it.
Just Google Ads if all you care about is bidding on the right keywords. Add GA4 if you also want calls to show up in your wider funnel reporting alongside form fills and other events.
Get your CallRail setup scoped.
Tell us how calls currently reach your team and what, if anything, CallRail already tracks. A free proposal, with a fixed price, reaches you within one business day of hearing back from us.