How Do I Track Calls From My Website, Not Just My Ads?

Your Google Ads report credits a handful of calls this month, yet your phone rang far more often. The rest came from people who found you through organic search, a referral or a saved bookmark and called the number on your site. None of those calls carries a source, so the pages that earned them get no credit.
To track calls from your whole website, you need dynamic number insertion (DNI) from a call tracking provider. Each visitor sees a number tied to how they arrived, and every number forwards to your real line. Google's forwarding numbers cover only ad clickers, and click-to-call events count taps, not conversations.
Why don't Google's forwarding numbers cover it?
Google Ads has its own website call tracking. It is free, and if you run ads you should use it. A phone snippet on your site replaces your business number with a dynamically generated Google forwarding number. That lets you judge keywords, ads, ad groups and campaigns against the calls they produce. A call only counts as a conversion when it lasts longer than a minimum length you set, which filters out wrong numbers and hang-ups. The setup is documented in Google's Ads Help Center, and setting up call conversions in Google Ads walks through it step by step.
The limitation is in the design. The forwarding number only appears for people who visited after clicking one of your ads. Everyone else sees your normal number and calls it untracked. That includes someone who searched your brand, read a service page from organic results, or came back three days later by typing your URL.
Two more constraints matter if your site is more complex. The snippet must sit on every page where the number appears. Google also states that the default JavaScript tag tracks only one number per page, so a multi-location site needs a manual install.
Google's tool covers the paid half of tracking calls from Google Ads. For the rest of your traffic, you need a different mechanism.
How does dynamic number insertion work?
DNI applies the same idea to every channel. You rent a pool of phone numbers from a call tracking provider and install their script through your site header, a tag manager or a CMS plugin. The script reads where each visitor came from, using URL parameters, the referring site and campaign tags. It then swaps every visible number on the page for one assigned to that source, including the numbers inside click-to-call links.
Every tracking number forwards to your real line, so callers notice nothing. When a call connects, the provider logs the channel, the landing page and the session. That data can then flow into Google Analytics and your CRM. Organic calls sit in the same report as paid ones, and you can finally compare them.
Some providers keep your main business number in the page's HTML source and swap it only in the visitor's browser. Crawlers then still see one consistent number. Ask any provider you are evaluating how they handle this.
Source, session or visitor level?
DNI comes in several levels of detail, and the right one depends on the question you need answered.
- Source-level assigns one number per channel, such as organic, paid, direct and referral. It tells you whether SEO produces calls, but not which page or keyword did.
- Session-level gives each browsing session its own number and returns it to the pool when the visitor leaves. This is where landing-page and keyword data comes from.
- Visitor-level ties a number to one person across several visits. It captures the pages and channels they touched before calling.
- Campaign-level assigns a fixed number to a single campaign, often an offline one such as a flyer or a billboard. It usually runs alongside one of the levels above.
For most local businesses, source-level answers the real question cheaply: is the website producing calls, and from where? Move to session-level when you want to know which service pages do the work.
The trade-off is cost. Session and visitor tracking need a larger number pool. Size it to your peak number of visitors on the site at the same time, not to your daily total.
Is a click-to-call event good enough?
There is a free alternative, and it is worth understanding what it does and does not tell you. In Google Tag Manager, you create a trigger that fires on clicks of any link containing `tel:`. You then send that click to Google Analytics as an event, with the page path attached. Many older guides were written for Universal Analytics, so rebuild the tag for GA4 rather than copying one.
This tells you which pages prompt people to tap your number. That is useful, but it is not call tracking. It records a tap, mostly from mobile visitors. It misses the desktop visitor who reads your number and types it into their phone. It cannot tell you whether the call connected, how long it lasted, or whether it was a booking or a wrong number.
Use click events as a directional signal while you decide on a provider, or as a sense-check alongside DNI. Do not report them as calls, and do not feed them to a bidding algorithm as if they were leads.
How do you protect local SEO while tracking?
DNI should change the number shown on your website and nowhere else. Keep your primary business number on your Google Business Profile and in directory citations. Local search leans on consistent name, address and phone (NAP) details across the web. Putting a tracking number into a citation introduces a phone number that contradicts everything else Google has on file for you.
The safe pattern is simple. Your real number is the canonical one everywhere off-site, and tracking numbers exist only in the visitor's browser on your own pages.
Then test before you trust the reports. Load your site from a Google search, an ad click, a direct visit and a referral link, and confirm each shows a different number. If a number fails to swap, check three things:
- the script loads on every page;
- no other tracking script is overwriting it;
- browser cookie settings are not breaking session recognition.
Make a test call from each source and confirm it lands in your analytics under the right channel.
Conclusion
Google's forwarding numbers answer one narrow question: which ads made the phone ring. To see calls from organic search, referrals and returning visitors, you need dynamic number insertion. Pick the level of detail your question needs, keep your real number canonical off-site, and treat click-to-call events as a hint rather than a count. Once every channel shows its own number, your website's call volume stops being a mystery and becomes something you can report and improve.
Frequently Asked Questions
Yes, but install carefully. Google advises against deploying its phone snippet through Google Tag Manager on sites using DNI or third-party call tracking. Install the tag manually, or link Google Search Console to Google Ads. Google cannot scan a DNI site to verify the number, so verify domain ownership to avoid call asset disapprovals. Search Console links take 24 hours, and call assets must then be resubmitted.
No setup catches everything. Google counts a website call as a conversion only when it lasts longer than the minimum length you set. DNI misses callers who saved your number on an earlier visit, and anyone who finds it in a directory or on your Google Business Profile. Treat tracked calls as a reliable floor, not a complete total, and compare against your phone system's logs.
That depends on the level of detail you choose. Source-level tracking needs one number per channel, often four or five in total. Session-level and visitor-level tracking need a pool large enough to give everyone on the site at once their own number. Size that pool to your peak concurrent visitors rather than daily traffic, or numbers will be reused mid-session and calls will be misattributed.
Get a complimentary audit to uncover AI opportunities hidden in your data.
Put these strategies to work


