If someone calls you from your website, does anything record that it happened? For a lot of Triangle businesses, the honest answer is no. You'll see a form submission in your inbox and call that a lead. You won't see the person who tapped your phone number from their car, talked to you for four minutes, and booked a job. That call is invisible to your analytics, even though it might be the thing that actually pays your bills.
This is a step-by-step guide to fixing that. You can set this up this week.
Why Calls Are the Conversion Most Websites Never Measure
Most analytics setups were built around forms because forms are easy to track. Someone submits, a thank-you page loads, a tag fires. Done.
Calls don't work that way. A tap on a phone number opens the native dialer and leaves your website entirely. Nothing about that action tells Google Analytics or your ad platform that a conversion just happened, unless you've specifically built something to catch it.
For phone-first categories, that's a serious blind spot. Think about home services, legal, medical, auto repair, and junk removal. These are urgent, high-trust purchases. People don't want to fill out a form and wait for a callback. They want to talk to a person right now. If your website only measures form fills, you're measuring the minority of your actual demand and making decisions based on incomplete data.
We saw this directly with Titan Junk Removal. Junk removal is an urgent, phone-first purchase. Someone standing in a garage full of things they want gone is on their phone, and they're calling the first company that makes calling easy. A site built around a contact form is the wrong tool for that moment. That's why the Titan Junk Removal site was designed mobile-first, with click-to-call as the dominant action throughout, rather than treating the phone as an afterthought to a desktop layout.
If your category rewards speed and trust over research and comparison, the same logic applies to you.
Tracking Number vs. On-Page Call Events: Which One You Need
There are two main ways to track calls from a website, and they answer different questions.
Dynamic tracking numbers swap the phone number shown on your site based on where the visitor came from. A visitor from Google Ads sees one number, a visitor from organic search sees another, a visitor from a Facebook link sees a third. Each number forwards to your real line, but the call gets logged against its source. This is the right tool when you're spending money on multiple channels and need to know which one is actually generating calls, not just clicks.
On-page call events track the tap itself, right where it happens, using the analytics platform you already have. When a visitor taps a "Call Now" button or a phone number link, that tap fires an event you can see in your reporting. This is simpler to set up, doesn't require a separate service or a monthly number-forwarding fee, and works well if you're mainly trying to understand which pages and channels drive calls, not which specific ad or campaign.
Here's the practical way to decide:
- If you run paid ads on more than one platform and need to defend that spend, get a tracking number setup, at least for your paid channels.
- If your main question is "which pages on my site are generating calls," on-page call events will answer that without added cost or complexity.
- Many businesses use both: tracking numbers for paid campaigns, on-page events for organic and direct traffic.
Either way, the setup below focuses on getting the click-to-call event itself tracked correctly, since that's the piece almost everyone skips.
Setting Up Click-to-Call Tracking for Mobile Visitors
Most of your calls are going to come from mobile visitors tapping a phone number, so this is where to focus first.
Step 1: Confirm your phone numbers are actually tappable links.
Check your site on your own phone. Every phone number should be a link formatted as tel: followed by the number, not plain text. If tapping the number doesn't open your dialer, nothing you do in analytics will fix that, because there's no click event to catch. This sounds basic, but it's one of the most common gaps we find on sites that weren't built with calls in mind.
Step 2: Add a call tracking tag in Google Tag Manager.
If you're using Google Tag Manager, GA4 has a built-in trigger type for this. Set up a trigger that fires on "Just Links" clicks where the URL starts with tel:. Attach a GA4 event tag to that trigger, name the event something clear like phone_call_click, and publish the container.
Step 3: Test it before you trust it.
Open your site on a phone, tap the number, and check GA4's real-time reporting for the event. If it doesn't show up, check that the trigger is actually catching tel: links and that the tag is attached to the right trigger. This is a five-minute check that saves you from weeks of bad data.
Step 4: Do the same for any click-to-call buttons, not just text links.
Sticky call buttons, header buttons, and "Call Now" banners on mobile all need the same tel: link structure and the same trigger will typically catch them, but confirm each variant fires the event.
If your site's mobile experience wasn't built with calls as the primary action, this is also a good moment to ask whether the layout itself is working against you. A site that buries the phone number below a hero image and three paragraphs is asking mobile visitors to work harder than they will. Our web development work starts from the assumption that for phone-first businesses, the number needs to be visible and tappable from the first screen.
Connecting Call Data Back to the Pages That Generate It
Tracking that a call happened is only half the job. The valuable part is knowing which page the visitor was on when they called.
Once your phone_call_click event is firing, GA4 automatically captures the page path as part of that event's parameters. You can build a simple report, or a GA4 exploration, that breaks down call events by landing page or by the page the click happened on. That report answers the question that actually matters: which pages on your site turn visitors into callers, and which pages get traffic but no calls at all.
This is where things get interesting. You might find that your homepage gets the most traffic but your services page gets more calls per visitor. Or that a blog post you wrote two years ago is quietly generating calls every week because it ranks well and has a clear number at the top. You won't know any of this until you can see calls broken down by page.
If you're also running paid search or local SEO campaigns, connect this same event data to your channel reporting so you can see which channels bring in visitors who call, not just visitors who click. A channel that generates lots of traffic but no calls isn't actually working for you, no matter what your cost-per-click looks like.
What to Do With the Data Once You Have It
Data without a decision attached to it is just noise. Here's what to actually do once you can see call events by page and channel.
Double down on pages that generate calls. If a specific service page consistently produces calls, that page deserves more internal links, more visibility in your navigation, and possibly its own paid campaign.
Fix or cut pages that get traffic but no calls. A page pulling in visitors with no call activity has a problem: unclear messaging, a buried phone number, or the wrong audience finding it. Diagnose before you assume the traffic is worthless.
Reallocate ad spend toward channels that produce calls, not just clicks. If you're paying for clicks that don't convert to calls in a phone-first business, that spend isn't working, regardless of what the platform's own dashboard says about "conversions."
Check your site speed on mobile. A visitor who's ready to call will abandon a slow-loading page before they ever see your number. If you haven't checked recently, run a free speed test and see where you stand.
Revisit this data monthly, not once. Call patterns shift with seasons, campaigns, and even changes you make to the site itself. A one-time setup that nobody looks at again is barely better than not tracking at all.
If your current analytics can't answer "which pages generate our calls," that's not a minor gap for a phone-first business. It's the difference between guessing and knowing where your leads actually come from. And if the deeper issue is that your site wasn't built to make calling easy in the first place, that's worth a harder look. We cover exactly that kind of setup, along with the SEO and analytics work to make the data useful once it's flowing, and you can get started whenever you're ready to fix it.
This week's task: open your site on your phone, tap your own number, and confirm whether anything records that it happened. If nothing does, that's your starting point.