Answers

How Do I Track Phone Calls From My Website?

If a visitor reads your website and then picks up the phone, that call is invisible to your analytics unless you capture it on purpose. You track phone calls from your website by routing the number shown on the page through a call tracking service, which hands the visitor a forwarding number, connects them to your real line, and records which marketing source sent that caller.

That is the whole trick. A form on your contact page fires a measurable event inside the browser. A phone call leaves the browser the instant someone dials, so nothing in Google Analytics ever sees it on its own. Call tracking puts a measurable step back in the middle of that call without changing anything for the person dialing.

Why calls from your site go uncounted by default

Most owners assume the phone channel is small because the dashboard says so. The dashboard is wrong, not the phone. Clicks, form fills, and checkouts all leave a digital trail. A voice call does not. Unless you insert a tracking layer, every call that started on your website gets filed under direct or unknown, and the pages and campaigns that actually drive the phone get no credit. Starve a channel of credit long enough and you will end up cutting the very thing that works.

The mechanism: tracking numbers and dynamic number insertion

Call tracking rests on two building blocks. Pick based on how precise you need the attribution to be.

Static tracking numbers

You assign one dedicated number per channel. One number lives on the website, another on your Google Business Profile, another on a printed flyer. Each one forwards to your real line. When a number rings, you know the channel it came from. This is blunt but dependable, and it is the right tool for separating online activity from offline sources.

Dynamic number insertion

Dynamic number insertion, usually shortened to DNI, is the precise version. A small script swaps the phone number displayed on your site for each visitor, drawing from a pool of numbers. A session from organic search is shown a different number than a session from a paid ad. Because each visitor gets a distinct number for the length of their visit, the platform can tie a connected call back to the source, the campaign, the landing page, and in many cases the search that brought them in.

DNI needs a few things to stay accurate:

• A large enough pool of numbers so two visitors are never shown the same one at the same time
• Consistent tagging on your inbound links, so the source is known before the number swap happens
• A script that loads fast and does not shift the page as it replaces the number

What call tracking captures, and what it does not

A good setup records more than the fact that the phone rang. For each call you can usually see:

• The caller's number and rough location
• The source, campaign, and landing page that produced the call
• Ring time and call duration, a rough proxy for whether the call was real
• Whether it is a first-time or repeat caller
• An optional recording or transcript, where local consent rules allow it

What it cannot do is tell you the call became a customer. Duration hints at quality, but a long call can still end in nothing and a short one can close a job. The outcome lives in your CRM, where sales marks which calls turned into work. Call tracking gets the lead to the door. It does not pretend to know what happened once the conversation started.

The tel link shortcut is not enough on its own

The simplest thing you can do is make your number a tappable tel link and fire an event when someone taps it. Do it. It costs nothing and gives you a floor. But understand what it measures: intent, not conversation. A tap is not a connected call. People misdial, change their mind, reach voicemail, or tap twice. Click counts always run ahead of real calls, so treat a tap as a ceiling for interest, never as a count of actual conversations.

How we set it up on sites we build

We run measurement like this only on websites we build and manage, because the tracking has to be wired into the markup, the analytics, and the reporting as one system. The process is consistent:

• Choose static or DNI based on whether you need channel-level or keyword-level attribution
• Provision tracking numbers that you own and that forward to your real line, so leaving is never held hostage
• Send connected calls into GA4 as a conversion event, deduplicated against form submissions so the same lead is not counted twice
• Pass the call data into your CRM so the sales outcome attaches to the marketing source that created it
• Reconcile it all in the monthly report, next to every other channel

The retainer that covers this, and the custom site it rides on, is described on the services and pricing pages rather than quoted here. See /services/seo/ for the measurement scope and /pricing/ for the commercial model.

Decide these before you start

Three questions settle the setup:

• Do you need to separate online from offline, or tie calls down to the keyword? That picks static versus DNI.
• Do you want recordings? If so, confirm the consent rules that apply to your callers before you turn them on.
• Who owns the tracking numbers if the relationship ends? The answer should always be you.

Get those right and the phone stops being a blind spot. It becomes just another measured channel, reported beside your forms and your traffic, so you can fund what works instead of guessing.