Why Call Tracking Metrics Is Not Tracking Phone Calls: Common Causes and Fixes

Quick Answer 

Most of the time, missing calls in CTM come down to one of six things: 

• Your website isn’t swapping your real number for a CTM tracking number. 
• People are seeing (and calling) your regular number instead of the tracking number. 
• Your tracking source is set up with the wrong rules, so CTM doesn’t know when to show the right number. 
• The call actually happened and got tracked, but it’s hiding from you in the report because of a filter or a reporting mix-up. 
• CTM’s script can’t actually “find” your phone number on the page, so it can’t swap it. 
• Browser privacy settings or ad blockers are quietly getting in the way. 

“Call Tracking Metrics not tracking phone calls or not working”-this is one of the most common problems we see. In fact, in most Google Ads jobs we get, 10% of them need to fix call tracking metrics.
When we delve into the root cause, we find so many problems. Website numbers are not swapping, tracking sources incorrectly, calls are filtered, and wrong browser privacy settings can cause things to go wrong many times. 
TTC Digital has been providing PPC services for years. We know what it takes, as we upgrade with strategic practices by keeping up with the latest techniques and principles.

Key Takeaways 

• Check your CTM tracking code if calls are not showing. 
• Make sure your phone number swaps correctly on your website. 
• Check your tracking sources, filters, and call settings. 
• Test your setup in a private browser window. 
• If a call is missing or has no recording, check the call details first. 

 Call Tracking Metrics Troubleshooting

Cause 1: Your Website Isn’t Swapping the Phone Number 

Here’s the deal with CTM: it’s supposed to swap out your real phone number for a special tracking number right on your website. That way, whenever someone calls, CTM can tell exactly where that call came from. 
But sometimes that swap just doesn’t happen. Here’s why: 

• The tracking code is missing, or it got installed wrong. 
• There’s a mismatched account ID in the script. 
• You’ve got two call-tracking scripts running at the same time, and they’re stepping on each other. 
• A caching or speed-optimization plugin is blocking the script. 
• The tracking source is turned off, or it’s using the wrong trigger. 
• The page someone landed on doesn’t match what the source is looking for. 
• Another source is grabbing the visitor before this one can. 
• Your real number isn’t added as a “target number” in CTM. 
• You’ve got duplicate numbers, or numbers formatted oddly, and CTM can’t recognize them. 

A quick way to check:

Open your browser console and type __ctm.config.aid. If nothing comes back (or you get an error), the script isn’t running. If it gives you an account ID, but it’s not your account, then the wrong script is on your site. 

The Fix 

• Copy the tracking code straight from CTM’s Tracking Code page. No edits, just paste it in fresh. 
• Reinstall it and republish your site. 
• Double-check it’s on every page that shows a phone number. 
• Remove any duplicate tracking scripts. 
• Tell your caching plugin to skip the CTM script. 
• Head to Numbers → Tracking Sources and make sure the source is turned on, “onsite” is enabled, the trigger matches your real traffic, and nothing else is overriding it. 
• Go to Numbers → Target Numbers and add your real number, typed exactly how it shows up on your website. 

And here’s a pro tip: always test in a private/incognito browser window. Just clearing your cache isn’t the same thing; it won’t always give you a clean, honest test.

Cause 2: Website Visitors Are Calling Your Regular Number Instead 

Sometimes your CTM setup is working just fine, but people never even see the tracking number. They’re calling your old, regular number instead, so CTM has no way to catch it. 
This usually happens when your number shows up as: 

• An image, PDF, or graphic instead of real text. 
• A number in a pop-up, iframe, or third-party widget. 
• A different number in your mobile menu or sticky header. 
• Whatever’s listed on your Google Business Profile, in online directories, or on social media. 
• An old number someone already had saved in their phone. 
• A number they grabbed from Google search results before landing on your site. 
• A call button in a Google Ad that isn’t connected to CTM. 

The Fix 

Audit every location where the number appears: 

• Your website’s header and footer (desktop and mobile). 
• Your mobile menu and click-to-call buttons. 
• Contact and location pages. 
• Landing pages. 
• Google Business Profile. 
• Google Ads call extensions. 
• Directory listings. 
• Email signatures. 
• PDFs and brochures. 
• Chat widgets and booking tools. 

For your website, set up CTM’s dynamic number insertion so the number always swaps automatically, no matter where someone lands. For offline stuff, like flyers or business cards, use separate static tracking numbers, so you can tell exactly which source each call came from. 

Cause 3: You Wrongly Configured The Tracking Source

CTM decides which tracking number to show someone based on rules you set up, called ‘tracking sources’. If those rules aren’t quite right, CTM won’t show the number you’re expecting, and the call won’t get tracked properly. 
This usually happens when: 

• The source is marked “off-site” when it should be “onsite.” 
• The URL or referral rule is wrong. 
• Both a referring URL and a landing URL are set, but your visitors only match one of them. 
• There’s a typo or mistake in a regex (pattern-matching) trigger. 
• A different source with higher priority is matching first. 
• The visitor’s path to your site drops important campaign info along the way. 

The Fix 

