A marketing director at a Phoenix HVAC company asked me last month why her Google Ads reports showed 47 conversions but her phone logs only had 31 calls. I asked if she was using session-level or source-level DNI.
"We have call tracking."
That's not an answer. And honestly? I've had this conversation maybe fifty times. It never gets less frustrating.
Call tracking sounds simple — put a tracking number on your site, count the calls. But the vocabulary gap between "I have call tracking" and "I understand my attribution" is where thousands of dollars go to die. Your agency reports a 3:1 ROAS; your CFO sees a 1.8:1 on closed jobs. The gap? Attribution window, offline conversion lag, and nobody agreeing on what counts as a conversion. I've watched operators lose six figures annually on this mismatch alone.
This glossary covers the 25 terms you'll hear when setting up call tracking, interpreting reports, or arguing with vendors about why the numbers don't match. Not pay-per-call terms — those are in the pay-per-call glossary. This is specifically about tracking, attribution, and the technology that ties phone calls to marketing spend. (And yes, I'll probably oversimplify something — I'm not perfect.)
Core Tracking Concepts
1. Call Tracking
Using dedicated phone numbers to attribute inbound calls to their marketing source. Someone clicks your Google Ad, lands on your site, sees a tracking number, and calls. That number rings, your platform logs it as a Google Ads conversion.
Simple in concept.
In practice, you're managing number pools, attribution windows, offline conversion imports, and trying to reconcile three different reporting systems that all count calls differently. The reconciliation part is what keeps me up at night.
2. Tracking Number
A phone number provisioned specifically for attribution purposes. It routes through your call tracking platform, which logs metadata (source, duration, caller ID, recording) before forwarding to your actual business line.
Tracking numbers are typically provisioned through Twilio, Telnyx, or Bandwidth. Local numbers run $1-3/month; toll-free is $2-4/month. You need one per source for source-level tracking, or a pool of 10-100 for session-level — see below.
3. DNI (Dynamic Number Insertion)
JavaScript that swaps the phone number displayed on your website based on where the visitor came from. Google Ads visitors see one number; Facebook visitors see another; organic visitors see a third.
DNI is the workhorse of call tracking. Without it, you'd need separate landing pages for each traffic source — nobody wants that. The DNI explainer covers implementation details, but the short version: you paste a script, configure your number pool, and the swap happens automatically. Usually. (I've debugged enough broken DNI implementations to know "usually" is doing heavy lifting there.)
4. Source Pool
A DNI configuration where one tracking number is assigned per traffic source. All Google Ads visitors see 555-0101. All Facebook visitors see 555-0102. When 555-0101 rings, you know it came from Google Ads.
Pros: cheap (fewer numbers), simple. Cons: no visitor-level attribution. Two Google Ads visitors call five minutes apart? You can't tell which session generated which call.
5. Session Pool
A DNI configuration where each website visitor gets a unique tracking number for their session. Visitor A sees 555-0101; Visitor B (arriving 30 seconds later) sees 555-0102.
When Visitor A calls, you know it was them — and you can tie that call to their exact session: which pages they viewed, how long they browsed, which ad brought them in, even which keyword if you're passing GCLID.
Session pools cost more (bigger number inventory) but pay for themselves in high-value verticals like legal intake, home services, and insurance. If a call is worth $50+, you want session-level attribution. Period.
6. Pool Size
The number of tracking numbers in your session pool. You need enough to cover peak concurrent visitors without running out.
The math: peak concurrent visitors × average session duration ÷ 60 = minimum pool. A site with 40 concurrent visitors and 4-minute sessions needs at least (40 × 4) ÷ 60 ≈ 3 numbers in active use at any moment. But sessions overlap unpredictably. Double or triple for safety. Most mid-traffic sites run 15-30 numbers; high-traffic sites need 50-100.
Run out of numbers and visitors see your main business line — no attribution, no tracking. Ask me how I know. (It was a bad week.)
Attribution Concepts
7. Attribution Window
The time period during which a call can be credited to a marketing touchpoint. If someone clicks your ad Monday and calls Thursday, does the ad get credit?
With a 7-day attribution window, yes. With a 24-hour window, no. Set it too short and you miss conversions from people who research before calling. Set it too long and you over-attribute to stale clicks.
Most platforms default to 30 days, which is too generous for many verticals. Emergency services (plumber at 2am) might use 48 hours. Considered purchases (roofing, legal) might use 14 days. There's no universal right answer — it depends on your sales cycle, and honestly most people never think about it after initial setup. That's a mistake.
8. First-Touch Attribution
Crediting the first marketing touchpoint for a conversion. Visitor finds you via organic search in January, returns via Google Ads in March, calls. First-touch gives organic the credit. Favors top-of-funnel awareness channels.
9. Last-Touch Attribution
Crediting the final touchpoint before conversion. Same scenario — last-touch gives Google Ads the credit. Most call tracking platforms default to last-touch because it's simple and actionable.
10. Multi-Touch Attribution
Distributing credit across multiple touchpoints. Sounds sophisticated. And look, I get the appeal — it feels more "fair" than picking winners. But in practice it requires hundreds of conversions to be statistically meaningful. Most SMBs don't have the scale. I've seen agencies sell multi-touch attribution setups to companies with 30 monthly conversions. That's not analysis, it's astrology.
11. Offline Conversion Import
Pushing call conversion data back into ad platforms (Google Ads, Meta) so their algorithms can optimize toward phone calls, not just clicks.
Google calls this "offline conversion import" or "enhanced conversions for leads." You export call data from your tracking platform, match it to click IDs, and upload. Google then knows which clicks generated actual phone leads — and optimizes bidding accordingly.
This is probably the single most impactful thing you can do for paid search performance on call-heavy campaigns. If you're running Google Ads and not importing offline conversions, you're leaving money on the table. For accurate session data to match against, JustAnalytics captures visitor sessions without consent banners — useful for tying calls to specific click IDs.
Why don't more people do it? Setup is annoying. Not hard, just annoying.
Call Handling Concepts
12. Whisper Message
A brief audio prompt played only to the agent before connecting the caller. "Google Ads lead, roofing, Dallas." The caller doesn't hear it.
Whispers give agents context without the caller knowing. They can skip "how did you hear about us?" and personalize the opener: "Thanks for calling about roofing — are you dealing with storm damage?"
The tradeoff: whispers add 1-3 seconds of connection delay. In speed-sensitive verticals, that matters. Most platforms let you toggle them per campaign.
13. Call Disposition
A tag applied after a call ends to categorize the outcome. "Qualified lead," "wrong number," "price shopper," "appointment booked," "callback requested."
Disposition codes are how you measure lead quality beyond duration. A 5-minute call that ends in "not interested" is different from a 5-minute call that ends in "appointment scheduled." Your CRM and reporting depend on agents tagging calls accurately.
The painful truth: disposition accuracy depends on agent discipline. Bad dispositions = bad data = bad decisions. Audit randomly. And when you do, prepare to be disappointed — I've never audited a team that didn't have at least 20% misclassifications.
14. Call Recording
Capturing audio for quality assurance, training, and dispute resolution. Most call tracking platforms offer recording as a core feature or add-on. VeloCalls charges 3¢/min.
Eleven states require all-party consent for recording (California, Connecticut, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, New Hampshire, Pennsylvania, Washington). A disclosure at call start — "this call may be recorded for quality assurance" — covers you in commercial contexts.
If you're running pay-per-call and not recording, you're flying blind. Disputes happen. Recordings settle them.
15. Transcription
Converting call audio to text. VeloCalls charges 4¢/min. Powers AI features (sentiment, intent, summarization) and lets you search across thousands of calls for specific phrases.
16. Sentiment Analysis
AI that detects caller emotion — frustrated, satisfied, confused, angry. VeloCalls charges 5¢/use. Practical use: QA prioritization. Review "frustrated" calls first, catch service problems before they become Yelp reviews.
Accuracy is good but not perfect. Maybe 80-85% on clear-cut cases, worse on ambiguous ones. Don't fire anyone over a "frustrated" tag without listening to the actual call.
17. AI Call Summary
Auto-generated summary of a call's key points. VeloCalls charges 10¢/call. Saves time — read a paragraph instead of listening to a 6-minute recording. Useful for pushing context into CRMs before follow-up calls.
Technical Concepts
18. STIR/SHAKEN
Caller ID authentication framework that reduces spoofing. If your tracking numbers show "B" or "C" attestation (partial verification), investigate — they're more likely to be spam-flagged. "A" attestation means full verification. This matters more every year as carriers crack down.
19. Caller ID
The phone number displayed to the called party. Configure whether to pass the original caller's ID (helps agents recognize repeat callers) or display your business line (helps with callbacks). No universal right answer.
20. ANI (Automatic Number Identification)
The technical mechanism that delivers caller ID through the phone network. For attribution, ANI identifies repeat callers across sessions — same phone number, even if their session cookie expired.
21. Call Forwarding
Routing incoming calls to a different number. Your tracking number forwards to your business line (or IVR, or agent queue). Can be unconditional or conditional (forward if no answer, forward if busy).
22. IVR (Interactive Voice Response)
The automated menu callers hear before reaching an agent. Keep it short — 2-3 prompts max. We've seen 15-20% of callers abandon when IVR exceeds 4 prompts. See the IVR abandonment study for data.
Every marketing person who's listened to their own IVR realizes it's too long. Every one of them.
23. Ring-To Time
Delay between call connection to your platform and the destination phone ringing. Lower is better — callers notice delays over 2 seconds.
24. Answered Call Rate
Percentage of inbound calls answered by an agent (vs. voicemail/abandoned). An 85% vs. 95% answer rate is a 10% revenue delta on the same traffic.
Track it obsessively. This is one of the few metrics that's actually actionable.
25. Conversion Window
The period during which a call can be matched back to an ad click for offline conversion import. Google Ads allows up to 90 days; Meta allows 7. Matters for accurate ROAS on long sales cycles.
Quick Verdict
If I had to pick three terms from this list to actually understand — not just memorize — they'd be: session pool (because visitor-level attribution is the difference between guessing and knowing), attribution window (because it's the source of most "the numbers don't match" arguments), and offline conversion import (because feeding call data back to ad platforms is how you stop optimizing for clicks and start optimizing for revenue).
The rest? Operational detail. Important if you're configuring platforms or debugging tracking issues, but the big three are what move the needle on whether your call tracking actually improves decisions.
Could I be wrong about the prioritization? Sure. But I've helped set up tracking for dozens of pay-per-call campaigns, and these are the three concepts that generate the most confusion and the biggest dollar impact when you get them right.
For paid traffic, click fraud drains budgets before calls even happen — ClickzProtect catches invalid clicks before they cost you. And if you're tying call data to on-site behavior, JustAnalytics tracks sessions without requiring cookie consent banners.
Frequently Asked Questions
What's the difference between session-level and source-level call tracking?
Source-level tracking assigns one phone number per traffic channel — all Google Ads visitors see the same number. You know which channel drove the call, but not which specific visitor. Session-level tracking assigns a unique number to each website visitor for their session. You can tie calls to exact on-site behavior: pages viewed, time on site, the specific ad clicked. Session pools cost more (more numbers) but give better attribution data for high-value verticals.
How long should my call attribution window be?
Depends on your sales cycle. For emergency services (plumbing leaks, HVAC breakdowns), 24-48 hours captures most conversions. For considered purchases like roofing or legal services, 7-14 days is more realistic. Medicare Advantage during AEP might need 30+ days. Set it too short and you miss delayed callers; too long and you over-attribute to stale touchpoints. Start with 7 days, adjust based on your data.
What is a whisper message and when should I use one?
A whisper is a short audio message played only to the agent before connecting the caller. Something like: "Google Ads, HVAC lead, Phoenix." The caller doesn't hear it. Use whispers when your agents handle multiple campaigns or verticals — it lets them personalize the opening without asking "how did you hear about us?" Whispers add a second or two of connection delay, so skip them if speed-to-answer is critical.
How do I prevent tracking number spam flagging?
Three things: rotate numbers that hit high volume (carriers flag sudden spikes), ensure STIR/SHAKEN attestation is passing (your platform should show this), and avoid sharing number pools across unrelated campaigns. Numbers that previously belonged to bad actors can inherit their reputation — when provisioning new numbers, test them before scaling. Some platforms offer reputation monitoring; use it.
Try VeloCalls for Your Vertical
Call tracking and pay-per-call platform built for HVAC, plumbing, roofing, PI lawyers, Medicare brokers, and insurance. Smart routing, real-time bidding, visual IVR builder, AI conversation intelligence (transcription, sentiment, summaries). Per-minute pricing — Managed carriers start at 4¢/min, BYOC at 2¢/min, both drop as usage scales.