When you track phone number clicks, you learn how many people selected a tel: link on your website, but not how many of them actually spoke to you. Everything after the tap happens outside the browser. Measurement therefore has two parts: a correct setup and an honest interpretation.
This guide covers both. You set up an event for tel: and mailto: links, check what distorts the result, and compare a click with a callback request and a chat. General rules for choosing events are in our article on website micro-conversions.
What a click on your number actually records
Once someone selects a tel: link, the browser hands the number to the operating system, which opens the dialer, suggests an app, or does nothing. Your script sees only the moment the link was chosen. It cannot see whether a call was placed or answered.
Google Ads Help states plainly that its mobile number click conversion counts clicks on your number, not actual phone calls. It does not say how many clicks end in a conversation. Google Ads Help.
The same limit applies to mailto: links. Opening an email program does not mean a message was sent. Name the event after what it records: "phone number selected" rather than "call", "email address selected" rather than "email sent". We draw a similar line between a click and an outcome in our guide on PDF downloads versus link clicks.
Set up measurement for tel: and mailto: links
Your number usually appears in several places, and later you will ask which of them works.
- List every place with your number.Note each tel: and mailto: link with its page and position, such as "header", "footer" or "offer button".
- Turn plain text into a link.Replace a number written as plain text with a tel: link in international format, with the country code and no spaces in the link address.
- Add an event with a position parameter.Create one event for phone and one for email, and pass the link position as a parameter.
- Test on a phone and a computer.Select every link on both devices and confirm in your tool's preview that the event fires once, with the right position.
- Write down the definition.In the report description, state that the event means a link was selected, not that a call was made or a message was sent.
The enhanced measurement article in Google Analytics 4 Help defines an outbound click as a link leading to another website and does not mention tel: or mailto: links. On an iPhone, Safari may also turn text that looks like a number into a link that is not on your list. Mark any number that should be tappable yourself.
Archived Safari documentation says that Safari on iOS detects strings formatted like phone numbers by default and turns them into links, and that the format-detection meta tag lets you switch this off. It is an archived document, so check the behavior of current versions on a real device. Apple Developer.
Why a tap is not yet a conversation
The number of phone clicks has known biases in both directions. Accidental taps and repeats push it up, while people who copy the number by hand or call from your search listing push it down.
- Accidental tap: a sticky call button at the bottom of the screen is easy to hit while scrolling.
- Second thoughts: the visitor sees the number in the phone app and closes it without dialing.
- Desktop click: the system offers a calling program or does nothing, and the visitor types the number into a phone.
- Repeats: the same person selects the number several times because the line was busy.
- No answer: the call was placed, but nobody picked up, so no conversation took place.
- A number typed by hand or dialed from elsewhere, such as your business listing, leaves no click on the website.
MDN documentation explains that tel: link behavior varies with device capabilities: a cellular device dials the number, while a computer may open a calling program, save the number to contacts, or send it to another device. It says nothing about how often users end up placing a call. MDN Web Docs.
So count sessions with at least one number selection rather than raw clicks, and report phones and computers separately. If measurement requires consent, the result covers only visits where it was given. If you have call logs from your phone system, compare weekly totals with the number of sessions with a click. These are two different sets: some calls bypassed the website, and some clicks never became calls.
Which pages and devices come before the clicks
Break down sessions with a click by landing page, traffic source, and device. A fictional installation company found that almost all number selections came from phones and from a single service page, while the contact page its campaigns pointed to produced few of them. Customers decided to call before ever reaching the contact page.
In Meetlead Analytics you can record a number selection as a goal: you first define the goal key in the panel, your website code then calls it when the link is clicked, and the widget accepts only active, preconfigured keys. An element marked with the tracking attribute also appears in the visit history as a click. The customer journey shows the traffic source, campaign, landing page, device, and events for each visit, and the report lets you drill down from a trend to specific sessions and completed goals. Meetlead does not record the phone calls themselves, so the limit from the previous section still applies.
To see whether a customer came back several times before choosing your number, combine the visits into one story as described in our guide to the customer journey on your website. Without an event, a session that ends with a number tap looks like a quick exit. We cover that effect in our article on bounce rate.
A click, a callback request and a chat side by side
Phone, callback requests and chat leave very different traces in your data. The table shows what the website records and what you need to fill in from another source.
Scroll the table sideways to see all columns.
| Contact route | What the website records | What the data lacks |
|---|---|---|
| Click on the number | Link selection, page and device | Whether the call was placed, answered and what was said |
| Callback request | A request with number, topic and time | How the call went, unless someone adds a note |
| Chat conversation | Messages and the moment it started | The outcome, unless it is closed in a ticket |
The table points to a simple rule: a click on your number is a signal of intent, while a callback request and a chat are contacts already on record. Do not add them up into one "leads" figure until you know how many clicks turn into calls. Which channel suits which enquiry is covered in customer contact in a service business.
When a callback gives you a measurable alternative
A callback request has the edge when you see many clicks on your number but cannot tell how many became conversations. The customer leaves a number and topic, and the request exists even when nobody could answer at that moment. In Meetlead a callback stores the name, number, topic and time, and the statistics show the status breakdown and completed requests. The process on your side is covered in our guide to website callbacks.
Keep the number on the page, though: a callback is an extra route for people who cannot call right away, not a replacement for the phone. It works best next to the number on pages where many visitors select it on a computer or outside business hours. For calls that already slipped through, see our guide to missed calls from customers.
"Phone number selections: sessions in which someone selected a tel: link on [page] at least once, split by phone and computer. The result does not mean a call was placed or answered. Callback requests are reported separately as recorded requests."
Questions about phone number clicks
Are clicks on the number from a computer worth counting? Yes, but report them separately. On a computer, selecting the link often opens an app picker or does nothing, so the visitor may type the number by hand. A high share of such clicks suggests offering a callback request or chat next to the number.
Can you link a click to a specific call? Reliably, only if you run a separate call tracking system, for example with numbers assigned to traffic sources. Without one, you can only compare totals. If you need a contact tied to a visit, a callback request provides it straight away, because the request is created on the website.