Here are some call tracking metrics trouble shooting : Go back and check your tracking source settings. Look at the rules one by one and ensure that the source is marked “onsite”, the URL rules match real traffic, and you’re not accidentally requiring two of the conditions to be met if your visitors only match one.  
Check the source priority and move the intended source above if needed. If you’re using a regex trigger, double-check that you didn’t make any typos, since a single one could cause a failure. If you have multiple sources, check which one has higher priority and if the intended one is getting overridden by another. 

Cause 4: Calls are Being Filtered or Not Counted 

Here’s one that trips people up a lot: the call actually happened, and CTM actually caught it. But when you go look at your report, it’s just… not there. That’s usually not a tracking problem at all. It’s a “looking in the wrong place” problem. 
This can happen because of: 

• An incorrect date range on your report. 
• You’re logged into the wrong account, user, or reporting view. 
• Filters are on for source, tracking number, call status, or campaign, and they’re hiding the call. 
• The call got tagged as missed, abandoned, spam, or too short, so it’s sitting in a different bucket than you’re looking at. 
• The call never actually reached the CTM tracking number in the first place. 
• A delay in your integrations or conversion imports, so the data just hasn’t shown up yet. 
• The call got routed through a forwarding number that isn’t hooked up to tracking. 

The Fix: 

Start simple. Double-check your date range and make sure you’re in the right account and reporting view. Then look at your filters, clear them out one by one, and see if the call pops up. If it’s still missing, check whether it might be sitting in a “missed” or “spam” bucket instead of your main call list. And if you’re relying on any integrations to pull the data in, give it a little time. Sometimes it just needs a few minutes to sync. 

Cause 5: CTM Can’t Actually “See” Your Phone Number on the Page 

 CTM’s script has to scan your webpage, find your phone number, and swap it. But if the script can’t see the number in the first place, there’s nothing for it to swap. 
This usually happens because of: 

• Your phone number is baked into an image or an SVG, or wrapped in some kind of element that the script just isn’t set up to scan. 
• The CSS selectors or target classes in your CTM settings don’t match your website’s actual HTML anymore. This happens a lot after a theme update, since new themes can quietly change element IDs or class names. 
• A JavaScript error somewhere else on your page is crashing things before CTM’s swapping script even gets a chance to run. 

The Fix 

Head into your CTM account under Settings → Tracking → Number Swapping, and take a look at your replacement rules and target selectors. Make sure your phone numbers are sitting inside standard HTML tags with clear identifiers or an obvious class or ID name. Avoid burying your number inside an image or graphic if you can help it. 
Then use CTM’s Number Swapping Debugger tool, or just test it yourself in an incognito window using a UTM link (something like ?utm_source=google&utm_medium=cpc) to see if the number actually swaps. 

Cause 6: Browser Privacy Settings or Ad Blockers Are Getting in the Way 

This last one isn’t really something broken on your end. It’s more about how browsers and privacy tools are getting stricter these days. Some of that can quietly mess with tracking. 
This usually happens because of: 
Strict privacy features, like Safari’s Intelligent Tracking Prevention (ITP), stripping out tracking parameters (like gclid or utm_*) before CTM even gets a chance to read them. 
Visitors using ad blockers or privacy extensions, like uBlock Origin, that block tracking scripts completely. 

The Fix 

• Set up First-Party Tracking or a subdomain tracking configuration through CTM. This will route your tracking script through your own domain instead of a third party, which offers much better resistance to browser privacy measures. 
• Educate stakeholders that a percentage of traffic may always be un-attributable due to privacy measures enacted on a user’s browser, but large decreases in reported traffic should be analyzed for anomalous configuration issues instead of user privacy policies. 

Cause 7: CTM Shows the Call, but There is No Recording 

This can be confusing. You can see the call in CTM, but there is no audio recording. 
There are a few simple reasons why this can happen: 

• The call was not answered. 
• The call had no talk time. 
• Call recording is turned off in the call settings. 
• A voice menu or agent turned off recording. 
• An admin deleted the recording. 

Usually, CTM starts recording after the call is answered and there is some talk time. If Record from Ringing is turned on, recording can start while the phone is still ringing.
Also, keep in mind that a deleted CTM recording cannot be recovered. 

How can you fix it? 

First, go to: 
Numbers → Call Settings → Edit 
Then check these settings: 

• Make sure call recording is turned on. 
• Check which call-settings configuration is linked to the tracking number. 
• Make sure the tracking number has the right configuration. 
• Check your IVR, voice menu, and agent recording settings. 
• Check if an admin deleted the recording. 
• Make sure your account permissions allow you to access recordings. 
• This quick check can help you find out why the call is showing up without an audio file. 

Final Thoughts 

The problem of missed calls in CTM seems complicated and can be disturbing, but it is usually caused by a small number of reasons: failure to swap numbers, calling a wrong number, a need to modify tracking rules, or the presence of the call on filtering. 
The best thing you can do is slow down and check it step by step. Review your setup, check your reports, and don’t be afraid to test things yourself. Most of the time, the answer is smaller and simpler than it feels in the moment. 
Take it one step at a time, and you’ll track down the issue in no time. You’ve got this!

Pritha Gupta

Pritha Gupta is the Digital Marketing lead at The Tech Clouds (TTC), leading digital growth through AI-powered search optimization, technical SEO, content marketing, performance marketing, and data-driven strategies that maximize brand visibility and business growth.