Case File 03 · Services
Call Attribution & Phone Lead Tracking
Connect every phone call back to the ad, keyword, or campaign that drove it. CallRail integration, dynamic number insertion, GA4 event mapping, delivered in five business days.
TL;DR
Phone calls are conversions. Most accounts treat them as unattributed because they only have one number on the site. We install dynamic number insertion, wire CallRail to Google Ads, and map every call into GA4 with full campaign context, in five business days.
The Definition
What Is Call Attribution?
Call attribution is the practice of connecting every inbound phone call back to the ad, keyword, or campaign that drove the visitor to dial. For service businesses, dealerships, law firms, and B2B sales motions where the phone is the primary conversion event, calls are revenue. Treating them as untrackable is leaving spend optimization on the table.
The technical mechanism is dynamic number insertion (DNI). A tracking platform (CallRail is the industry standard) maintains a pool of phone numbers. When a visitor arrives, JavaScript on the page reads their traffic source (Google Ads campaign, organic search, direct, referral) and swaps the displayed number for one assigned to that source. The user dials; the call is routed through CallRail to your real business line; the campaign context is recorded against the call in real time.
From there, every call shows up in your reporting the same way a form fill does. Google Ads can see which campaigns produced calls. GA4 can attribute them in the conversion path. If your CRM records call outcomes (qualified, scheduled, closed-won), those outcomes can be pushed back to Google Ads as offline conversions, so bidding optimizes for revenue-producing calls instead of every call over 30 seconds.
The result for most phone-led accounts: 30-50% of total conversions become visible for the first time, and the same ad spend produces a measurably better cost per qualified lead once the bidding has phone-call signal to work with.
Suspects of Interest
Who This Is For
If phone is the primary conversion or a significant share of total leads, call attribution is almost always the highest-ROI tracking project to open first.
Profile A
Law, insurance, and professional services
Phone is the primary lead channel. Closed-won revenue depends on call volume, and you have no idea which campaigns are producing the qualified calls.
Profile B
Home services, HVAC, plumbing, roofing
Local service ads and Google Ads driving call volume from multiple campaigns, but every call lands as unattributed because there's only one phone number on the site.
Profile C
Auto dealerships and high-AOV retail
Showroom visits start with a phone call. The sales team takes the name; the ad platform never finds out the call ended in a sale.
Profile D
B2B with a phone-led sales motion
Inbound discovery calls book on every campaign and your CRM has no field for which ad source produced them.
Scope of Work
What We Deliver
Every call-attribution engagement covers the same scope.
- Call-source audit: 30 days of inbound call volume reconciled against ad-platform click and lead data to size the attribution gap
- CallRail account configuration: tracking pool sized to your traffic volume, source-rule logic for paid versus organic versus direct
- Dynamic number insertion (DNI) installed sitewide so each visitor sees a tracking number tied to their actual campaign source
- Source attribution rules: Google Ads campaign, keyword, and ad-group passthrough so calls land in CallRail with the full ad context attached
- GA4 event mapping: phone_call events with duration, source, campaign, and qualified-lead flag so calls show up in attribution reports alongside form fills
- Call-to-sale tracking: recording outcome (qualified, closed, no-show) and pushing it back into Google Ads as an offline conversion when CRM data confirms the sale
- Spam and short-call filtering so junk volume doesn't poison the attribution model
- Documentation covering tracking pool size, source rules, GA4 mappings, and how to add new campaign sources later
Fixed price · Five business days · Pay when complete
The Process
How It Works
Five business days from kickoff to handoff. Same shape every engagement; depth scales with call volume.
Day 1
Call Audit
Pull 30 days of inbound call data from your current phone system. Reconcile against ad-platform reporting. Size the gap between calls received and calls credited to a source. Written report by end of day.
Day 2
CallRail Setup
Provision the CallRail account, configure tracking pool sizing for your traffic volume, build source rules for paid versus organic versus direct, and connect the Google Ads integration so campaign data flows through.
Day 3
DNI & Source Attribution
Install dynamic number insertion sitewide. Wire campaign, keyword, and ad-group passthrough so every call records its full source context. Test with live ad clicks before going public.
Day 4
GA4 & Offline Conversions
Map call events into GA4 with full source attribution. Configure CallRail to push qualified calls into Google Ads as offline conversions so the platform can optimize bidding on phone leads, not just form fills.
Day 5
Handoff
Walkthrough with your team. Spam filtering rules documented. Source rules explained. Reporting walkthrough so your team can read the dashboards on day one.
Evidence Locker
The Stack We Integrate
The tools we wire together on every call-attribution engagement.
- CallRail
- Dynamic Number Insertion
- Google Ads
- GA4
- Google Tag Manager
- HubSpot
- Salesforce
- Offline Conversion Imports
From the Files
Related Case File
B2B / Long Sales Cycle
A B2B services client was running Google Ads with no phone attribution. Sales took inbound calls all day; nobody knew which campaigns were producing them. Cost-per-form-fill in the account looked acceptable, but the real conversion was the call, and the platform had no idea calls were happening.
We installed CallRail with dynamic number insertion, wired the Google Ads integration, and mapped call outcomes through the CRM back into Google Ads as offline conversions. Implementation took three days; reconciliation took two.
Once the platform had call-to-sale signal in the bidding algorithm, cost per closed-won dropped by roughly 35% over the following quarter, not from more spend but from the spend shifting toward the campaigns that actually produced revenue. The team finally bought more leads at lower cost because they finally knew where the closed-won was coming from.
Interrogation
Frequently Asked Questions
How does call tracking work?
Call tracking replaces your single phone number with a pool of tracking numbers, each tied to a specific traffic source. When a visitor arrives from a Google Ads click, the page displays a number associated with that campaign. When they call it, the tracking platform (we use CallRail) records the campaign, keyword, and ad-group context, then forwards the call to your real business line. The call arrives at your team with no friction; the attribution arrives in your reporting.
What is dynamic number insertion (DNI)?
Dynamic number insertion is the technique that swaps the phone number displayed on your site based on who's visiting. A user arriving from a paid Google search sees one number; a user from organic Facebook sees a different one; a direct visit sees a third. All numbers route to the same internal phone system. The swap happens in milliseconds, before the user has a chance to read the page, and the source attribution is recorded against the call from the moment it's dialed.
Can I see which ad drove a phone call?
Yes. That's the entire point of call attribution. With CallRail wired to Google Ads, every call records the campaign, ad group, keyword, and even the search term that triggered the click. Reports show calls per campaign exactly the way they show form fills, so paid search optimization can finally include phone leads in the bid logic instead of treating them as invisible.
How long does call tracking setup take?
Five business days for standard installations: one day of audit, one day of CallRail configuration, one day of DNI deployment, one day of GA4 plus offline conversion wiring, one day of handoff. Multi-location accounts or accounts with custom phone routing (e.g., department-based switchboards) can extend by a day or two, which we'll flag during discovery.
How big does the tracking number pool need to be?
Pool size scales with simultaneous-visitor count, not total traffic. The rule of thumb: enough numbers to give every concurrent visitor a unique one for the length of their session. CallRail's own sizing recommendation is roughly one number per 100 unique daily visitors as a baseline; we size yours based on your actual concurrent peaks pulled from analytics during the audit, so you're not over-buying.
Will call tracking hurt my local SEO or NAP consistency?
No, when done correctly. Your real business number stays published as the primary NAP citation across Google Business Profile, directories, and on-page schema. Tracking numbers are added in addition to (not in place of) the real number, and they're swapped in only on the website, not in third-party listings. Local search engines never see the tracking pool, so name-address-phone consistency stays intact.
Can phone calls be sent back to Google Ads as conversions?
Yes. CallRail pushes qualified call events into Google Ads as offline conversions, which means the platform's bidding algorithm starts optimizing for actual phone leads instead of just form submits. Combined with call-outcome data from your CRM, Google Ads can optimize for revenue-producing calls rather than every call that lasts more than 30 seconds.
Ready to open your own case?
15 minutes is enough to tell whether call attribution is the biggest gap in your stack, or whether one of the other five case files is leaking more.