How to Track Phone Number Clicks in GA4 (Tested)

web development
Two plain silver tin cans joined by a cotton string, a homemade string telephone, on a dusty-lavender table, a metaphor for phone number clicks that GA4 does not record by default
A tap on a tel: link opens the dialer, but GA4's enhanced measurement sends nothing for it. You have to send the event yourself.

The short answer

GA4 doesn't track phone number clicks out of the box. Enhanced measurement's "outbound clicks" setting only fires for links that leave your domain for another website. A tel: link isn't a website, so a tap on your phone number sends nothing. The same goes for sms: and mailto: links. You fix it with one small click listener (or a Google Tag Manager trigger) that sends a phone_click event, then you mark that event as a key event.

That's the answer most local service businesses need, because for a plumber, a dentist or a roofer the phone number is the main conversion. If GA4 can't see it, your reports say the site barely converts.

The web is split on this. Some guides say enhanced measurement already counts tel: and mailto: as outbound clicks, others say it doesn't. So we tested it instead of picking a side.

How we tested it

We built a plain page with 10 different links and buttons, loaded a real GA4 container from a public site that has enhanced measurement and outbound clicks switched on, and clicked each element in headless Chromium 148. Every request to Google was intercepted locally, so no hit ever reached anyone's property. We recorded exactly what gtag.js handed to the browser to send, ran it once as desktop Chrome and once as an emulated iPhone, and then ran it again with our fix installed.

Here's what enhanced measurement sent with outbound clicks ON:

  • Phone link with text (tel:+12145550100): nothing.
  • Icon-only phone link (an SVG inside the <a>, clicked on the icon): nothing.
  • Email link (mailto:): nothing.
  • Text-us link (sms:): nothing.
  • "Call now" button that runs location.href = 'tel:...': nothing.
  • WhatsApp link (https://wa.me/...): a click event with link_domain: wa.me and outbound: true.
  • Booking link, same tab (calendly.com): a click event with outbound: true.
  • Booking link, new tab: a click event with outbound: true.
  • Internal link to the contact page: nothing, as expected.

The iPhone run matched desktop: tel: and sms: sent nothing, wa.me sent a click.

So the phone, text and email links are invisible to GA4, while WhatsApp and booking links are tracked. Google's own enhanced measurement documentation describes outbound clicks as links "that leads away from the current domain and to another website", and the tag behaves exactly that way.

One more detail from the test: the built-in outbound click event carried link_url, link_domain and outbound, but no link_text. If you have three WhatsApp buttons on a page, the built-in event can't tell you which one got tapped unless they point to different URLs.

Why this costs local businesses real money

When phone taps don't exist in GA4, three things go wrong at once.

Your conversion rate looks terrible. A home-services site where most leads call instead of filling in a form will show a fraction of its real conversions. We covered how to read those numbers properly in our CRO checklist for service websites.

Your ads bid on the wrong signal. If Google Ads imports GA4 key events and phone clicks aren't one of them, Smart Bidding optimizes toward form fills only. Campaigns that drive calls look like they're failing and get cut.

You can't compare pages. You don't know whether the sticky call bar on mobile beats the number in the header, because neither one reports.

The fix: a 10-line click listener

If you use the gtag snippet directly (no Google Tag Manager), paste this after it, anywhere on every page:

<script>
document.addEventListener('click', function (e) {
  var link = e.target.closest && e.target.closest('a[href^="tel:"], a[href^="sms:"], a[href^="mailto:"]');
  if (!link || typeof gtag !== 'function') return;
  var href = link.getAttribute('href');
  var names = { tel: 'phone_click', sms: 'sms_click', mailto: 'email_click' };
  gtag('event', names[href.split(':')[0].toLowerCase()], {
    link_url: href,
    link_text: (link.textContent || link.getAttribute('aria-label') || '').trim().slice(0, 100)
  });
}, true);
</script>

We ran the same 10-element test with this installed. Results with the fix:

  • Phone link with text: phone_click with link_url: tel:+12145550100 and link_text: Call (214) 555-0100.
  • Icon-only phone link, clicked on the link or on the SVG inside it: phone_click, but link_text was empty.
  • Email link: email_click with the address and the link text.
  • Text-us link: sms_click.
  • JavaScript "Call now" button: still nothing.
  • Booking link: the normal enhanced measurement click, unchanged.

The iPhone run sent phone_click and sms_click the same way.

Why these choices

It listens on the document, not on each link. Phone numbers get added by page builders, footers and popups after the page loads. A single listener catches all of them, including links added later.

It uses closest(). People tap the phone icon, not the <a> around it. In our test the click target was the SVG, and closest() still found the link.

It reuses link_url and link_text. GA4 already has "Link URL" and "Link text" dimensions that read those parameters, so you can break phone clicks down by number or button text in Explorations without creating custom dimensions.

It doesn't block or delay the dialer. A tel: tap doesn't unload your page, so the hit goes out normally.

Two things the snippet can't fix for you

Icon-only links send an empty link_text. Add aria-label="Call (214) 555-0100" to them. It's better for screen readers anyway, and the snippet falls back to it.

JavaScript call buttons are invisible to it. A <button> that sets location.href = 'tel:...' isn't a link, so nothing matched in our test. Make it a real <a href="tel:..."> link, or put gtag('event', 'phone_click', {...}) inside that button's own click handler.

Doing the same thing in Google Tag Manager

If your GA4 tag lives in Google Tag Manager, you don't need the script. Create a trigger of type Click - Just Links, set it to fire on Some Link Clicks where Click URL starts with tel:, and attach a Google Analytics: GA4 Event tag named phone_click with link_url set to {{Click URL}} and link_text set to {{Click Text}}. Repeat for sms: and mailto:, or use a regex condition ^(tel|sms|mailto): with a lookup table for the event name.

Turn on the Click URL and Click Text built-in variables first, or the fields won't be available. Test it in GTM's Preview mode before you publish the container.

Make phone_click count as a conversion

Sending the event is half the job. In GA4, go to Admin > Data display > Key events, create a new key event and type phone_click exactly as it's sent. From then on it shows up as a key event in reports and you can import it into Google Ads.

If you run Google Ads and import GA4 key events, check that the imported action is set to the counting method you want. For calls, counting "One" per click is usually right, because the same person tapping the number twice in a minute isn't two leads.

A phone click is not a phone call

Be honest about what this event measures. phone_click is call intent, not a connected call. On an iPhone, Safari asks the visitor to confirm before it dials, and some people cancel. On a desktop, a click may open FaceTime or a calling app nobody uses. And it won't see anyone who reads the number off the screen and dials it by hand.

For most local businesses the click is still the best signal you'll get from the website itself, and it's far better than nothing. When you need connected calls, call length or which calls became booked jobs, you need call tracking or your phone system's records. We explain how that works with dynamic numbers and AI phone agents in our guide to call tracking for voice agents.

Quick checks if phone_click still doesn't show up

Consent mode is blocking it. If your cookie banner sets analytics_storage to denied, GA4 sends cookieless pings or nothing until the visitor accepts. That's the same reason form conversions vanish after a consent update, which we walked through in our consent mode troubleshooting post.

The snippet loads before gtag. The typeof gtag !== 'function' guard means it quietly does nothing if gtag isn't defined yet. Put it after the gtag snippet.

Your container has no enhanced measurement code at all. Open https://www.googletagmanager.com/gtag/js?id=G-XXXXXXX with your own ID and search for __ccd_em_outbound_click and __ccd_em_scroll. The container we used for this test had both. While setting up the test we also loaded a container where those modules were missing, and in that one no scroll or outbound click event fired at all, even though its tag config listed outbound clicks and scroll as enabled. If yours is missing them, check the stream's enhanced measurement settings in GA4 Admin first.

You're checking the wrong report. New events take up to a day or two to reach standard reports. Use DebugView or Realtime to confirm the event, then wait before building anything on it.

What we'd set up on a typical local business site

  • A phone_click key event for every tel: link, with aria-label on icon-only buttons.
  • sms_click and email_click as regular events, so they're visible but don't inflate conversions.
  • WhatsApp and booking links left to enhanced measurement's built-in click, or given their own named events if they're a primary lead path. Paid WhatsApp traffic needs more than that, covered in our click-to-WhatsApp ads tracking guide.
  • Call tracking on top when the business spends real money on ads and needs to know which calls turned into jobs.

The bottom line

  • GA4 enhanced measurement does not track tel:, sms: or mailto: clicks. In our test those links sent nothing on desktop or iPhone.
  • It does send a click event for WhatsApp and booking links on other domains, without link text.
  • An 10-line click listener (or a GTM Just Links trigger) fixes it. Use link_url and link_text so GA4's built-in dimensions work.
  • Mark phone_click as a key event, and remember it measures intent, not connected calls.

Not sure whether your site is counting calls at all? That's one of the first things we check. Get a Free Automation Audit and we'll email you an initial report within 24 hours covering your GA4 key events, phone and form tracking, and what your ads are actually optimizing for. If you want us to fix it and keep it running, see our ads management and tracking service.